Skip to content

Make 'agents intentionally paused' a first-class state — deliberate token disable presented as fleet-wide outage (2026-08-16) #1525

Closed

Description

@don-petry

Story

As a maintainer who sometimes takes the agent fleet offline deliberately (e.g. disabling CLAUDE_CODE_OAUTH_TOKEN to conserve quota),
I want "agents intentionally paused" to be a first-class, visible state,
so that a deliberate pause doesn't present as a mysterious fleet-wide outage — red dispatch runs on every event, silently stalled PRs, and hours of diagnosis to rediscover a decision the maintainer already made.

Problem — observed 2026-08-16→18

The maintainer disabled CLAUDE_CODE_OAUTH_TOKEN to limit token usage until the quota reset. Effects, none of which announced the cause:

Acceptance Criteria

  1. A single explicit switch (suggestion: repo/org Actions variable AGENTS_PAUSED=true, since variables are visible where secrets are not) short-circuits agent dispatch workflows (dev-lead, pr-review trigger paths) as an early exit 0 step with a ::notice::agents paused by maintainer (AGENTS_PAUSED) — runs conclude green/neutral, not red.
  2. When the required engine secret is absent and AGENTS_PAUSED is NOT set, the dispatch fails fast with an error that names the secret and links this issue — one clear line, not a secrets-evaluation stack error.
  3. scripts/validate-engines.sh (already the engine-availability preflight) recognizes and reports the paused state distinctly from a misconfiguration.
  4. The fleet monitor treats paused runs as healthy/neutral, not failures.
  5. Docs: one paragraph in AGENTS.md on how to pause/resume the fleet deliberately.

Dev Notes

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementFeature requestsinitiativeEpic / initiative tracking issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions