Troubleshooting

Quick fixes for common issues. Most problems resolve themselves — Clawctl monitors your agent 24/7 and auto-recovers from failures.

My agent won't start or shows an error

After subscribing, your agent is deployed automatically. If something goes wrong during setup, you'll see an error on the provisioning page.

What to do:

Click "Try Again" on the provisioning page. Most failures are temporary and resolve on retry.
Check your dashboard. The status indicator shows whether your agent is healthy, starting, or needs attention.
Wait a few minutes. Clawctl's auto-recovery detects unhealthy agents and restarts them automatically.
Still stuck? Email support@mg.clawctl.com with your account email and what you see on screen. We'll take it from there.

Your agent's chat interface may briefly show "Chat Unavailable" during restarts, updates, or temporary network interruptions.

What to do:

Refresh the page. The connection re-establishes automatically in most cases.
Check your dashboard. If your agent shows "unhealthy", auto-recovery will restart it within minutes.
Use the CLI. Run clawctl status for a quick health check, or clawctl pause then clawctl resume to force a restart.

If your agent can't generate responses, it's usually an issue with your LLM provider API key or quota.

What to do:

Verify your API key is correct and active at your provider's dashboard (Anthropic, OpenAI, etc.).
Re-enter the key in your agent's Control UI under Settings. Keys are encrypted at rest — re-entering ensures the latest key is used.
Check your quota. Most providers have rate limits and spending caps. Ensure you have available credits.
Try a different model. Clawctl supports Anthropic, OpenAI, Gemini, Grok, OpenRouter, and Ollama (Team+). Switching providers can bypass temporary outages.

If clawctl status or other commands show connection errors, here's how to fix it.

What to do:

Re-authenticate. Run clawctl login to refresh your credentials via the browser.
Check your network. The CLI needs to reach the Clawctl API. Corporate firewalls or VPNs can sometimes block the connection.
Update the CLI. Run npm install -g clawctl-cli to get the latest version with bug fixes.

After adding a messaging channel, it may show "connected" but need one more step to fully pair with the messaging platform.

What to do:

Check the pairing status in your dashboard. Each channel shows whether it's fully paired or waiting for approval.
For WhatsApp: Scan the QR code shown in your agent's Control UI to link your WhatsApp account.
For Telegram: Make sure your bot token is correct and that you've started a conversation with your bot.
For Discord/Slack: Verify the bot has been invited to the right channels with proper permissions.

Your agent is healthy but doesn't reply when you send it messages through a connected channel.

What to do:

Check approvals. If approval mode is enabled, the agent may be waiting for you to approve a pending action. Check the Approvals section in your dashboard.
Test via the web chat. Open your agent's Control UI directly and send a test message. If web chat works but the channel doesn't, the issue is with the channel connection.
Restart the agent. Use clawctl pause then clawctl resume to restart cleanly.

Clawctl includes built-in monitoring, auto-recovery, and health checks — so most issues fix themselves. If something persists:

Email: support@mg.clawctl.com
Include: Your account email and a description of what you see. Screenshots help.
Response time: We typically reply within a few hours during business days.