An analyse-stage agent can end normally without invoking the finish tool, producing agent idle and parking otherwise recoverable work. Add a bounded, deterministic recovery path that preserves explicit workflow completion and does not accept an unverified model final response.
Notes
Follow-up: the recovery wiring is correct inside archie-agent, but a separate architecture bug remains: embedded NATS still falls back to daemon-local execution. Tracked by the new NATS-only execution issue.
Close reason
SDK v0.1.22 provides one bounded forced-finish recovery; Archie opts in through InProcessRunner. Focused test, task check, module verification, and independent adversarial review passed. Re-verified 2026-08-24: the opt-in moved from the deleted InProcessRunner to agentexec.NewLoopRunner (loop_runner.go:106 CompletionForceFinish), which is what the archie-agent worker constructs; ai-sdk still v0.1.22. [Closure restored 2026-08-24: originally closed 2026-08-24, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]
Imported from beads archie-core-dfck · GitHub #623 · type bug · priority P2 · created 2026-08-24 · closed 2026-08-24
An analyse-stage agent can end normally without invoking the finish tool, producing agent idle and parking otherwise recoverable work. Add a bounded, deterministic recovery path that preserves explicit workflow completion and does not accept an unverified model final response.
### Notes
Follow-up: the recovery wiring is correct inside archie-agent, but a separate architecture bug remains: embedded NATS still falls back to daemon-local execution. Tracked by the new NATS-only execution issue.
### Close reason
SDK v0.1.22 provides one bounded forced-finish recovery; Archie opts in through InProcessRunner. Focused test, task check, module verification, and independent adversarial review passed. Re-verified 2026-08-24: the opt-in moved from the deleted InProcessRunner to agentexec.NewLoopRunner (loop_runner.go:106 CompletionForceFinish), which is what the archie-agent worker constructs; ai-sdk still v0.1.22. [Closure restored 2026-08-24: originally closed 2026-08-24, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]
---
_Imported from beads `archie-core-dfck` · GitHub #623 · type bug · priority P2 · created 2026-08-24 · closed 2026-08-24_
sam
added the mediumbug labels 2026-10-27 13:39:46 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
An analyse-stage agent can end normally without invoking the finish tool, producing agent idle and parking otherwise recoverable work. Add a bounded, deterministic recovery path that preserves explicit workflow completion and does not accept an unverified model final response.
Notes
Follow-up: the recovery wiring is correct inside archie-agent, but a separate architecture bug remains: embedded NATS still falls back to daemon-local execution. Tracked by the new NATS-only execution issue.
Close reason
SDK v0.1.22 provides one bounded forced-finish recovery; Archie opts in through InProcessRunner. Focused test, task check, module verification, and independent adversarial review passed. Re-verified 2026-08-24: the opt-in moved from the deleted InProcessRunner to agentexec.NewLoopRunner (loop_runner.go:106 CompletionForceFinish), which is what the archie-agent worker constructs; ai-sdk still v0.1.22. [Closure restored 2026-08-24: originally closed 2026-08-24, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]
Imported from beads
archie-core-dfck· GitHub #623 · type bug · priority P2 · created 2026-08-24 · closed 2026-08-24