A clear view of the work.
What needs a closer look, what’s running, and where spending adds up.
Needs attention
Observed exceptions, with a next step for each. Related signals may describe the same problem.
Work in progress
—
A quick way in
Follow a spending flag, inspect a delayed job, then see the rules behind the numbers.
Data coverage
Understand your setup →What this view tells you
A snapshot of available session logs and configured registries. Refresh to read them again.
Budget breaches show spending above a limit. They do not prove a session was stopped.
Work sessions
Review individual runs of agent work. “Active” reflects recent log activity, not a process health check.
| Work session | Project | Model | Status | Spending | Review notes |
|---|
Spending
Estimated USD from recorded model usage and the pricing table, across all available history. These are not billing invoices.
By session start date UTC · full session cost attributed to its start date
By project all scanned history · configured project limit shown when set
Scheduled work
Check reported job status and delayed activity. Schedules come from your registry; this page does not create or run jobs.
Scheduled jobs
| Automation | Status | Schedule | Since last success | Detail |
|---|
Job locks
A lock marks work claimed by a job. An orphaned lock may remain after its process ended.
| Lock | Automation | Host | Age | Status |
|---|
Service check-ins
Reported activity from services. A stuck check-in means the same phase has lasted longer than expected.
| Service | Phase | Time in phase | Status |
|---|
Issues
Recorded problems from your error registry. Review the details and follow up in the system that owns the work.
| Issue | Priority | Status | Follow-up |
|---|
Budget rules
Recorded history compared with configured limits. This is a read-only evaluation until you explicitly record breaches.
Recording adds these observations to Issues. It does not block or stop execution. Enforcement requires a connected runner.
| Type | Scope | Limit | Actual | Observation | Detail |
|---|
Settings
Adjust spending limits and inspect the connected configuration. Process actions require explicit confirmation.
Spending limits
Blank or zero disables that limit. Saving updates these limits and the configured action. The hook blocks tool calls only when separately installed. “Kill” is a legacy setting and does not automatically stop a process; use the confirmed process actions below. Hook installation is not verified here.
Pricing table
Rates used for spending estimates. Expand to see the source file and model prices; edit that file to change rates.
Pricing source and model rates
Managed process allowlist
Only listed processes with an allowed action can be stopped or restarted. You will review the exact process and action before confirming.
| Name | Manager | Identifier | Kill | Restart | Action |
|---|