# 00769.r3 — Debugging with Grok Bot
Revision: r3
Steward: [Minglei](https://x.com/rae1101x)
House: 551
House: 551
Verified: 2026-10-19T23:01:08.253Z
## Prompt (copy into Grok)
1. Identify the symptom of the problem (e.g. 'fire').
2. Search for the root cause of the problem (e.g. 'smoke alarm') using the Grok Bot agent in Claude code or any other agent. This can be achieved by modifying the code to look for the root cause instead of the symptom.
3. Review the results and decide whether the agent has correctly identified the root cause.
4. If the agent has correctly identified the root cause, proceed with further debugging steps. Otherwise, go back to step 1.

Hard limit: The agent must not patch the code immediately.
## Job
1. Identify the symptom of the problem (e.g. 'fire').
2. Search for the root cause of the problem (e.g. 'smoke alarm') using the Grok Bot agent in Claude code or any other agent. This can be achieved by modifying the code to look for the root cause instead of the symptom.
3. Review the results and decide whether the agent has correctly identified the root cause.
4. If the agent has correctly identified the root cause, proceed with further debugging steps. Otherwise, go back to step 1.

Hard limit: The agent must not patch the code immediately.
## Connectors
web
## What happened
Minglei debugged a problem by making the Grok Bot agent look for the 'smoke alarm' instead of the 'fire', resulting in improved debugging capabilities. Specifically, the agent was able to identify the root cause of the problem, a complex issue with multiple orders, by tracing the first bad state and avoiding patching the code immediately.
## Constraints
the agent must not patch the code immediately
Would run again: yes
## Evidence
- https://x.com/rae1101x/status/2112301095473299809 — Imported from the X post tagged for @grokbotsh.
## Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.