FAQ
Straight answers about the library and how agents use it.
Questions
How do enterprises use Sirro?
Company workspaces give teammates and their connected agents a shared library. Packs collect onboarding docs, conventions, and working examples. Sirro is also developing company Playbooks with confirmed facts, recorded outcomes, and owner-approved changes for recurring work.
How does Sirro help work improve?
Teams update saved work, and subsequent retrievals return the improved version. The planned Playbook loop adds outcome records, version history, and a path from draft to used to proven, supported by human confirmation or checkable evidence.
How does reuse affect compute usage?
Retrieving saved work replaces generation of that work with retrieval and adaptation. The net compute effect is the work avoided, less the cost of retrieval, reading, adaptation, and validation. Measure complete tasks against the same quality criteria to establish the result.
What is Sirro?
Sirro is a library of reusable work for AI agents. Its coding-agent library lets you save components, prompts, and docs by name across projects and tools. Personal-agent Playbooks for recurring work are in development.
What problem does Sirro solve?
Agents start fresh in every repo, and teams rebuild the same sections, prompts, and patterns. A folder of snippets in one repository does not travel with the next agent. Sirro keeps the named work in one library.
How does Sirro connect to AI coding tools?
From the dashboard, Connect Cursor, Claude Code, Codex, or another supported agent. The tool opens Sirro in the browser. You sign in and Allow a workspace. The agent keeps a token. You do not paste an API key into chat.
What can I save in Sirro?
In the coding library, you can save components, page sections, animations, prompts, code patterns, and links. Group related assets in a Pack. Images are not saved with a component. Personal-agent Playbooks and confirmed work facts are in development.
What is a Playbook?
A Playbook is a named, step-by-step method for a recurring personal-agent task. The planned Playbook workflow will track versions and move a Playbook from draft to used to proven only with a confirmed or checkable result. Personal-agent Playbooks are not available yet.
Will my personal Playbooks be shared?
No. The planned personal-agent library will stay private unless you choose to share. Team or community sharing will require an explicit choice and review.
Is Sirro tied to one codebase?
No. The library is outside Git. The same names are available in every project where an allowed agent is connected.
Does Sirro replace project rules or instructions?
No. Rules guide an agent inside one project. Sirro stores work you chose to keep, and that work can be fetched by name from another project.
Does Sirro store every chat?
No. Sirro saves what you ask an agent to save. It does not index the repository or keep the chat log.
Can a team share one library?
Yes. A personal workspace stays private. A team workspace is one library for the people on that team and the agents they have allowed.
Is Sirro open yet?
The public product is not fully open. Join the waitlist to be told when it launches. People who already have access can sign in to their workspace.
Who is Sirro for?
Today, developers and teams using coding agents across projects. Sirro is also building a personal-agent library for people who want to reuse and improve proven methods for recurring work.