A control room for coding agents
Run coding agents from one browser tab — and always know which one actually needs you.
Workain runs real Claude Code and Codex CLI agents in parallel, in a browser tab, on your own provider subscriptions — with a status board that only ever tells you what it can prove. The agents and your code run in a workspace you control — your own machine or a dedicated box we host — never inside the LLM provider's cloud; only the model calls go out.
You keep 2+ CLI sessions going and alt-tab between terminal panes to find the one that needs you. Workain is the fleet view those terminals never had — same agents, same subscriptions, one honest board.
You want a coding agent working for you, but the CLI setup — terminals, auth, tmux — isn't your thing. We hand you a workspace with the agent already running: open a tab, type what you need.
You need agents your team can actually see: workspaces provisioned per person, provider accounts managed in one place, one status board across everyone's sessions — all in an environment you control, not the model vendor's.
Against the tools you already use
What's actually different here
Not a feature list — a direct contrast against Claude Code's own CLI, ChatGPT, and the closest real competitors.
A status board that never lies to you
Four primary states, each requiring positive evidence before it's shown: working, idle, your turn, problem — plus explicit infrastructure states (like "no report received") shown as exactly that, instead of being guessed into one of the four. A session mid-tool-call stays working for however long that genuinely takes — never flipped to a false "done" because the screen went quiet.
Real files, not an ephemeral thread
Every session here works out of a real folder on disk, in your own controlled workspace — not in a sandbox at the model vendor. What it produces is a real file you can browse independently of the chat that made it — days or logins later. Close the tab, come back tomorrow: the project → folder → session tree and everything in it is exactly where you left it.
Your subscription. Your vendor choice. Every session.
Every session is a genuine native CLI process authenticated with your own account — never a key this product holds on your behalf, never a shared house account. Run Claude Code and Codex side by side in the same workspace, switch providers per session, and each session's provider traffic goes straight from that session to the provider — nothing pooled, nothing re-routed. See the architecture that backs this ↓
The real competitors, addressed directly — not dodged
Conductor runs Claude Code and Codex in parallel worktrees well, but it's a native Mac-only app — one install per machine. Agent Deck is closer in spirit — self-hosted, built on tmux like we are — but it's a terminal TUI you install and run per machine (its web view is local-only, not a hosted one you can reach from another device). Workain is a browser tab: no install, no OS requirement, check your fleet from whatever device you're on right now. During early access your sessions run in a workspace we provision on a dedicated machine — self-hosting on your own box is where the model is heading.
See it for real
Real captures of the current build, taken in a demo workspace we set up for this page. The states are genuine — the crash below really crashed — but the scenarios were staged for legibility, and the app UI still wears the product's original working name, harness-control, until the in-app rebrand lands. Click any screenshot to enlarge.
How it's built
Genuine processes. Nothing routed through a shared key.
Workain orchestrates the same native CLI binaries you'd run over SSH — it just gives every session a real place to live, a real status, and a browser tab instead of a terminal multiplexer.
Plainly, on hosting: during early access your workspace runs on a dedicated machine we operate — your provider logins stay yours, and each session's provider traffic goes directly from that workspace to the provider. Self-hosting on your own box is where the model is heading. Source is closed during early access — every architecture claim above is verifiable by testers directly against a running workspace, and we're glad to walk through the design on request.
Not just this product
We research every layer of the agent harness — and test the claims
Workain is both the company and this product — and behind it runs our research program into every layer of an agent harness: the instructions and identity an agent runs with, its tools and skills, the memory and data behind it, and the gates that keep it honest. The first component class we've fully live-evaluated is memory systems; the rest of the catalog is being worked through the same pipeline.
The harness equipment registry
A structured, sourced catalog of agent-harness components and bundles — and, where we've actually run the benchmark ourselves, an honest tier verdict instead of a vendor's own claim.
Of the 11 memory systems cataloged, 6 are live-tested and 7 carry tier verdicts — one (OpenAI's Conversations API) is tiered from source review because there is no client-side algorithm to run, and its entry says so. Best result to date: tier B (Anthropic's own Memory Tool) — nothing has earned an A yet, and the entry says so.
github.com/workain/agent-harness-registry →The registry is opening up publicly right now — if the link above still says 404, the public flip is mid-flight; early-access testers get a walkthrough today either way.
Notes & findings
Short write-ups from actually running this stuff, not vendor claims. All posts →
- Nothing is obvious to an agent until it's in the file A factorial study, a presence-effect RCT, and our own fleet's task history, argued through to what actually earns a place in an agent's instruction file.
- Git worktree isolation for agent sessions, shipped in one release Sessions can now run in their own git worktree instead of a shared checkout. What it buys you, what it costs, and the internal incident that decided the cleanup had to ship in the same release, not later.
- The tab-switching tax: what actually breaks past 3 sessions It's usually not the agents costing you time once you're past two or three at once — it's re-establishing context every time you switch panes.
- We live-tested 6 memory systems and tiered 7. Here's the scoreboard. A live benchmark against a bare-model floor and a flat-file baseline. One leader — narrowly — and one real surprise.
- Why we test everything live before we recommend it A claim from a summary or README never gets cataloged as fact until it's re-confirmed against the primary source. Same bar we hold our own product to.
News
What's new
- 2026-07-22 Sessions now run in a separate git worktree by default, reducing accidental file/branch collisions with other sessions in the same folder. Checkbox and branch picker in session creation, branch badges on folders/sessions, an orphaned-worktree view in workspace settings; overridable per session, folder, or project. Automatic registration and cleanup ship in the same release. Write-up in the blog.
- 2026-07-20 Site refresh. Access requests and contact now send straight from the page, screenshots open full-size, and the research registry is linked from the front page. Memory scoreboard updated: 6 live-tested, 7 tiered.
- 2026-07-18 First research write-ups published. The memory-systems scoreboard, field notes on running multiple agents, and our test-everything-live methodology — all in the blog.
- 2026-07-18 Early access opens. workain.ai goes public and the first tester cohort starts onboarding, by hand, a few at a time.
Not asking for access
Other ways to reach us
Found a mistake in something we published? Have a security report, a press or partnership question, or something else that isn't "I want a workspace"? Use this instead of the access-request form below — it goes to the same inbox, read by a person.
Sends straight from this page to our inbox — no third-party form processor involved. Prefer plain email? hello@workain.ai works too.
Early access · Free while we onboard the first testers
Currently onboarding a small group of testers
Request access
We're bringing on the first testers by hand right now, a few at a time, while we finish hardening the fleet — free for the length of early access. Every request is read by a real person, not a queue. Tell us what you're running today and we'll set up your workspace.
Sends straight from this page — the inbox behind it is read by a person, not a queue. Prefer plain email? hello@workain.ai is the same pipeline.
No customers or testimonials yet — we're genuinely pre-launch, so you'd be among the first hands-on testers, not case study #40. Every claim on this page is checkable by testers directly against a running workspace, and the registry's public slice is being prepared right now.