Policy & instructions
Set project-wide instructions, ownership leases, and recovery rules.
Workspace
Project overview
A quiet view of what is ready, active, and waiting.
Projects
Open tasks to manage work. Use a project's gear button for settings and repository binding.
Loading projects…
Project
These settings apply across the project.
Review & integration
Choose who reviews submitted work and whether integration needs human authorization.
Required checks
Configure the validation checks required before code can be integrated.
Integration owner
Who publishes approved code to the target branch.
Integrator reports
Findings the integrator recorded, such as privilege gates and flaky checks. Resolve the ones that need a person.
Attention digest
What the attention budget did on its own and what still needs a person. Opening it here records that you read it.
Autonomy
Human-required interventions, parked items, cost against the daily caps, review outcomes, canary history and digest status, each with its source.
Connected sessions
Agent sessions still working in this project. Check them before a test, preflight or cutover.
Archive project
Hide this project from the project list while keeping its tasks and records. Restore it later from Archived projects. Claimed work, reviews and integrations must finish first.
Repository binding
Download this non-secret file, then place .agent-coordinator.toml in the root of your repository so agents connect to this project.
Workspace
Archived projects
Archived projects keep their tasks and records but are hidden from the project list and cannot take new work. Restore one to bring it back.
Integrator reports
Findings the integrator recorded for this project, newest first. A report that needs a person stops the integrator until a human resolves it.
Attention digest
Decisions that proceeded on their recommendation, the ones about to, and the interventions that need a person. Opening this page records that the digest was read; if it goes unread for several days the canary pages.
Autonomy
How much of this project's work runs without a person. Every figure links to the record it comes from: the attention digest, the service's task and review records, or what supervisor hosts report.
Connected sessions
Open agent sessions bound to this project, most recently active first. Use this list to quiesce agents before a test, preflight or cutover.
Last activity comes from instruction acknowledgments, claims, heartbeats and checkpoints in this project; reads don't count. A session holding an active attempt is always listed, even after its lease lapses.
Execution
Task queue
Choose a project to inspect its work.
Blockers
What is waiting on a person or a prerequisite, with a link to where it is cleared.
Select a project to load tasks.
Task history
Archived tasks
Archived work is kept separately from the task queue.
Choose a project to load archived tasks.
Loading task…
Task · Revision
CLI commands
Run these from a checkout bound by .agent-coordinator.toml. Commands are read-only unless marked as taking ownership.
Task brief
Acceptance criteria
Ownership
ObservedDependencies
Direct prerequisites and the tasks waiting on this one.
Task attachments
Upload up to ten images or files, 16 MiB each and 64 MiB total. Files are retained for 90 days by default. Agents should inspect and download relevant attachments before implementation.
Evidence packet
Download this task's criteria, submitted evidence, candidate identity, reviews, integration results and artifact references as a portable file. Artifact contents are referenced by SHA-256, not embedded. Credentials, sessions and reporter identities are never included.
Complete task history
Browse all preserved records, including earlier attempts and review or integration activities.
Lifecycle changes
Why this task was canceled, archived, restored or deleted, and what replaced it.
Checkpoint trail
Progress shared by the active or previous attempt.
Submission & completion
Review and checks apply to a specific candidate. Code completion requires validation of the integrated result.
Jobs & resource holds
A missing observer does not prove a job stopped. Holds remain until explicitly released or resolved.
Shared capacity
Resources
Resources represent limited capacity shared by agents across every project: for example, an exclusive test database, a licensed device, or a validation workstation.
How resources coordinate work
Define a resource before jobs need to compete for it. An agent reserves all required units before it starts its work and releases them only after the related job has terminal evidence, so another agent can safely use the available capacity.
A reservation coordinates access only. It does not start or stop a job, and it is not proof that a job has run or finished.
Define a resource
Use the edit icon in the table to change a resource, or the delete icon to remove one that no reservation has used.
Loading resources…
| Key | Description | Capacity | Held | Available | ID | Actions |
|---|
Administration
Access & credentials
Issue a coordinator credential for an agent and revoke it when its work ends.
Admin access is limited to administrator accounts.
Server clock
Restore status
Operator accounts
Issue agent credential
Issue a credentials.toml file for the native client. Keep the downloaded file private.
Install this file in the client’s protected credential directory. Dismissing or leaving this page removes the download link; it does not delete a saved file.
Download credentials.toml againCopy this token now
Issued credentials
Revoked credentials cannot create new sessions.
Loading credentials…