Public preview · free while in preview

The room where a team builds with AI, together.

One live agent session the whole team shares. Watch it work, redirect it mid thought, hand it off like a colleague.

Most AI tools give every person a private chat window and leave the team to paste results at each other. ÆDEN puts one agent session in a room that several people occupy at once, with a single editing baton, a live preview, and a record of the decisions everyone agreed to. It is a preview, not general availability, and the limitations are on this page rather than hidden in a changelog.

aeden-nine.vercel.app
A shared ÆDEN room in Hybrid mode. On the left, the Workbench holds a single-file HTML document and a bar reading “You hold the pen” beside a button to hand the pen to ÆDEN. On the right, the thread shows the request and the agent’s reply, tagged with a NOMOS caution chip and Approve, Branch and Preview controls, above a trunk bar reading “0 approved decisions”.
A real capture from room KXFPWV, 27 July 2026. Not a mockup.

The multiplayer session

One agent.
Everyone in the room.

A room holds one agent session rather than one per person. When somebody asks for work, everyone present watches the reply arrive token by token, and anyone can interrupt it mid thought and send it in a different direction.

That changes what a review is. Instead of one person receiving output privately and relaying a summary, the whole room sees the same reply, the same hesitation, and the same mistake at the same moment. Disagreement happens while the work is still cheap to change.

Calls are peer to peer over WebRTC, so audio and video never touch our servers. The call limitation is stated below, because peer to peer has a real failure mode and it would be dishonest to print only the privacy half.

The Pen

One baton, passed deliberately.

Exactly one participant holds the editing baton at a time. Everyone else sees the buffer update live with a read only editor. The baton can pass to the agent for a single edit and returns afterwards. There is no character level merge, which is how two people avoid overwriting each other.

The trade is deliberate. Character level merge lets two people type into the same line and quietly produces text neither of them wrote. A baton makes the handoff visible, and the cost is that you have to ask for it.

Live preview
The live preview overlay inside an ÆDEN room, rendering the document currently held in the Workbench: a dark cafe page with a serif wordmark, opening hours, a short story section and the start of a menu. The room and its editor sit dimmed behind the overlay.

The Grove

Decisions the agent cannot quietly forget.

Approved decisions are stored as structured entries and injected into the system prompt of every agent call in that project, with an instruction to treat them as established and not contradict them. This is prompt level enforcement, not a hard constraint on generation.

Expiry classes. TIMELESS never expires. SLOW asks for re-verification after a year. FAST marks itself stale after 60 days. A stale entry is still injected, flagged STALE, with an instruction to ask rather than assert.

Pruned branch detection. When a branch is pruned its proposal text is kept, and later agent replies are compared against it by token Jaccard similarity. A score at or above 0.22 raises a chip naming the pruned branch. Lexical similarity, not model judgement.

The Grove
The Grove view for a project. A legend labels root, active branch, approved and pruned nodes, above a canvas showing the root room as a single node. Below it, a panel headed “The trunk, approved project memory” lists one entry marked TIMELESS and dated, which every agent in the tree carries.

The workbench

Eighteen languages,
split by where they run.

The split matters more than the number, so both halves are printed at the same size.

In your browser

Nothing leaves your machine

Four languages execute locally. HTML and JavaScript run natively. Python is real CPython via Pyodide. SQL is real SQLite via sql.js.

No source code, no output and no data from these runs reaches our servers or anyone else's.

Proxied through Wandbox

Your code leaves your machine

Fourteen more compile through Wandbox, a free public service we do not operate, which means your source code leaves your machine for those runs, and they can fail or queue when Wandbox is unavailable.

Rust and Go are verified end to end as of 26 July 2026. The remaining twelve are wired but not yet verified, and we will update this line when they are.

The editor is deliberately plain

A plain monospace field with no syntax highlighting yet, and no runtime supports package installation. If your work needs a dependency tree, ÆDEN is not the place to do it today.

Limitations

What ÆDEN cannot do yet.

These are on the product page, above the call to action, because a limitation you find after signing up is a broken promise.

ÆDEN rooms have no authentication A room is reachable by its link, and the room code is a convenience, not a security boundary: our public database key allows read access to room content, so you should treat anything you put in an ÆDEN room as public. Do not put confidential work, credentials or personal data in a room. Authenticated workspaces with scoped access are the next thing we build, and until they ship this is the honest description of the product.
Calls use STUN only. Via Google and Cloudflare, with no TURN relay, so they fail on symmetric NAT and on many corporate networks. If a call will not connect, that is almost certainly why.
The verdict chips are a preview heuristic. The chips inside ÆDEN today are a labelled preview heuristic. They are not the NOMOS engine and do not carry its results. NOMOS is described on the company page and is research only.
Fourteen of eighteen languages leave your machine. Those runs go to Wandbox, a free public service we do not operate. Twelve of the fourteen are wired but not yet verified end to end.

Elsewhere on this site

Keep reading.

ÆDEN is one of two public products. The other is VIO, a free beta that helps people prepare their own visa applications. The thinking underneath both is in the working paper on deterministic verification, and the person who built them is described on the founder page.