Skip to content

Shared memory for Claude Code, Cursor, and Codex

You shouldn’t have to explain your preferences to every agent.

Save the facts you want to carry between tools in Kody. Your connected agents can retrieve them without carrying over an entire conversation.

Connect your agents
Your Kody memory
Release summaries

Include source links.
List breaking changes first.

A fact you chose to save

Write the release summary for this pull request.

Relevant memory from Kody

Release summaries: include source links and list breaking changes first.

Preparing a release summary

Breaking changes first. Source links attached to each change.

Example only, these buttons don’t read or change your saved memories.

Keep your preferences with you.

Save a preference in Kody so your other agents can find it. Keep repository instructions, chats, and credentials where they belong.

Read how Kody memory works ↗

Your preferences can shape the work, too. Kody puts memory alongside your connected services and reusable workflows, so your agents can find the context they need.

In your Kody memory
Writing preferences, project nicknames, and context your other agents should be able to find.
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 preference, then try another agent.

  1. Connect two agents to your Kody account.
  2. Give the first agent this prompt.
  3. Ask the second to find your release-summary preference and use it.

Change the preference and verify it again, or delete the test memory when you’re done.

Set up your Kody account ↗

Check my existing Kody memories before saving this preference: release summaries should include the source links and list breaking changes first. Save or update the relevant memory, then show me exactly what was saved so I can verify it from another agent.