We’ll get you moving.

You landed here because a shoti CLI command, the MCP server, or the API returned an error with this help link. Per-topic pages will land with the Phase 9 trust surface; until then, here’s the path that gets you unblocked fastest.

Re-run with verbose output. Add --debug to the failing shoti command (or check the Shoti.app log at ~/Library/Logs/Shoti/) and copy the full error including the topic slug above.

Check your auth + config. Most tier-2 errors come from one of three places: stale credentials at ~/.shoti/auth.toml, a team you’re not yet a member of, or an outage on api.shoti.ai. shoti doctor walks the full surface in under five seconds.

Still stuck? Send the topic slug + the --debug output to hello@shoti.ai. We respond within one business day during the private beta; every report shortens the queue for everyone behind you.