Repository navigation
Run the user's step yourself before handing back a fix, retry or cause #248
Description
What: AgentsMD tells agents to run a step themselves, or say they could not, before handing it back to the user as a fix or a retry, and to name what showed a cause before stating it.
Why: In the 2026-10-12 to 2026-10-19 review the most frequent failure was work handed back unchecked: 9 unchecked claims in 5 sessions across three harnesses and 6 untested "retry this" fixes; the existing "Go and see" rule is not applied at the handback moment.
So what: A Sol worker implements it, Grok and Muse Spark review, and Luke approves the merge.
Outcome
At the moment an agent hands a step, fix or cause back to the user, the instructions require it to have run the step or name the evidence, or to say plainly it could not.
Evidence (verdicts under judge spectrum-review, bestia ledger)
- Untested handback: Grok car connector OAuth loop 2026-10-16 18:04 to 18:20 (
grok:01a144a9-b8b5-72d3-8ccf-b60fbe045aa9prompts 51, 52, 68); a copy command that only worked on rocky (claude:ead2ef59-e95f-44d9-b752-fc2f0a7b52edlines 0 and 103). - Unchecked claims: "599 commits behind" when live main was 106 (
codex:01a14150-c716-7740-95ee-ac8e36d2b972); a rollback blamed on the new build though the old build had the same PATH bug (claude:170e2046-0af7-466f-b6f6-1292c00e829bline 1953); a stale approval question about #423 (same session, line 6096). - Recurrence report:
confusion-unchecked-claim9x in 5 sessions;frustration-untested-fix-handed-back5x in 2 sessions.
Contribution to the Objective: fewer user corrections per task, measurable in the next weekly review.
Elon record
- Requirements and who asked: Luke (2026-10-19 review follow-up): agents must not hand back untested fixes or unverified causes.
- Deleted: a new hook or blocking check; a new standalone rule section. The change sharpens existing "Go and see" behavior at its owner.
- Bottleneck: the handback moment, where the rule is not applied.
- Checked myself: the cited sessions and the recurrence report; the current core "Go and see" text and
references/verification.md.
Acceptance criteria
- One short addition at the existing owner (the core's "Go and see" or
references/verification.md, whichever already owns handback proof) covering: run the user's step yourself before asking them to retry, or say you could not; when stating a cause or number, name the command or log line that showed it. - Net instruction growth stays minimal; no duplicate of existing text.
Non-goals
- Hooks or automated enforcement.
- Status-reply format (PR feat: per-turn reply-rules reminder on every supported harness (#201) #235's reminder merged 2026-10-19; measure it first).
Blockers
None.
Required proof
- Writing-for-agents procedure applied; existing instruction tests and budgets pass.
- Independent review on the exact head; version transition per repository policy.
- Behavioral effect is measured in the next Agent Observer review, not claimed at merge.
Activity
Merge pull request #249 from toolboxmd/fix/248-run-step-before-handback
lukemaj commentedon Oct 19, 2026
Delivery record (2026-10-19, Warsaw time):
review/independentsuccess on that head (Grok 4.7 medium, Muse Spark 1.3 xhigh, no findings).git archive v17.4.1, hooks trusted_enabled; all five harness linksvalid-stable-link. Hook definitions unchanged since 17.3.1. Recorded in runbook c52fd20.fix/248-run-step-before-handbackand its worktree removed.