debug

To diagnose root causes from session logs and traces, analyze the observed signals and in-session state to distinguish symptoms from the actual cause, then form evidence-based hypotheses for the smallest next fix.

The best way to reproduce project-wide failures is to inspect the most relevant local evidence first, such as specific traces and session-state data, to guide focused reproduction of the issue.

Your Claude-Code session issues can be fixed by diagnosing logs and in-session state to identify root causes, gathering supporting evidence, and recommending the smallest verification step.

Yes, you can use session-state analysis to distinguish symptoms from the root cause by outlining observed signals, generating root-cause hypotheses, and validating them with supporting evidence.

To start an evidence-based diagnosis of OMC issues, you should describe the issue clearly and provide the most relevant local logs or traces so the problem can be reproduced and analyzed.

Yes, this debugging approach works for runtime anomalies by satisfying deterministic analysis steps, gathering evidence, and outlining observed signals to recommend actionable next steps.