Skip to content
Integrations/Overview

Setup Command

Configure and migrate agent harnesses with reversible changes.

Install and Configure

Requires Node.js 20 or later on macOS or Linux. The versioned npm package is distributed directly from AudioLab; no global installation is needed.

Terminal
npx https://tryaudiolab.ai/cli/router-0.1.0.tgz setup

To install the standalone audiolab-router command:

Terminal
npm install --global https://tryaudiolab.ai/cli/router-0.1.0.tgz
audiolab-router setup

Choose your installed agent and review the planned files and fields. Setup asks before writing. Supply --agent pi to choose a client directly, or use list to see all automatic and guided paths. Windows users can follow each guide’s manual setup.

Set AUDIOLAB_API_KEY through your shell or secret manager. The package never writes its value into configuration.

Migrate an Existing Configuration

Terminal
npx https://tryaudiolab.ai/cli/router-0.1.0.tgz setup --agent opencode --dry-run

Setup adds an AudioLab provider or profile where the client permits it. Existing providers, credentials, tools, and permissions are retained. Hermes uses its custom-provider selection; review that change before applying. JSONC and YAML edits retain comments where supported. TOML and JSON5 may be reformatted; the exact original file is backed up.

Use --base-url for a staging endpoint and --model for an enabled model. The base URL must end in /v1. Client recipes use a conservative 128K context and 4096 output budget where configurable; adjust only within the model’s published limits.

Noninteractive setup requires --yes. Invalid syntax, unsafe symlinks, and edits made after planning stop the migration. Custom configuration locations must remain inside your home directory.

Launch an Agent

Terminal
npx https://tryaudiolab.ai/cli/router-0.1.0.tgz run pi

The launcher reads the configured model and your environment, then starts the installed agent. Additional arguments go after --. Environment-based routing is scoped to the child process; no shell profile or saved login is changed. Desktop apps or background services may need the key entered in their own credential settings.

Check the Connection

Terminal
npx https://tryaudiolab.ai/cli/router-0.1.0.tgz doctor --agent pi

This checks GET /v1/models using your key and confirms the configured model appears. It does not send a paid inference request or certify tool execution. Follow the harness guide to test a short response and a read-only tool call.

Undo Setup

After a change, setup prints its backup ID and the exact restore command.

Terminal
npx https://tryaudiolab.ai/cli/router-0.1.0.tgz restore <backup-id>

Restore recovers original bytes and file permissions, or removes files created by setup. It refuses to overwrite files edited after setup. Backups are private files under ~/.config/audiolab/backups; they may contain credentials that were already in your original configuration. Keep them private. Re-running an unchanged setup makes no edits.

Commands

CommandPurpose
listShow automatic and guided setup paths
setup --agent <id>Review and configure one agent
run <id> -- <arguments>Launch its selected profile
doctor --agent <id>Check credentials and model discovery
restore <backup-id>Undo an unchanged setup

Agent Harnesses