The copilot

The copilot is how you drive emma. It's a chat assistant that understands your infrastructure: it can answer questions about what's running, reason about cost and security, and carry out changes through Infrastructure-as-Prompt. You keep one ongoing conversation rather than hunting through screens.

In a nutshell:

• It has context — it can see the resources in your connected cloud accounts
• It works in conversations you can return to, with a history of what you've done
• It uses tools to read and act on your infrastructure, and asks you to confirm anything that changes
• You can choose the model behind it

Context

Once you've connected a cloud provider, the copilot can read your resources and answer grounded questions — not generic advice, but answers about your environment.

Conversations

Work happens in conversations, listed in the sidebar so you can pick up where you left off. A conversation keeps its context as you go, so you can refine ("make that one bigger", "now do the same in a second region") without re-explaining.

Tools and actions

Behind the scenes the copilot calls tools to list resources, read cost and security data, and propose changes. Read-only questions are answered directly; anything that would create, change, or delete infrastructure is turned into a plan you must confirm — see Safety & confirmations.

Choosing the model

You can pick which model powers the copilot, or let emma route automatically. See Choosing models for the options.

Where to find it

Open the copilot from the emma AI toggle in the top bar. It docks alongside your work — the diagram, deployments, settings — so you can keep chatting as you move around the console.

What's next

• Quickstart — put the copilot to work
• Choosing models — pick the model behind the copilot
• Connect the MCP server — use the same capabilities from your own AI tools