Docs

Troubleshooting & FAQ

Common issues with emma AI Console, what causes them, and how to fix them — plus answers to frequent questions.

If something isn't behaving as expected, start here. Each entry is a symptom, its likely cause, and the fix. Still stuck? Ask the copilot How do I ...? right in the console, or reach the team from the help menu.

The copilot can't see my resources

Symptom — you ask what's running and emma reports nothing, or misses a cloud you use.

Likely cause — that cloud provider isn't connected, or the connection lost access.

Fix — connect or reconnect the provider under Settings → Cloud Providers, then ask again. To pull in resources emma isn't tracking yet, run Import existing infrastructure.

My change didn't happen

Symptom — you asked emma to create or change something, but nothing changed.

Likely cause — the change is waiting on your confirmation. emma never applies infrastructure changes on its own.

Fix — look for the plan preview in the chat and click Confirm. See Safety & confirmations.

My MCP client doesn't show emma's tools

Symptom — Claude Desktop, Cursor, or your agent doesn't list the emma tools.

Likely cause — the server isn't configured, the client wasn't restarted, or the token is missing or invalid.

Fix — recheck the config against Connect the MCP server, confirm EMMA_TOKEN is set to a valid key from Settings → API Keys, and restart the client.

An alert never arrived

Symptom — a condition you set an alert for occurred, but you weren't notified.

Likely cause — the delivery channel isn't linked, or the alert routed somewhere you didn't check.

Fix — confirm the channel is linked (Telegram / Slack) and that the alert routes there — see Set up alerts.

A model I want isn't available

Symptom — a model doesn't appear in the picker, or a stage fell back to a default.

Likely cause — the model needs a key your company hasn't added, or multi-provider isn't enabled.

Fix — check Choosing models; for your own providers, see Bring your own model keys (administrator required).

FAQ

Is it safe to let the copilot manage production? Yes — every change waits for your confirmation, so the copilot can propose but never apply on its own. See Safety & confirmations.

Does emma lock me in? No. Your infrastructure lives in your own cloud accounts, and anything emma builds can be exported as code.

Which clouds does emma support? The major providers; connect them under Settings → Cloud providers. One conversation spans all connected clouds.

Can I use emma from my own tools? Yes — the MCP server exposes your infrastructure to any MCP-compatible client.

What's next

How is this guide?

Last updated on 17 Jul 2026

On this page