Continuous AI: A Navigation Map of Always-On Agent Workflows¶
Continuous AI groups the always-on agent workflows here — each a distinct application with its own trigger, authority, and data source.
"Continuous AI" is GitHub's umbrella term for running agents continuously inside a repository on schedules and events, producing reviewable artifacts rather than autonomous commits (GitHub Blog). The pages below share that always-on shape but differ in what fires them, what they are allowed to write, and what they read. This page is a map, not a merge: each member is its own application and stays a separate page.
The Continuous-* Family¶
These workflows run agents on a recurring loop or event stream against a codebase or backlog.
- Continuous AI (Agentic CI/CD) — agents run alongside CI/CD to handle judgment-heavy tasks deterministic rules cannot express, emitting reviewable PRs and reports.
- Continuous Documentation — agents detect documentation-code drift on schedule or push and open PRs that realign docs.
- Continuous Agent Improvement — an observe-categorize-update-verify loop that keeps AGENTS.md and skills accurate as the project evolves.
- Continuous Autonomous Task Loop — a self-directed loop that reads a backlog, executes each item via a ReAct inner turn, commits, and repeats with fresh context.
The Triage Family¶
These workflows continuously classify and route inbound work — issues, alerts, or security findings.
- Continuous Triage — agents summarize, label, and route issues on every event or schedule, with read-only defaults and constrained safe outputs.
- Auto-Triage Workflow — a monitor-correlate-investigate-propose-fix agent on alert streams that tags an owner or opens a fix PR, safe only under three named preconditions.
- Backlog Triage as a Named Agent Skill — a single skill that encodes a label state machine and emits a durable agent brief as the hand-off contract.
- AI-Powered Vulnerability Triage — decomposes security analysis into threat-model, suggest, and audit stages to suppress hallucinated findings.
How to Choose¶
Match the trigger to the family. A schedule or push against your own code points at the continuous-* family; an inbound stream of issues, alerts, or vulnerabilities points at the triage family. Within each, the distinguishing axis is authority: read-only classification (continuous triage), constrained writes behind preconditions (auto-triage, vulnerability triage), or full PR-producing loops (agentic CI/CD, continuous documentation).
Key Takeaways¶
- Continuous AI is a family of distinct always-on workflows, not one mergeable pattern — each member keeps its own page.
- Two sub-families: the continuous-* loops act on your own code or backlog; the triage family classifies inbound issues, alerts, and findings.
- Choose by trigger first (schedule/push vs. inbound stream), then by authority (read-only, preconditioned writes, or full PR loops).
Related¶
- Workflows index — the full catalog these families sit within
- Programmatic Cloud Agent Dispatch — the dispatch surface that fires many of these always-on loops
- Safe Outputs Pattern — the write-constraint mechanism the triage family relies on