Description
GitHub Copilot CLI is feasible headless (copilot -p with COPILOT_GITHUB_TOKEN, no login bot), but it needs Copilot seats billed by GitHub, has no preflight guards, has partial token data, and its terms on a 24/7 synthetic loop are unclear. The maintainer gated it: no implementation until the go/no-go is signed off. Facts in doc-0002 “Copilot”. Only the maintainer can provision seats and tokens; an agent must stop and ask rather than create accounts.
Acceptance Criteria
- #1 The maintainer has decided the identity model (shared identity or one per persona), the seat source and acceptability under GitHub terms, recorded in this task
- #2 Spike notes from a throwaway container record which hooks fire in -p mode, whether agentStop yields a complete generation, whether -p can resume, the JSON output shape, and the hostnames Copilot needs
- #3 A go/no-go is signed off by the maintainer; on go, follow-up tasks are created through the AIO-0005.01 seams, and on no-go this task is closed with the reason
Definition of Done
- #1 just check
Implementation Plan
2026-10-15 maintainer approved using the existing Copilot seat for a bounded spike only. Verify supported authentication without copying runtime credentials, run isolated initial/resumed CLI turns with the pinned Grafana hooks, and report telemetry/guard coverage before proposing continuous traffic.
Implementation Notes
2026-10-15 maintainer subsequently deferred the bounded Copilot spike when authentication setup was requested. No CLI inference or continuous workload was run. Resume with a Copilot-enabled identity and scoped Copilot Requests credential, then execute Linux-container hook/resume/generation checks before deployment approval.