Shared workspaces instead of disposable chats
Threads stay attached to the machine, path, approvals, previews, and execution history that produced them.
Commercial homepage
Shared AI workspaces for real machines.
Run Codex where the code already lives. Pair the machine, bind the real path, and supervise previews, approvals, and long-running sessions from one browser control plane.
Pair the machine that already holds the repo
Reopen sessions with path, preview, and approval context intact
Supervise from the browser or your phone without touching the filesystem directly
Keep localhost previews explicit, isolated, and server-brokered
Workspace live
checkout-recovery
Machine: `tomatoaws-web-1`Path: `/srv/project`
Active run
Review checkout recovery and prepare the commit plan
reconnect-safe
Model
Codex with browser supervision
Tools
Diff, approvals, previews, terminal
Continuity
Delta resume + event replay
Timeline context
server-authoritativePrompt, response, approvals, and preview events all stay attached to the same workspace.
Changing machine or path affects future turns only. Old events keep their original context.
Approvals
`git commit` requires approval before write access is granted.
Device pairing is approved from the browser, not silently from the desktop.
Preview
`preview.localhost:3000` is exposed explicitly, opened in an isolated origin, and relayed through the existing desktop socket.
Install/update
Signed metadata, local-by-default install, then pairing and long-running connection.
Desktop stays local
Server owns state
Browser owns supervision
Previews stay explicit
Why Eridai
Built for teams that need more than a chat window.
Cold buyers need to understand the difference immediately. Eridai is not another hosted AI tab. It is a control plane for running AI work on real machines, with enough structure to review, preview, and reopen that work later.
Local runtime, remote supervision
The desktop stays on the real Mac, Linux host, or VPS. The browser stays the control plane.
Preview and approvals beside the run
Open explicit localhost previews, approve actions, and inspect events without switching tools.
Recovery built into the model
Desktop replay, presence leases, and browser delta resume keep long-running work recoverable.
Operational difference
What Eridai keeps that most AI tools lose.
The repo path, machine identity, preview exposure, approval history, event stream, and reconnect story are part of the product model. That is why Eridai can feel serious where lighter tools still feel temporary.
Cold-buyer test
A serious buyer should see this page and understand that Eridai is for running real engineering work with stronger context and control, not for generating one more isolated answer.
Machine pairing and browser auth
Proof-bound machine auth, browser cookies with CSRF, and user-scoped actions across workspaces, machines, sessions, approvals, and previews.
Signed install and update path
Desktop install and update flows are brokered by the server and verified with signed release metadata instead of raw unauthenticated downloads.
Preview relay with explicit exposure
Localhost previews are saved exposures, not implicit tunnels. The browser opens an isolated preview origin backed by the existing desktop socket.
Workspace-native git and runtime context
Machine choice, path binding, repository inspection, and session continuity stay part of the same working surface rather than spread across tabs.
How it works
From install to handoff in one operating model.
The public site should show a real path into the product, not vague promises. Eridai starts with install and pairing, then moves into workspace-bound execution, approvals, previews, and reopenable supervision.
Step 01
Install Eridai where the work already lives
Generate a signed bootstrap command, install locally by default, and keep the runtime on the machine you already trust.
Step 02
Approve the machine from the browser
Device pairing is explicit. The desktop starts pairing, the browser approves it, and the server keeps the user scope authoritative.
Step 03
Bind a workspace to the real path
Workspaces and machines stay separate. Bind the path you want, keep standalone chats when needed, and avoid fake migrations.
Step 04
Operate, preview, approve, and hand off
Run the agent, inspect previews, manage approvals, and reopen the same operational context later from the browser.
Security and control
The browser never becomes a fake remote filesystem.
Eridai keeps the ownership boundary intact. The desktop owns local execution and localhost relay to its own machine. The server owns persisted truth and authorization. The browser stays presentation and supervision only.
Proof-bound machine authentication
Refresh and connect flows are challenge-based. Runtime scope comes from the server database, not client claims.
Explicit preview exposure registration
Preview access is created, opened, and revoked through saved server records rather than implied tunnels.
Workspace and machine separation
Deleting or rebinding a machine does not rewrite historical sessions. Old commands keep the context they were created with.
Signed desktop release access
Install and update flows verify signed metadata and checksums before switching the active desktop release.
Install desktop
Start with the real machine, not a sales contact form.
The public site can issue a short-lived bootstrap command right now. Install the desktop, pair the machine, and continue the workflow in the browser.
Local install is the default and supports `--global` when needed.
After install, the desktop continues into pairing and then the long-running connection flow.
Pairing approval still happens in the browser, so install does not silently grant access.
Signed bootstrap
Install command
Generate a fresh token any time. The command is public-install only; pairing and browser approval still gate the machine into the product.
Install command will appear here.
Choose Eridai
Run serious AI work where the code actually lives.
If the choice is between a cleaner chat surface and a real operational control plane, Eridai should look like the tool for the second job. That is the bar this page is designed to clear.