SETUROSClaude Code
Memory for Claude Code that carries across sessions and tools.
A new Claude Code session doesn’t know what the last one decided. Seturos keeps what was settled in each repository and hands it to the next session, or to whichever AI tool you open next.
Set it up
In Claude Code, run:
/plugin marketplace add labby2094-blip/seturos-plugin /plugin install seturos@seturos-plugins
The plugin connects to your Seturos account the first time you use it.
Three commands
- /seturos:resume brings back what was decided and what is still open in this repository.
- /seturos:carry saves what this session settled, so the next session or tool can continue.
- /seturos:find looks something up in your earlier work and your projects.
One repository at a time
Each repository keeps its own sessions. A session is filed under the repository it ran in and is never offered to another one, so a side project never turns up in client work.
Between the terminal and the browser
Carry from Claude Code and resume in ChatGPT or Claude in the browser, or the other way round. Codex, Cursor and other tools connect the same way, through the Seturos MCP server:
https://app.seturos.com/api/mcp
Questions
Is this the same as CLAUDE.md?
No. CLAUDE.md holds the rules you write for a repository. Seturos keeps what each session decided and left open, and makes it available to your other AI tools too.
What leaves my machine?
What a session settled, when you carry it, with API keys and tokens removed. It is never used to train models, and only people who can see the project can see it.
Does it work with Codex and Cursor?
Yes, through the Seturos MCP server, listed in the official MCP registry as com.seturos/seturos.
More guides
Start free during early access. Sign up at app.seturos.com, add the extension, and carry your first conversation in a minute.