Stuck, surprised, or missing something?
ScreenBook is a solo-built project — write directly and you'll reach the person who wrote the code.
Report a bug
Something renders wrong, validate is red on a screen that looks fine, the studio won't boot. Include what makes a report actionable: versions, the failing screen, the validate output.
Email a bug report →Request a feature
A control the studio is missing, a tool your agent needs, a workflow ScreenBook should support. Describe the problem — the shape of the fix can come later.
Email a feature request →Ask a question
Not sure whether it's a bug, or just want to talk through a setup? Write and say hi — questions are welcome.
Ask by email →Before you file a bug
1. Check Troubleshooting. The ten most common surprises — blank studio, missing sidebar entries, eternal “Loading…”, red validate — each with its actual cause.
2. Run screenbook validate. Its output names the failing screen, the exact theme × mode × direction combination, and the first console error — paste that into the report.
3. Grab your versions. screenbook version and node --version — include both.