Sirro now works in Cursor, Claude Code and Codex

Developers move between coding agents. You might use Cursor in one project, open Claude Code in a terminal for another, and ask Codex to take on a third. The useful work you finish should be available wherever you work next. Sirro now connects to all three, giving each approved coding agent access to the same library of saved assets.

That library lives outside any one editor, terminal session, or repository. Save a component, design pattern, prompt, or link with one connected agent, and another can find it later by name. If you refined a navbar in Cursor and approved the result, you can save it to Sirro and ask Claude Code or Codex to retrieve it for a different project. The agent still has to adapt the material to that project and check the result, but it starts with the actual work you chose to keep.

The connection uses the Model Context Protocol. Sirro's beta onboarding gives you setup steps for Cursor, Claude Code, and Codex. After you add Sirro to a client, the client opens a browser authorization flow. You sign in if needed and approve access to your library. Each client makes its own connection, and those connections point to the same saved workspace. Your credentials stay out of the agent conversation and project files.

Once connected, an agent can save work worth keeping, search the library, inspect a promising result, and retrieve the full asset it needs. You can browse the same material in Sirro. Named assets and saved versions make it easier to point an agent to a result you already trust, even when you have changed tools or started a fresh session.

The shared library becomes especially useful when your work moves across projects. The application code stays in its repository. The reusable pieces you deliberately save stay in Sirro, ready for another approved agent to use. Your choice of coding tool can then follow the task at hand while your library remains available.

Cursor, Claude Code, and Codex are the three coding clients presented in the closed-beta onboarding. If you already have access, open Connect for the tool you use, complete its authorization steps, and save the first result you would want another agent to find. If you are joining now, start at beta.sirro.dev.