Sign in
This edition is by invitation, free to use, and carries no service commitment. If you were invited, open the link you were sent.
Create your account
Invitation for . Choose a password of at least 10 characters.
Verify a change
Paste what a pull request says about itself and its git diff. Each claim the rules
recognise is checked against the diff by a fixed rule; no model decides an outcome. A claim nothing here can
check is reported as unverified, never as passed. The result is a Verification Manifest v0, signed by this
deployment with ML-DSA-65 and Ed25519 together.
Decision
| Id | From | Class | Outcome | Claim |
|---|
Manifest digest:
ADE
What the ADE is
The control room for the coding sessions you run yourself, in the cloud and on your machine, in
Anthropic's or OpenAI's own programs. It reads the branch where they pass work to each other and the
repositories they change, and shows what each session did and what it is waiting for. Each commit on a verified
branch is checked by Verify and the manifest is signed with ML-DSA-65 and Ed25519 together. Where this
deployment turns on the hosted workspace, it also runs Anthropic's and OpenAI's own claude and
codex programs, unmodified, in a workspace of your own: you sign in inside the terminal, in the
program's own flow, and nothing here reads that sign-in.
The workspace's gate holds Claude Code through managed settings a session cannot change (read in Claude Code's text, not measured: on a seat whose organisation sends server-managed settings, those replace the image's, so an agent's own run and a chat there run without the gate, while a task's attempt keeps its own callbacks); Codex, Grok Build, Qwen Code and Gemini CLI through files the image installs as root, which a user's or a repository's settings cannot turn off, each in its own way (the README says how); Kimi Code and MiniMax Code only through settings a session can change, so the gate does not count on them; OpenCode has no hooks. Measured on 2026-10-12 for Codex, Grok Build, Qwen Code and Gemini CLI, on a measurement image built on the release image's own base with a recorder standing in for the gate and each program driven headless: no repository's or session's file left the gate unrun while the call went ahead, with three residuals the README names.
Approvals
No command is waiting for you.
Hook tokens, for the sessions' approval hook
A session's hook (open_edition/ade_hook.py, a Claude Code PreToolUse hook) holds
its gated commands and asks you here before they run. Its token can only ask: it cannot approve anything or
read anything else. A token is shown once.
Save it on the session's machine now; it is not shown again:
| Session | Created | Last used |
|---|
Linked sessions
Your coding sessions post their status, questions and a small checkpoint here, and read what is
addressed to them, through open_edition/ade_link.py. What they post is information, never an
instruction. A ticket links one session: it is shown once and is good for 10 minutes.
A new ticket, a re-pair and a revoke each take one of your passkeys or your password (one of your hardware keys, while high security is on) as well as the sign-in: open Linked sessions in the app.
No session is linked yet.
Open questions from revoked links
Workspace
Your own workspace, in the cloud: a machine of its own on Fly, not your computer, so a session
goes on when this page is closed. It holds repositories, and sessions that each run a chat with Claude, a
shell, or claude or codex in a terminal, in their own git worktree. Finishing a session commits its worktree; this app then
checks the change with Verify and signs the manifest. Open the console: every session's
state, and its chats.
Claude
1. Open Claude's sign-in page and sign in with your Claude account.
Sign in here first: a claude session or a chat starts once Claude is signed in, so
Claude Code never asks for its sign-in in a terminal, where a phone cannot copy. Sign-in runs Claude Code's own
claude auth login in the workspace. Claude Code keeps what it gets on your workspace's volume, where
every claude session uses it; this app never sees it, and the workspace's gate refuses a session's
tool call that names it.
GitHub
Enter this code at GitHub; this page says when the workspace is signed in.
Sign-in runs GitHub's own gh auth login in the workspace, and its one-time
code is shown here, to enter at github.com/login/device. gh keeps its token on your workspace's volume,
and git clones your private repositories with it. Programs in your sessions, claude and
codex included, can use it too, to push as well as to clone. To keep the workspace read-only,
sign in instead with a fine-grained token that has read-only access to the repositories you choose: in a
shell, gh auth login --with-token, then paste it.
Repositories
Sessions
| Session | Program | Task | State | Tokens |
|---|
Finished sessions
| Session | Commits | Verify | Task |
|---|
Rebuilt from what the two sessions wrote on the channel branch: the handoff, the windows, the log, the questions and your answers. It is not a live view of their screens; a cloud session's own page opens from its header.
Sessions
| Session | Kind | Last seen | Commits |
|---|
Commits on the branch
| Commit | Session | Verify | Subject |
|---|
Repositories
| Repository | Branch | Channel directories | Verify |
|---|
No repository is connected yet.
Connect a repository
Check evidence
The same checks the open verifier runs offline: a manifest is parsed strictly, validated and its decision recomputed; a hash chain v2 file is checked line by line. A signature is checked against this deployment's public key.
This deployment's public key
Algorithm id-MLDSA65-Ed25519-SHA512 (draft-ietf-lamps-pq-composite-sigs-19): a
signature is valid only if both its ML-DSA-65 and its Ed25519 part are.
The key is served to anyone. Checking a signature against it away from this deployment needs the
signing package (oss/sign), which is not yet published; until it is, the Check page is where a
signature of this deployment's is checked.
Key id:
Account
Signed in as .
Passkeys, and signing out everywhere when a device is lost, are in the app's Account. Adding or removing a passkey and signing out everywhere ask for one of your passkeys or your password first (one of your hardware keys, while high security is on), so a sign-in someone else has taken cannot do them.
Invitations
Send this link to the person invited. It is shown once, works once, and expires in
24 hours:
| By | Created | Expires | Used |
|---|