debug

To debug an enigmatic bug with an unclear root cause, you can trigger a structured debugging workflow that coordinates root cause investigation, pattern analysis, hypothesis testing, and implementation. This systematic process enforces discipline to identify the actual failure.

A systematic debugging workflow is a four-phase process—Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation—that guides agents through unclear failures. It uses optional sub-agents to split investigation and implementation roles.

To stop endless debugging loops, the workflow includes built-in guardrails that trigger an escalation after three failed fix attempts. This prevents agents from repeatedly applying ineffective patches to the same root cause.

Yes, you can split roles during root-cause analysis by using optional sub-agents. The workflow supports assigning an investigator agent for pattern analysis and an implementer agent for the actual fix.

You should use a structured root-cause investigation when tests fail unexpectedly, you face enigmatic bugs, or you trigger a /debug request. It enforces a disciplined workflow needed when the underlying failure is not immediately obvious.