Document recovery procedures for agent issues

Added details on recovery procedures for agent states and hallucination detection.
This commit is contained in:
Levi Neely 2026-05-01 12:37:58 +02:00 committed by GitHub
parent c2b50509a8
commit aca064e810
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 0 deletions

View File

@ -81,6 +81,7 @@ The following transitions required manual user intervention (the user prompting
3. **Hallucination Detection**: The user identified the "CMake" hallucination and prompted for its documentation and subsequent cleanup. The agents did not autonomously identify that the premise of the task (CMake) was incorrect for the repo.
## Recovery Procedures
- **Human Intervention**: The human user notified the parent agent that all agents were idle, requesting the parent agent to inspect the current state and kick-off the agents to resume their work.
- **Parental Inspection**: The parent agent used `tail -c +$((offset+1))` to read the exact response of all active agents. This provided the parent agent with enough information to understand the current state and required next actions.
- **Directed Nudging**: With the information provided from inspection of sub-agent last responses, the parent agent either (a) prompted the "stuck" agent to continue working / complete the administrative notification step, or (b) performed the cross-agent coordination itself (e.g., by prompting the target agent on the stuck agent's behalf). In all cases, the work was able to continue from where it got stuck, requiring minimal human intervention.
- **Technical Debt Resolution**: Upon identifying the hallucinated `CMakeLists.txt`, a specialized cleanup subagent (`agent-issue-394-cleanup`) was spawned. This agent successfully coordinated with the build reviewer to delete the file and verify the Makefile's supremacy, resulting in commit `74ec0b0`.