ac-debug

Multi-module trace analysis diagnostics coordinate a main thread with subagents to gather evidence across components, aggregating logs to pinpoint root causes. This staged workflow ensures cross-component traces are captured and validated before any repair is applied.

Log aggregation for debugging failures is handled by dispatching clues to subagents that collect and integrate evidence across affected modules. This parallel evidence gathering ensures full traceability and reproducibility for complex error diagnosis.

To start a structured diagnostic workflow for cross-component errors, input the issue description into the command interface. The system initiates staged evidence gathering, coordinates subagents for trace analysis, and presents a user-validated repair plan.

Yes, this debugging approach requires explicit user confirmation before applying any fix. It generates actionable repair suggestions only after the main thread and subagents complete evidence collection and validate the root cause analysis.

You can use subagents to diagnose issues when the same error appears in multiple modules by automatically dispatching clues to relevant subagents. They gather evidence in parallel and integrate findings to ensure comprehensive cross-component trace coverage.

You should not use a coordinated subagent workflow for issue diagnosis when dealing with single-module errors that lack cross-component traces, as the overhead of dispatching and integrating subagent evidence outweighs the benefits of parallel collection.