LOCAL-FIRST RECALL FOR CODING AGENTS
BRING YOUR CODING AGENT ON
STEROIDS.
Ask any agent why you made a call. Steroid answers from your past sessions and cites the session it came from.
Works with Claude Code, Cursor, Codex and GitHub Copilot CLI.
>
CONTEXT-MAXXING.
Most memory tools only remember what happens after you install them, and only inside one agent. Steroid gives each project one unified context: the work you've already done on it in every IDE, and everything you do from here on, is one prompt away.
MOST MEMORY TOOLS
Start empty the day you install them, and remember per agent. Everything you did before is out of reach.
STEROID
One context per project, across every IDE. Starts with your project's history on day one, and keeps everything that comes after.
WHERE STEROID RUNS.
C
Cursor
Cursor IDE and Cursor CLI chats.
CC
Claude Code (CLI)
Sessions kept up to date automatically (past 30 days by default).
GH
GitHub Copilot CLI
Copilot CLI sessions. Copilot Chat in VS Code is not covered yet.
CX
Codex
Sessions and file edits. Shell commands are not captured.
AG
Antigravity
Coming soon
// Don't see your IDE? Use the button above to request support.
WHAT STAYS ON YOUR MACHINE.
ON YOUR MACHINE
Your project memory is built and stored on your device, and needs no Steroid account.
HANDED TO YOUR AGENT
When your agent asks for context, Steroid gives it just the relevant pieces, right on your device. Your agent uses them like anything else you share with it.
USAGE COUNTS
Unless you opt out, the CLI sends aggregate counts, such as whether a recall succeeded, tied to a random install ID. Never content.
NEVER COLLECTED
Your code, files, conversations, queries and answers, and your project names or paths.
STEROID CLI
What it is
One unified context per project. Work you've done on a project in Claude Code, Cursor, Codex and Copilot CLI comes together in one memory, so any new session — in any editor — can recall what was decided, built or fixed before.
4
IDEs, One Memory
3
Operating Systems
1
Prompt to Recall Any Chat
LOCAL TODAY. CONNECTED NEXT.
LOCAL
- Conversation recall
- Cross-agent context
- Always-fresh memory
No sign-up. Your memory stays on your device.
CONNECTED
Everything in Local, plus:
- MCP marketplace — discover and run tool servers from your agent.
- Flows — workflows your agent can build and run.
- Vault — encrypted credential storage.
QUESTIONS, ANSWERED.
Does my code or conversation leave my machine?
Steroid doesn't send your code or conversations anywhere. Your project memory is built and stored on your device, and when your agent asks for context, Steroid hands it the relevant pieces locally. Your agent then uses that context like anything else you share with it, under the terms of its own model provider.
What usage data does Steroid collect?
By default the CLI sends aggregate usage counts, such as whether a recall was answered, a coarse time bucket, and which setup or update step failed. They are tied to a random install ID that is not linked to an account, and they never include your code, files, conversations, queries, answers, project names or paths. Turn it off with DO_NOT_TRACK=1 or by running steroid telemetry disable. The full field list is on the telemetry page.
Which agents does it support?
Claude Code (CLI), Cursor, Codex and GitHub Copilot CLI today. Antigravity is coming soon. Copilot Chat in VS Code is not covered yet.
How is this different from the memory built into my agent?
Built-in memory is per vendor and keeps short notes the agent chose to save, starting from when it was turned on. Steroid searches your full past sessions across vendors, even including the ones from before you installed our tool, and shows where each answer came from.
Does it cost anything?
Local mode is free.
What if my agent deletes old sessions?
Steroid remembers the sessions your agents still keep. If an agent deletes an old session, Steroid forgets it too the next time its memory refreshes.
ONE MEMORY
FOR EVERY AGENT.
Free for individual developers. Local mode runs on your machine.