Agent memory
A new chat.Not a blank slate.
Agent memory on CoreSpeed keeps the preferences, project decisions and team context your agents learn, across chats and across clients. Save a decision in Claude Code and find it later in Codex or Cursor, because memory lives on your CoreSpeed account and is served over MCP. You host nothing, and private memories stay private.
Give this to your agent
set up https://corespeed.io/SKILL.mdNo app connection needed. Save a useful memory and recall it later.
Keep the contextworth keeping.
Three kinds of memory worth saving. The data is fictional.
Lead with the recommendation. Keep the explanation short.You
Use US spelling in customer emails.You
Keep your preferences
Private · Useful again in your next chat
Carry project decisions
Shared · The decision stays in view
Jessica owns the Acme rollout. Confirm scope with her before quoting a date.Cursor · Mira
For the launch, start with existing customers.Claude Code · You
Release notes go out on Thursdays.Codex · Reid
Share what the team knows
Shared · Found before the next step
Switch agents.Keep the context.
Save a decision in one agent. Find it in another agent signed in to the same CoreSpeed organization. The useful context stays with you.
Reads fromCoreSpeed Memory
More about CoreSpeed Memory →What did we decide about the launch audience? Use that decision in this draft.
memory__searchok
1 shared memory: the launch audience decision
Save it once.Find it when it matters.
Keep working in your agent. Give the next session something useful to start from.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Save one useful thing
Ask your agent to remember a preference or a decision. Choose private or shared.
- 3
Recall it in a later session
Ask any connected agent to find the memory before it starts.
Setup guidesClaude CodeCodexCursor