Shared memory for Claude Code, Cursor, and Codex
Give repeatable work a package. Save the leftover facts in memory.
Keep task behavior in code, with typed inputs and documented defaults. Use memory for facts that don’t have a better home, like a project nickname your other agents should recognize.
Connect your agents
Your Kody memory“Maple” is my nickname for
the customer portal project.
Available to agents connected to the same Kody account.
Which project do I call Maple?
Maple is the customer portal project.
Maple is your nickname for the customer portal project.
Example only, these buttons don’t read or change your saved memories.
Choose the right home for context.
Want every release summary to include source links and put breaking changes first? Build that into the release-summary package so it happens whenever you run it.
Read how Kody memory works ↗A reply utility can quote the thread automatically. A weather utility can have a documented default location. Neither needs an agent to remember a separate instruction each time.
- In package code and documentation
- Repeatable steps, output rules, typed inputs, and task defaults.
- In your Kody memory
- Facts that don’t already belong in a package or another system, like a project nickname or how you know someone.
- In your repository or client
- Local instructions and conversation history. Connecting Kody doesn’t synchronize every chat.
- In package storage or secrets
- A workflow’s last processed item belongs in storage. API credentials belong in secrets or integrations.
You decide
what sticks.
The agent checks related memories before it saves, updates, or deletes a fact. You can review and export what’s been saved.
Kody finds a few relevant memories when your agent searches or runs code with task context. It doesn’t load everything, so a saved fact won’t necessarily show up in every response.
Shared memory here means your own connected agents. It doesn’t automatically share your private context with other people.
Separate shared context from agent instructions ↗Save a fact, then try another agent.
- Connect two agents to your Kody account.
- Give the first agent this prompt.
- Ask the second to retrieve the project nickname you saved.
Change the fact and verify it again, or delete the test memory when you’re done.
Set up your Kody account ↗Help me test shared memory with a harmless project nickname that isn’t already recorded in my project tools. Ask me for the nickname and what it refers to, check existing Kody memories, then save or update the fact. Show me what was saved so I can ask another agent to retrieve it.