Skip to main content

The six commands

The first four take you from nothing to a voice you can talk to on your own machine. deploy is the one that puts an agent somewhere else, and it is SLNG only: a livekit or pipecat target compiles to a project that platform deploys with its own tool.

Saved company rules

init uses the saved default automatically. Add --manifest <name> for direct selection, or --from-manifest to open a picker for one new agent. For a coding assistant, init <agent> --manifest <name> --draft creates an unfinished package without prompts. The skill reads the copied rules, completes the use case, then validates and compiles it. Follow the draft quickstart for commands and a copyable assistant brief.

Two commands off that path

Neither reads or writes a package. resources reads your SLNG organisation and changes nothing there, so it is the command to run before you write a builtin: or mcp: tool and have to spell a name exactly. skill makes no network call at all: the skill ships inside the binary. help and completion come from the command framework.

Running unmute with no arguments

In a terminal, unmute with no command opens an interactive console. Outside a terminal, for example when the output is piped, it prints the help above. That is the root command on its own. The commands below it have their own no-argument behaviour, and it is a different thing.

Running a command with no package

validate, compile, deploy, dev and pull take the package directory as an optional argument. Leave it out and the package is the current directory, so you can cd into an agent and work there:
Naming a directory still works, and still wins:
The current directory must hold agent.yaml itself. No parent directory is searched, so a run from inside build/ cannot rewrite the package above it:
init is the exception: its argument is the name of the package to create, and with no name in a terminal it opens the interactive console instead.

Version

It prints one line: the release, the commit it was built from, and that commit’s date. All of it is stamped in at build time. -v is the short form.

Exit codes

There are no other exit codes today.

Warnings

Warnings go to standard error and do not change the exit code. A command that prints warnings and exits 0 succeeded:
Errors are printed to standard error too, prefixed with unmute:, and exit 1:

Shell completion

Each subcommand’s own help explains where to install the script on your system.

Where to go next

unmute init

Start with the scaffold.