Runs stay attached to a repo instead of disappearing into fresh chats.
Approvals, checkpoints, browser state, editor context, and event history stay with the work so supervision does not depend on memory.
Multi-provider workspace for serious agent work
A real interface for supervising coding agents.
ace keeps the work legible while it is running: project threads, terminal context, browser checks, editor review, provider handoff, and recovery when long sessions go sideways.
Providers Codex, Claude, Gemini, Cursor, Copilot, OpenCode
Environment Desktop UI plus remote host sessions
Behavior Local-first, recoverable, thread-based supervision
Workspace view Conversation, browser, diffs, and execution state in one frame
Live supervision surface 
What matters
The run stays readable while work is happening, failing, and getting handed off.
What you can do
Inspect, redirect, approve, and recover without rebuilding context from memory.
What happens next
ace is moving toward persistent multi-agent workflows rather than isolated turns.
System
Everything you need to keep agent work under control.
ace keeps the important surfaces together so you can understand what is happening and decide what to do next without context switching.
Browser, editor, terminal, and diffs stay nearby while decisions are being made.
The operator does not need to bounce across windows to understand what changed, what failed, or what needs approval next.
Long sessions remain readable when streams break, reconnect, or restart.
ace is designed around the awkward parts of real agent work, not just the happy-path screenshot.
Dense histories and local context stay usable under load.
The interface is shaped for supervision of active work rather than lightweight prompt demos.
Providers
Switch agents without starting over.
Bring the provider accounts and CLIs you already trust. ace keeps the project narrative continuous while responsibility moves between agents.
Codex
Claude
Gemini
Cursor
GitHub Copilot
OpenCode
- 01
Start where the repo can actually run
Use local provider CLIs, attach terminal context, and keep execution on the machine that holds the code and tools.
- 02
Switch providers without losing continuity
Move between agents as the task changes while the same thread retains browser checks, history, approvals, and review state.
- 03
Monitor and steer from another device
Remote hosts keep work near the environment while the interface stays available on the machine you want to carry.
Remote
Run where the code lives. Check in from anywhere.
Host machine repo + provider CLIs
ace daemon session broker + thread continuity
Operator interface desktop or laptop
One heavy local machine running repo work with the full interface beside it.
Separate workstations, servers, or sandboxes available through the same workspace.
The host runs where the code lives while the interface stays elsewhere.
Roadmap
Built for longer-running, more connected workflows.
The direction is toward workflows that keep moving across providers and longer time spans without sacrificing inspectability or operator control.
Flow Mode
Coordinated multi-agent loops where providers can pass responsibility across backend, web, mobile, and test work without breaking the run narrative.
Skills
Reusable instruction packs and workflow standards so teams can shape agent behavior deliberately instead of reinventing prompts for every project.
Download
Put agent work in a workspace built to be supervised.
Install ace locally, keep the thread attached to the project, and stop spreading execution, review, and recovery across disconnected tools.