Skip to main content
Unmute is one static binary. Pick your operating system and install it. Normal use does not need Go. On this page:

​
Install Unmute

Install with Homebrew:
Check it:

​
Keep it current

This site is written against the newest release, and releases come often. If a field or a flag on a page does not exist in your build, upgrade. The changelog says what changed in each release.

​
What you need to run an agent

The default LiveKit browser dev loop needs Docker with Compose. Check it before the quickstart:
Pipecat browser development uses uv instead. You can write, validate, and compile a package without either runtime. A phone route is verified after you deploy; see phone calls for what each route needs.
Verify a release archiveEach archive holds the binary, LICENSE, and README. Every release also has a unmute_<version>_checksums.txt file, its signature, and one SBOM per archive.Check the archive against the checksum file:
Check that this project’s release workflow, and nobody else, signed the checksum file:
Install with GoOn any platform with Go 1.26 or newer:
Build from a cloneThis is the contributor path, and the one to take if you want to change the CLI itself.
1

Clone the repository

2

Build

That writes bin/unmute. The direct equivalent is CGO_ENABLED=0 go build -o bin/unmute ., and the version string is stamped in at link time.
3

Check it

It prints one line: the release, the commit it was built from, and that commit’s date. A plain go build with no link-time stamping prints unmute version dev.
Put a source build on your PATH
That runs go install, which puts unmute in your Go bin directory (usually ~/go/bin). Add that directory to your PATH and you can run unmute from anywhere. The rest of these pages write unmute; if you skipped this step, read that as bin/unmute from the repository root.A package manager install is already on your PATH.

​
Where to go next

Quickstart

Scaffold an agent and talk to it in your browser.