Sirro

Agent connections

Connect your coding tools to one Sirro workspace. Save useful work by name, then use it in another project or agent.

Overview

Sirro gives connected agents one library of reusable work outside your repositories. Save a component, pattern, prompt, skill, or link once. Later, ask another agent to use it by name.

Sirro connects through the Model Context Protocol (MCP). Cursor, Claude Code, and Codex can use the same workspace, so a piece saved in one tool is available in the others.

Core concepts

  • Workspace

    The library you connect to. A personal workspace holds your own work; a team workspace lets its members and connected agents use the same names.

  • Asset

    One named piece of reusable work, such as a component, page section, convention, prompt, skill, or link.

  • Pack

    A named collection of assets and instructions. Use a Pack to onboard an agent, carry a workflow into another project, or share approved work with your Team.

  • Connection

    The link between a coding tool and a workspace. You sign in and Allow the tool in your browser.

Quickstart

  1. Sign in to your Sirro workspace. If you do not have one yet, join the waitlist.
  2. Open Connect in the dashboard and choose Cursor, Claude Code, or Codex.
  3. Complete the browser sign-in, select your workspace, and Allow the connection.
  4. Ask your agent: save this navbar to Sirro as navbar.
  5. In another project or tool, ask: use navbar from Sirro.

The setup guide walks through the first save. The connection commands show how to add Sirro inside each tool.

Connect your agent

Cursor, Claude Code, and Codex have guided setup from the Sirro dashboard. You can also add the hosted Sirro connection inside each tool. It opens your browser so you can sign in and Allow.

Other tools that support hosted MCP connections can use the connection address shown in the dashboard. Their sign-in flow depends on the client. See integrations for the supported tools and documentation for setup snippets.

What your agent can do

  • Find and retrieve

    Use sirro_list when you do not know a name, and sirro_get when you do. For several named pieces or a Pack, use sirro_compose.

  • Save and organize

    Use sirro_save to save an asset, sirro_update to change its details, and sirro_save_bundle to create a Pack when you ask for one.

  • Use packs

    Ask your agent to use a Pack by name when it needs a set of docs, workflows, or assets together. A teammate can use a Pack from the Team workspace as soon as they have access.

Requests that work well

  • Use navbar from Sirro. Names one asset to fetch.
  • Find a hero section in Sirro that fits this page. Starts with a search when you do not know the name.
  • Save this hook to Sirro as use-debounce. Gives the saved work a name you can ask for later.
  • Use the frontend-onboarding Pack from Sirro. Gives your agent the team docs and workflow for its task.

Use names you can remember. When a save returns a different name because one is already taken, use the returned name next time.

Workspace access and data

Each connection is tied to the workspace you select when you Allow it. An agent connected to one workspace cannot retrieve assets from another. Team members use the same library only when they have access to that workspace.

Sirro does not scan your projects on its own. Your agent sends source files or text to Sirro when you ask it to save them. Review what you are saving, especially when a project contains private material.

Troubleshooting

  • Sirro is missing from the tool list. Restart the coding tool after adding the connection, then check its connection settings.
  • The browser did not finish connecting. Sign in to Sirro, reopen Connect, and complete Allow for the workspace you want.
  • An asset cannot be found. Check its exact name with sirro_list and confirm the agent is connected to the workspace where it was saved.
  • A save used an unexpected name. Another asset may already have that name. Use the name returned by sirro_save.

Build on better work

Update a shared implementation or Pack when you find a better approach, so subsequent retrievals return the improved version. Sirro is also developing Playbooks that record outcomes, preserve versions, and use confirmed results to improve recurring methods.

Read How work improves for that loop, Compute and reuse for the compute model, and For enterprise for company workflows and onboarding.

Keep going

Setup covers the first connection. Documentation has commands for each tool. Integrations lists supported clients. For the planned personal-agent library, read Personal agents and Playbooks.