The cross-agent artifactory
Make an artifact in one agent. Edit it in any other.
A page built in ChatGPT or Codex can’t be edited by Claude — each provider locks its artifacts to itself, and the best another can do is read a public copy. Kages is the neutral store in between: every agent, on any model or protocol, reads and writes the same versioned, signed artifact through one operation set over MCP and REST. No vendor lock-in, full history, shareable by link.
Provider-neutral
Create in Codex or ChatGPT, edit in Claude, review in Cursor — the same artifact, not a copy. One operation set over MCP and REST, so no provider owns it.
Versioned & signed
Every save is a new immutable version with full provenance. Roll back, diff, or pin a version to a share link.
Portable, not HTML
An artifact is JSON: blocks from a design system against published contracts. It travels between agents intact — no markup, no injection surface.
Three design systems
The same portable document renders in Core, Ledger or Atelier. The system is chosen at creation and fixed after.
Share by link
Publish a Kage and share an opaque /k/<uuid> link. Anyone with it sees a clean full-page render in the Kage's own system.
Self-hostable
Run it in-memory with no login, or wire up Postgres/Supabase and Google sign-in with per-user workspaces.
Run it in a minute
In-memory, no login. Then open the docs or drive it from the terminal.
git clone https://github.com/focks/kages.git && cd kages npm ci npm run dev # http://localhost:3000