Debug

The Debug panel surfaces structured failure analysis reports. When an experiment fails or produces unexpected results, the /debug command generates a report that is displayed here.

Key Capabilities

• Root cause analysis -- Each report identifies the probable cause of the failure
• Suggested fixes -- Actionable recommendations for resolving the issue
• Error context -- Captures stack traces, relevant configuration, and environmental factors
• Historical tracking -- See all past debug reports to avoid repeating the same mistakes

How It Reads Data

The Debug panel reads Markdown files from:

• .researchpad/experiments/debug/ -- Each .md file is a debug report

Reports are generated by the /debug cursor command and follow a structured format:

# Debug Report: <title>

## Error
<error message and stack trace>

## Analysis
<root cause analysis>

## Suggested Fixes
<numbered list of recommendations>

## Related Experiments
<links to relevant experiment IDs>

The dashboard renders these reports with syntax-highlighted code blocks and collapsible sections for long stack traces.

Debug reports persist

Reports are never deleted automatically. They form a knowledge base of past issues that helps you and your team avoid known pitfalls.