> ## Documentation Index
> Fetch the complete documentation index at: https://unmute.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Unmute compiles to exactly three targets. Pipecat and LiveKit are code targets: compile writes a Python project you run. SLNG is a hosted target: compile writes a deployment body and SLNG runs the agent, so it has no `unmute dev`. Those three are the only values `provider` accepts in `targets.yaml`. Deepgram and ElevenLabs appear in these docs as model vendors, which is not the same thing as a target, and `slng` is both.
> The Go structs in `internal/spec` and `internal/ir` are the schema truth. Check a field against them, or run `unmute validate`, rather than against what you remember.

# Community

> Where to ask a question, where to file an issue, and how to contribute to Unmute.

Unmute is open source and MIT licensed. Anyone can read it, run it, change it,
and send the change back. Contributions are welcome, and the
[contributing guide](/community/contributing) says exactly what a good one
looks like.

<Columns cols={2}>
  <Card title="Discord" icon="message-circle" href="https://discord.gg/kxZactmWj">
    Ask a question, show what you built, and talk to the people who maintain
    Unmute.
  </Card>

  <Card title="GitHub" icon="github" href="https://github.com/slng-ai/unmute">
    Read the source, file an issue, and open a pull request.
  </Card>
</Columns>

## Where to take what

| What you have                                                                        | Where it goes                                                                                  |
| ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
| A question about authoring a package, or a call that did not go the way you expected | [Discord](https://discord.gg/kxZactmWj)                                                        |
| Something broken: a wrong refusal, a bad compile, an agent that misbehaves           | [Bug report](https://github.com/slng-ai/unmute/issues/new?template=1-bug.yml)                  |
| Something that works, but not well enough: latency, cost, a rough error message      | [Improvement](https://github.com/slng-ai/unmute/issues/new?template=2-improvement.yml)         |
| Something that does not exist yet: a target, a provider, a transport, a tool kind    | [Feature request](https://github.com/slng-ai/unmute/issues/new?template=3-feature-request.yml) |
| Code you want merged                                                                 | [Contributing](/community/contributing)                                                        |

Search the [open issues](https://github.com/slng-ai/unmute/issues) before you
file a new one. Adding what you know to an issue that already exists moves it
faster than a second copy of it.

## What is worth sharing

A voice agent is hard to judge from a diff. What it sounds like on a real call
is the part that matters, and that part travels badly in text. So the things
most worth posting are the ones a reader can hear or run:

* A package you built, and a recording of it answering a call.
* A route, a provider or a carrier you got working.
* A prompt that fixed a behaviour you could not fix with a field.
* A number: how long your agent waits before it answers, and on which target.

## Contribute

<Columns cols={2}>
  <Card title="Contributing guide" icon="heart-handshake" href="/community/contributing">
    The issue, an example that uses your feature, a video, a README and the
    docs page. What a change needs before it can be merged.
  </Card>

  <Card title="Changelog" icon="tag" href="/changelog">
    What shipped in each release, newest first.
  </Card>
</Columns>