The google-gemini/gemini-cli repo added the caretaker triage worker in commit c988cbb1e on July 7, with issue-quality skills, a triage orchestrator, Firestore issue locks, validators, and tests.
Maintainers should watch whether this becomes a visible issue-management lane, because the strongest source now shows agent triage being treated as a stateful worker instead of an ad hoc bot comment.
Facts
- The triage orchestrator marks issue bodies as untrusted context before asking quality, effort, and specification skills to produce one JSON result.
- The issue store claims Firestore locks, caps attempts, and routes exhausted work to
NEEDS_HUMAN. - A follow-up egress commit adds Octokit actions for comments, labels, and unlabels while refusing unauthorized repository targets.
Evidence
The public source stack is the triage-worker commit, the egress-handler commit b31b755bb, and the thought-scrubbing commit 27a3da3e, which shows nearby hardening of agent history.
Context
The practical movement is not that Gemini CLI solved issue triage. It is that a major agent CLI is carving issue intake into worker instructions, durable status, retry policy, and explicit GitHub side effects.
Limits
The commits do not prove the caretaker is live on the public repo. What to watch: whether issues start carrying caretaker labels, comments, or generated specs that match this worker contract.