uac unified agent context

Claude Code Codex + any MCP agent

One shared brain for your coding agents.

A memory and skills layer your agents read and write — so what one learns, the next one already knows. No API keys, no cloud: it drives the tools you already pay for, on your machine.

open source · local-first · works with the agents you already use

shared context · one project
— a Claude Code session
> fix the flaky staging deploy
  done. `npm run lint` drops into an interactive setup
  prompt and hangs — used `npx tsc --noEmit` instead.
✎ memory_write   saved to shared context
 
— a Codex session, the next day
> how do I check the web build compiles?
▸ memory_search
  Run `npx tsc --noEmit`. Avoid `npm run lint` — it isn't
  configured and hangs a non-interactive agent.

Claude wrote it. Codex read it. The fact lives in no file — only in the shared store, on your machine.

What's inside

the shared layer

One store. Every agent you use.

Connected through open surfaces — MCP, AGENTS.md, session hooks — so adding an agent is a small adapter, not a rewrite.

Claude Code Codex any MCP agent reads AGENTS.md

No API keys

Every model call runs inside the official CLI under your subscription. uac reads and forwards nothing.

Shared memory

Decisions, gotchas and conventions — the why that isn't in the code. Written by whichever agent learned it, read by both.

Shared skills

Write a procedure once. Claude gets it natively; Codex gets it over MCP. One source, both agents.

Across projects

Link one project's memory into another — read-only, one-way — so conventions travel without copy-paste.

Use it however you work

Nothing new to learn in Claude or Codex — they read the layer through MCP and hooks. Or drive both from the VS Code extension or the terminal app, switching agents without losing context.

Same agents. Shared brain.

What changes when they stop working in isolation.

Agents on their own With uac
What one agent learns, the other knows
Skills usable in both agents
One source of truth for instructions
Reuse another project's context
Runs locally, no API keys

Three commands to a shared brain

$ uv tool install unified-agent-context
$ cd your-project
$ uac init   # registers with Claude Code and Codex

Then have one agent save something, and ask the other about it.