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. Every topic has its own page at shoti.ai/troubleshooting — the slug above is the page name. Here’s the path that gets you unblocked fastest.

Copy the full error. Every shoti error names what failed and one fix — copy the whole message, including the topic slug above. On desktop, the Shoti.app log at ~/Library/Logs/Shoti/ keeps the full trace.

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 full error text to hello@shoti.ai. We respond within one business day during the public beta; every report shortens the queue for everyone behind you.