KV storage for Claude, Codex & other agents
Agents forget everything between runs. A KV storage is a small named key-value store that lives in AIP — your agents read and write it through two tools, so notes, decisions, and state survive to the next session and can be shared between agents.
What your agent can do
These are the exact tool names an MCP client sees — KV storage is built into AIP, so they come straight from the product. Each one can be set to Allow, Confirm, or Hide — per agent.
| Tool | What it does | Access |
|---|---|---|
| kv_get | Read the value stored under a key. Returns found: false when the key was never written. | read |
| kv_set | Write a value under a key, replacing whatever was stored under that key before. | write |
Why agents need it
Every agent session starts from zero: yesterday’s context, decisions, and half-finished state are gone. A KV storage gives your agents a place to keep that context between runs — stored in AIP, not in any single client, so the same memory is there whether the next session runs in Claude, Claude Code, Codex, or anything else connected through your AIP URL.
Each storage is a separate integration with its own name and its own permissions. That means you can keep concerns apart — one storage for a project’s working notes, another for personal preferences — and decide per agent which storages it sees at all.
How to set one up
- Open the dashboard, go to Integrations, and add a KV storage — just pick a name, no account to connect.
- Switch on
kv_getandkv_setfor the agents that should use it. Like every tool in AIP, each one can be set to Allow, Confirm, or Hide — per agent. - Tell your agent what to remember. It writes with
kv_set, reads withkv_get, and the values are there on the next run.
KV storages are part of the Pro plan, along with the other custom integrations.
Shared memory between agents
Because a storage lives in AIP rather than in one client, two different
agents can use the same storage as a shared workspace: Claude Code writes a
handoff note at the end of a coding session, and the Claude app reads it when
you ask “where did we leave off?” — no copy-paste between tools. Give one
agent write access and another read-only access by hiding kv_set where it
is not needed.
Limits
Keys are strings up to 512 characters; values are strings up to 100,000 characters. Writing to an existing key replaces its previous value. That is enough for notes, checklists, JSON state, or a compact document — it is not a database, and truly large artifacts belong in the systems your agents already reach through other integrations.
What to ask your agent
Once it's set up, prompts like these all resolve through KV storage: