Feature · Organization

Oversight

Review risks, failures and paused work with their evidence.

Last changed

Generated from commit be57775 ·

How it works

What it watches

Detectors run every minute where workers are enabled. They look for:

  • Spend: a spike against the recent average, a budget that will run out today, and single calls that cost much more than usual;
  • Loops: the same tool call again and again, repeated failures, review loops, stuck items and runs with no progress;
  • Failures: high error rates, and items that reopen or fail verification again and again;
  • Behaviour: actions outside a worker's history, bursts of outgoing messages, and writes into another department's work;
  • Catastrophic attempts: critical-risk actions, the kill switch, and secrets the outgoing check blocked.

Severities and responses

Each finding is Info, Warning or Critical. By default:

  • Info goes to the digest.
  • Warning notifies you and asks the responsible manager.
  • Critical pauses the worker or department and notifies you.

The Oversight page

Oversight shows findings, open findings by severity, spend by department and paused subtrees. Members can Acknowledge and Resolve a finding. Admins can suppress a finding for 1 hour, 1 day or 1 week, and resume a paused subtree.

Settings

The oversight.* settings hold the thresholds and responses. An owner or admin changes them in the organization settings list on Settings.

From the help article Oversight, checked against the product on .

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • oversightSummary

    Viewer

    Oversight summary.

    Types: EmptyRequest returns OversightSummaryDto

  • listFindings

    Viewer

    Lists findings.

    Types: ListFindingsRequest returns ListResponse<FindingDto>

  • acknowledgeFinding

    Member

    Acknowledges the finding.

    Types: FindingIdRequest returns FindingDto

  • resolveFinding

    Member

    Resolves the finding.

    Types: ResolveFindingRequest returns FindingDto

  • suppressFinding

    Admin

    Suppresses the finding.

    Types: SuppressFindingRequest returns FindingDto

  • resumeSubtree

    Admin

    Resumes the subtree.

    Types: ResumeSubtreeRequest returns { pause: SubtreePauseDto; workersResumed: number; itemsWoken: number }

  • listMembers

    Viewer

    Lists members.

    Types: EmptyRequest returns ListMembersResponse

Screens

What it records

The feature writes these events to the audit log, the permanent record of what happened.

  • Oversight finding opened
  • Oversight finding updated

Generated from code at commit be57775 ·

Turn the numbers into shipped work.

Agent runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.