Documentation

Guides

• Playbooks: a task written down for a cheaper model, and the cheapest model that passes it.
• For enterprise: company knowledge, onboarding, access, and shared methods.
• Agent onboarding: give a teammate the working context in a Pack.
• How work improves: outcomes, evidence, versions, and review.
• Compute and reuse: reduce repeated work and measure the result.
• Personal agents and Playbooks: recurring work across agents.

Overview

Sirro keeps reusable work available across agents and projects. Start with a named asset, gather related knowledge in a Pack, or save a task as a Playbook so a cheaper model can run it next time. The guides cover personal use, company libraries, and how shared work improves.

Connect from your library, or add Sirro in your coding tool. Sirro opens in the browser so you can sign in, choose a workspace, and Allow the connection.

Playbooks

After a strong model does a task well, say “save this as a playbook”. The agent writes the steps, rules and worked examples for a weaker model and saves them by name. Any agent can then run the Playbook, every run records the model and whether it passed, and your library names the cheapest model that does the job. Read Playbooks for the whole loop.

Personal agents and Playbooks

Sirro is expanding beyond coding. The planned personal-agent library will keep Playbooks for recurring work, facts you have confirmed, and versions that improve as results are checked. The connection steps below cover the coding library. Read the personal-agent guidefor the planned workflow.

Requirements

• A Sirro account
• Cursor, Claude Code, Codex, or another supported coding agent

Connect

Open Connect in your library and pick your tool. That is the usual path. If you are adding Sirro by hand, use this address, then Allow in the browser and pick a workspace:

https://sirro.dev/mcp

Cursor

Use Add to Cursor from your library, or paste this into Cursor Settings. Cursor opens Sirro so you can Allow.

{
  "mcpServers": {
    "sirro": {
      "url": "https://sirro.dev/mcp"
    }
  }
}

Claude Code

Run this in your terminal, or use the command from your library. Claude opens Sirro so you can Allow.

claude mcp add --transport http --scope user sirro https://sirro.dev/mcp

Codex

Run this in your terminal, or use the command from your library. Codex opens Sirro so you can Allow.

codex mcp add sirro --url https://sirro.dev/mcp

What your agent can do

• sirro_save

  Save code or a link to your Sirro library. Pass files with source paths for fast, complete saves. Sirro reads from disk, bundles local imports, and collects the rules and design tokens that style the component even when they live in a stylesheet it never imports. Images are excluded.

• sirro_get

  Retrieve a saved asset by name.

• sirro_list

  List saved asset and Pack names.

• sirro_compose

  Fetch several named assets or a Pack in one request. Use this when someone asks for a Pack, for example: use the frontend-onboarding Pack from Sirro.

• sirro_save_bundle

  Create a named Pack when someone asks the agent for one. An agent can also make an ordered list of named assets when asked; it appears in the library as a Pack.

• sirro_update

  Update metadata for a saved asset (name, category, tags, and more).

• sirro_open

  Open your Sirro library in your browser (requires login).

Typical workflow

1. Open your library. If you do not have one yet, join the waitlist.
2. Connect your agent from your library, then Allow in the browser.
3. Ask your agent to save work, for example: save this navbar to Sirro as navbar.
4. Reuse it later in any project: use navbar from Sirro. For a page, name the pieces: use hero-4, section-2, section-1, section-9, cta-2 and footer-2 from Sirro.

Next steps

Setup is the short path. How it works explains the workflow. Integrations lists the tools. Tips covers agent onboarding, working across tools, and sharing Packs with your Team.