Workspace
Your surface, your layout. Drag and resize the panels, add any from the registry, or tell the agent what you're doing and let it compose for you. There is one layout manifest underneath — you write it by hand, the agent writes it by intent, both as deltas against the same vetted set. Every agent move is yours to undo. It lives on your node; nothing here executes and nothing leaves.
Semios
Your intelligence, on your silicon. Every turn is routed local-only and stamped with its confinement — never Anthropic, never a round trip you didn't own.
connecting to your local intelligence…
Memory
Owned. On your node. Content-addressed in the FactStore, gossiped across your surfaces over iroh. There is no context window here — nothing is forgotten when a session ends.
Content by address
Any owned blob, rendered here through your own bridge — image, text, or file — no CLI, no external host. The address is the proof: the bridge re-hashes the bytes on the way out.
Submit
Drop in something — a note, a draft, a file. The engine analyzes it on your own silicon, tells you what's valuable about it for AI training, and suggests tags. You adjust the tags, keep what you want, then commit it to your corpus.
1 · what are you submitting
Your corpus
Mesh
The same Semios on every surface, kept consistent by iroh — encrypted, peer-to-peer, no certificate authority. This is what "consistent across surfaces" is made of.
This node
——Surfaces in your mesh
- loading…
Add a surface
Bring another machine online as a node — the installer is signed by this principal, no hex paste, no operator restart.
Open node onboarding →Operate
The Semios administrative interface — your substrate's vitals, read live from the bridge. No Anthropic session required to run your own system.
Repository
Bridge
Intelligence
Recognition
Presence
Telemetry
Session delta
Deployment
Genesis Node pre-beta state — the same answer the public dashboard renders, served from this bridge's FactStore. Every refresh is a content-addressed snapshot, gossiped across your mesh by iroh.
Critical path · longest open chain
Next actions · sorted by unblock count
GRW decisions · awaiting
CHK ladder · α → π
Live surfaces · HTTP probes
Recent activity · last 6 commits
Snapshot history · last 12 refreshes
Your node
One non-extractable key, generated in this browser, never leaves it. It is your identity on the substrate — no account, no password, no email.
Principal
———loading identity…
Why this is different from a cloud login
Your private key is created with WebCrypto as non-extractable — the bytes never exist in JavaScript and never reach a server. The bridge only ever sees signatures it can verify against your public key.
That is the whole on-ramp: session_open is a signature, not a credential handed to someone else. The substrate is something you own, not somewhere you have an account.