Support

Get help with Sleepy.

Start with the first-run guide, then use the right channel for the problem. Keep private code, credentials, and proprietary benchmark evidence out of public reports.

Public support

Open an issue in the public releases repository for install failures, onboarding problems, bugs, and documentation gaps.

Open GitHub Issues

Include the Sleepy version, OS, command, expected behavior, actual behavior, and non-sensitive error output.

Private and security reports

Report suspected vulnerabilities through GitHub private vulnerability reporting, not a public issue. Directly onboarded alpha users may also use their established private support channel.

Do not paste API keys, OAuth tokens, source code, client-owned exports, or proprietary benchmark data into a public issue.

Useful diagnostics

sleepy version
sleepy doctor
sleepy doctor --project --server https://sleepy.run
sleepy status <run-id> --server https://sleepy.run --json
sleepy export <run-id> --lineage on the creating executor

Hosted status is source-free. Client-owned exports can contain source and raw evidence; redact them before sharing.

Before filing

Follow the first-run guide and check service status.
Confirm the workspace API key is active in the authenticated workspace dashboard.
Confirm SLEEPY_TOKEN is set for the shell or CI job running the worker.
Start workspace deletion from the dashboard and retain the returned D-011 receipt.