Introduction
A self-hosted workspace to observe and intervene in bounded coding-agent attempts on GitHub issues, with mixed harnesses, visible policies and recovery controls.
Find work needing attention
Use Overview for complete filtered counts and automation observations. Open Work for owners, waiting reasons and PR context; inspect Repositories for intake, polling and overlaps. Factory views include mixed harnesses by default and have their own URL filters.
Finished tracking is not a measured delivery outcome. Escalation or an operator stop does not prove process termination. Unknown observations remain unknown.
Keep the actors separate
Agents propose plans for designated Leader decisions. Operators configure policies and perform protected interventions. Human PR review and merge follow repository policy. An eligible action is an observation, not authorization; the server checks the current principal and state again.
Manual work and native configuration
Harnesses lists implemented native pages and manual entry points. Teams, Live sessions and Agent Mail can be used without watching a repository or enabling autonomy. Native/project preferences do not select factory work. Coverage differs; see Multi-Provider and Codex CLI.
Current scope
This reference describes the integrated product source candidate. Earlier packaged releases and separately pinned runtime or pilot environments can retain previous navigation and capabilities; integrating source does not upgrade those environments.
Harnesses includes the versioned operations/readiness catalog for all five harnesses, bounded local configuration observations and guarded native pages. See the Providers API for the catalog contract. Native adapters remain provider-specific; catalog support does not create an editor or grant authority.
Configuration checks do not verify model access. Credential readiness remains unknown, and generic provider cards do not establish a team-slot session binding. Conditional operating support still requires the current identity, workspace and approval authority.
Feature pages describe the capabilities in the integrated source. A source update does not grant milestone or pilot acceptance. The manual Bridge trial is unperformed; pilot participants, human benefit measurements and timing comparisons are unavailable. Promotion, publication, paid execution and deployment require separate authorization.
Repository setup uses a guided, observation-only access and label check. Leader authority uses the preset's explicit leader_slot_id; slot order and descriptive Role text do not select it. Guided configuration keeps the saved configuration, the reviewed launch and the activation as separate steps.
Tech Stack
| Layer | Technology |
|---|---|
| Backend | Python 3.11+ with FastAPI |
| Frontend | React 19 + TypeScript 6 + Vite 7 |
| UI | shadcn/ui + Tailwind CSS |
| Charts | Recharts |
| Database | SQLite (async via SQLAlchemy + aiosqlite) |