sleepy

Support

Get help with Sleepy

Start with the hosted guide, then use the public issue tracker for install, onboarding, MCP connection, worker, and hosted alpha problems. Keep private code, secrets, and proprietary benchmark details out of public issues.

Public support

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

Open GitHub Issues

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

Private alpha support

If you were onboarded directly, use the private support channel you were given for source-bearing details, workspace deletion requests, security-sensitive reports, and proprietary benchmark context.

Do not paste API keys, OAuth tokens, source code, private run exports, or proprietary benchmark data into public GitHub issues.

Useful diagnostics

  • sleepy version
  • sleepy doctor
  • sleepy status <run-id> --server https://sleepy.run --json
  • sleepy export <run-id> --server https://sleepy.run --lineage

Redact run exports before sharing if they include source-bearing candidates.

Before filing

  • Follow the first-run guide.
  • Check Sleepy status.
  • Confirm your workspace API key is active in the workspace dashboard.
  • For hosted workers, confirm SLEEPY_TOKEN is set in the shell or CI job that runs Sleepy.
  • For MCP clients, confirm the endpoint is https://sleepy.run/mcp.