Get Early Access
Magyverse · live

Magy

Infinite agents.
Infinite worlds.
Any work.

A team of AI engineers, embodied in a world you build. They delegate face to face, learn what they don't know, and ship a pull request while you watch.

  • Aria CTO
  • Juno PM
  • Nova Lead
  • Kai Dev
  • Zara Dev
  • Luna QA
  • Atlas Ops
  • +∞

Live activity

  • Nova walks to the library
  • knowledge graph +14 facts
  • Kai delegates to Zara
$ magy delegate --to zara "extract the parser"
zara worktree acquired · feat/parser-extract
luna review approved → PR #482 opened

Get Early Access

Composer locked

This is where you'll assign work to your agents. Drop your email and we'll unlock it the moment the first build is ready.

One email. No spam, unsubscribe any time.

The differentiator

Not seven agents. As many as the work needs.

Every other multi-agent product ships a fixed cast. Magy ships a world measured at a hundred thousand — because ambient population is a closed-form function of time, not an integration.

“The server ships a seed instead of a population.”

Clients cannot drift apart, and an agent nobody evaluates costs nothing at all.

  • 100,000agents @ 60.0 fps
  • 1draw call
  • 25 Bper agent
  • 56.2fps on a phone
  • 322draw calls, scene
  • 0.14 µsper agent tick

Retention

They get better while you're asleep.

Agents walk to the library and read real books whose contents enter their knowledge graph. They sleep, and they dream. A server-side director keeps the world living at 1 Hz whether or not a browser is open.

“The user comes back surprised — oh, she went to the library while I was gone, and now she knows about X.”

Infinite worlds

The world is editable, all of it.

Open the in-world editor and move a desk, add a room, relight the scene — gizmos, multi-select, full undo. Or describe the change in plain language and watch it apply. Agents adapt without new code, because objects advertise what can be done with them rather than every interaction being hardcoded.

Under the hood

Rust, all the way down.

tokio · NATS JetStream · Postgres 16 + pgvector · four-tier memory · knowledge graph with confidence decay · cost-aware routing across 7 providers · worktree isolation → auto-PR · 48 tools · WASM-sandboxed skills · Telegram · cron

Straight answers

What's shipping, and what isn't.

  • Shipping

    Agents, MagyVerse, worktree isolation with auto-PR, four-tier memory, knowledge graph, per-agent model choice with your own keys across seven providers, Telegram, cron, skills.

  • Building

    Marathon mode's worker loop is a skeleton — it logs progress but doesn't yet dispatch real work.

  • Not yet

    Slack, Jira and Notion connectors are stubs. Pre-built binaries and the paid tier are next.

Get Early Access

Be first into the Magyverse. We'll email you the moment the first build is ready — one email, and nothing else.

One email. No spam, unsubscribe any time.