Showcase; the app, running

One window. Whole workflow. Zero interruptions.

No slideware below; this is the shape of the running app: the editor, a real terminal, and a fleet that reports back. And in the middle, the piece nobody else has: a vault of OAuth accounts and keys that switches itself when one runs dry.

§1. The IDE

editor · terminal · fleet
unary. ~/dev/unary-code · main
fleet · 3 workers
lib.rs main.rs
// src/lib.rs; patched by the fleet, reviewed by you
pub fn reindex(root: &Path) -> Result<Index> {
    let mut idx = Index::open(root)?;
+    idx.watch(root)?.incremental();agent · coding-l2 · accepted
    idx.rebuild()
}

$ cargo test --workspace

   Compiling unary v0.4.1 (~/dev/unary-code)

    Finished `test` profile [optimized] in 11.8s

214 passed · 0 failed · 0 ignored

Every agent edit lands as a diff you accept or reject, every worker runs inside a token budget, and the verifier gets the last word before anything merges.

§2. The vault, live

multi-oauth · auto-switch
vault; anthropic 18,402 tok this run
oauth · work streaming

claude · logged in once · token refreshed locally

oauth · private standby

claude · logged in once · never asked again

api key · sk-…f3d9 standby

openai · plain keys rotate exactly the same way

streaming on “work”; one of three accounts in the vault.
the run never interrupted

switch at the tick; no login window, no lost context, no “please re-authenticate”.

§3. Steer it from anywhere

e2e encrypted

From the web app

Approve, redirect or stop a running session

The fleet keeps running on your desktop; you pick the session up in the browser and steer it mid-run.

From your phone

Start on the laptop, finish at the desk

QR pairing, no port forwarding; the relay only ever sees ciphertext, your code never touches it.

Pre alpha; by invitation
Watch it on your own codebase.

A page can only show you the shape. Ask for a key, connect two accounts, and let one of them hit its limit; then see what happens.