API keys & the co-host
| What you see | Why & how to fix it |
|---|---|
| "No API key set — add one in Settings." | No Anthropic key is saved (or it was cleared). Open Settings and paste your sk-ant-… key. Wait for the green check. |
| "Anthropic API key was rejected — check it in Settings." | The key is wrong, expired, or revoked. Re-copy it from your Anthropic dashboard (watch for stray spaces) and re-save. Confirm the key still exists and has credit. |
| "Anthropic is overloaded right now — try again in a few seconds." | The provider is temporarily overloaded. Wait a moment and summon again — nothing's wrong on your end. |
| "Anthropic rate-limited the request — wait a moment and retry." | You've hit your account's rate limit. Pause briefly, then retry. If it's constant, check your usage tier/limits with Anthropic. |
| A key field never turns green | Maneku validates keys live. A red/blank state means the provider didn't accept the key or couldn't be reached. Re-check the key, then your internet connection. You can force a re-check from Settings. |
Joining a room
| What you see | Why & how to fix it |
|---|---|
| "URL must use http or https" | The room link isn't a valid web URL. Paste the full link starting with https:// (not an app deep-link or partial address). |
| Stuck on "loading" or "filling in the name" | The room page is still loading, or the join automation couldn't find the name field. Give it a few more seconds. If it doesn't progress, type the name and click Join in the room view yourself. |
| A platform-specific join error | The join flow hit a snag (network, timeout, or the platform changed its page). Retry the join. If it persists, complete the join manually in the room view — the co-host can still operate once it's in. |
| Discord: "browser not supported" or voice won't connect | Discord is experimental. You may need to be logged in to Discord first, and captcha/2FA can block an automated join. Expect rough edges here while support matures. |
Reminder: some platforms have rules about bots or automated participants. Make sure your use is allowed under the platform's terms, and disclose the AI co-host to the room — see the disclosure guide.
Audio & transcript
| What you see | Why & how to fix it |
|---|---|
| The co-host joins but won't speak | Either it isn't being summoned, or audio isn't reaching the room. Confirm you're triggering a summon (Ctrl+Shift+Space or the Summon button). If you're using ElevenLabs for voice, verify that key is valid — otherwise switch to the system voice in Settings. |
| No transcript appears (and the co-host won't respond) | The co-host responds to the live transcript, so no transcript means it has nothing to work with. On a BYOK plan this almost always means the Groq key is missing or invalid — add/fix your gsk_… key in Settings and wait for the green check. On a credit plan transcription runs for you, so a missing transcript points to audio not being captured from the room (check you've actually joined and that participants are audible). |
| The co-host responds to itself | Its own voice was picked up as new conversation. Lower the chance by giving it a beat to finish before summoning again; if it persists, let us know your setup. |
| "Empty text" | A speak action fired with nothing to say. Make sure there's a response or text to send before triggering it. |
Cost & budgets
Maneku shows a live summon count and a running cost in the header, and you can set warning/stop alerts in Settings. On a credit plan this reflects credits consumed (and your balance). On a BYOK plan it's an estimate based on provider pricing — your authoritative bill comes from the providers themselves (Anthropic, Groq, ElevenLabs). Heavier summon types (Research, Deep) cost more than Ask; see the guide for the breakdown.
Still stuck? Email support@maneku.ai with what you were doing and any on-screen message, and we'll help.