ok · diff

git:20260928.81caee6 to git:20260929.190173f

6 added, 4 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
name: ok
- description: Give blanket approval to the single most recent pending confirmation request in this conversation, so the user doesn't have to type it out. Use when the user invokes /ok.
+ description: Give blanket approval to the agent's latest pending confirmation request, or confirm the agent's latest result worked when it asked the user to verify. Use when the user invokes /ok.
---
- - Treat this invocation as explicit approval for the single most recent action the agent asked the user to confirm (e.g. a proposed commit, plan, or other approval-gated step) — proceed with exactly that action as proposed.
- - If nothing is currently awaiting approval, say so instead of taking any action.
- - This approves only that one pending request; any later proposal still needs its own confirmation (a new `/ok` or explicit approval).
+ - Read only the agent's latest message; a request from an earlier message that the agent moved past is no longer pending.
+ - If it asks the user to confirm an action (e.g. a proposed commit, plan, or other approval-gated step), treat this invocation as explicit approval and proceed with exactly that action as proposed.
+ - If it reports a result the agent could not verify or asks the user to test or check it, treat this invocation as the user's confirmation that the result is correct: record it as verified and take no further action, including no commit.
+ - If neither applies, say so instead of taking any action.
+ - This approves only that one item; any later proposal still needs its own confirmation (a new `/ok` or explicit approval).