the create-t3-app for agent workspaces

Give your agents
a world to work in.

A typed knowledge graph, a self-improving loop, and review by blast radius. Scaffold a structured, portable workspace your AI agent can actually navigate, verify, and improve. Plain Markdown. Any editor. Any agent.

$npm create @vivary my-workspace

MIT · Python 3.11+ · zero dependencies · on PyPI & npm

billing invoice checkout receipt auth emails
tropo blast billing  →  4 things depend on it. See impact before you touch it.

Every AI-agent project starts the same way: a pile of spec files, a notes.md, some “rules,” a memory dump. Then it rots. Vivary makes the workspace a known, structured, navigable thing, the way create-t3-app did for web stacks.

A self-improving loop running over a typed, navigable knowledge graph, with one visible state surface and human gates.

Four layers, named for the sky.

A vivary is a small self-contained world with stacked layers. Each one is a standalone, zero-dependency CLI. The baseline is the bottom two; the rest snap on when you need them.

  1. exosphere exo Coordination when one agent becomes many.
  2. the filter ozone Graph-aware review, by blast radius.
  3. stratosphere strato The agent OS: loop, state, memory, gates.
  4. troposphere tropo The typed knowledge graph. Ground truth.
  5. spaceground

Not just a folder of Markdown.

The graph is validated, opinionated.

tropo check is a gate, not a linter. Untyped docs, typo'd fields, and broken links fail. Your agent's context stays trustworthy instead of quietly rotting.

$ tropo check
changes/billing.md:3 error E101: missing required field 'status'
modules/auth.md:5 warning W220: ref 'sessoin' matches no document id
tropo: 12 document(s), 1 error(s), 1 warning(s)  →  exit 1

Review by blast radius.

See what a change touches, not just what lines changed. ozone review reads the whole graph; impact walks the dependents. The thing a text diff can't show.

$ ozone impact billing
billing  →  4 node(s) depend on it
  1  invoice    (change, via related_changes)
  1  checkout   (module,  via related_modules)
  2  receipt    (change,  via related_changes)

Start in one command.

$ npm create @vivary my-workspace   # pick: coding · second-brain · writing
$ pip install vivary-tropo vivary-ozone vivary-exo create-vivary
$ uvx vivary-tropo check   # or run without installing