CLI Troubleshooting & FAQ · Developers
The bugs we see the most in the Dailybot CLI, ranked by frequency, with copy-paste fixes.
If a CLI command is misbehaving, one of the entries below is almost certainly the reason. They’re ordered by how often we see them in support.
401 Unauthorized on every command▾
Your session or API key isn’t being resolved. Run dailybot me — if it also 401s, run dailybot login (personal use) or verify $DAILYBOT_API_KEY is set in the current shell. In containers, ensure the env var is passed through (docker run -e DAILYBOT_API_KEY …).
403 Forbidden on a specific endpoint▾
You’re hitting one of the four CLI-only endpoints with an API key. Only dailybot login can call /v1/cli/updates/, /v1/cli/status/, /v1/cli/chat/completions/, and /v1/cli/auth/*. Everything else works with either credential.
429 Too Many Requests▾
You hit a scope’s rate limit. Honor the Retry-After header. See /developers/rate-limits for scope names and quotas. Add jitter when retrying.
The CLI hangs on dailybot login▾
The browser tab didn’t complete OTP. Cancel with Ctrl-C and re-run. If your machine can’t open a browser, follow the URL that dailybot login prints in a browser on another device.
Report doesn’t appear in the team feed▾
Two common causes: (1) the report went to a different org because you have a stale session — check dailybot me; (2) the repo’s .dailybot/disabled is present. Delete it or unset the opt-out.
AI-agent hook fires too often▾
If your harness installs the Dailybot reporting hook, silence it for a repo by creating an empty file at .dailybot/disabled. See /developers/cli-configuration#opting-out-of-local-hooks.
Command not found: dailybot▾
If installed via pipx, ensure ~/.local/bin is on $PATH. If via npm, ensure the global npm prefix is on $PATH (npm prefix -g).
Which credential am I using right now?▾
Run dailybot me. The command prints your current identity and the credential type in use.
How do I rotate a leaked API key?▾
Revoke it in your Dailybot dashboard immediately. Any pipeline using it will start 401-ing on the next call; rotate the secret in your CI vendor and re-deploy the job.
Still stuck?
Open a ticket at dailybot.com/help or drop into the community. Include the CLI version (dailybot --version), the full command you ran, and any redacted error output.