Getting Started

Sonic Agent ships in two forms: a standalone CLI and a Claude Code plugin. This page covers install, license activation, your first run, and the one rule you must never break.

Install the CLI

npm install -g @lebtiga/sonic-agent

Then activate your license:

sonic activate

You will be prompted for two things:

1. License key (format SONIC-XXXX-XXXX-XXXX-XXXX)
2. Email on the license

On success, Sonic installs itself to ~/.sonic, confirms the seat (licenses are limited to 3 devices), and syncs the skill pack:

✓ License valid  (1/3 devices)
✓ Installed
✓ skills v2026.3.0 installed
⚡ Sonic is ready. Run "sonic" to start.

First run

sonic

You get the Sonic banner, a confirmation of your licensed email and device count, and a summary of the 17 loaded skills grouped by stage (Research, Design, Build, Optimize, QA, Publish). From here you can:

• Run sonic autopilot to approve a plan and let Sonic build every page hands-off.
• Run sonic setup once to save your preferences.
• Just describe your project (niche, city, what you want to rank for) and Sonic figures out the next step.

Quick identity check

Type Are you Sonic? and you should get back: "Yep, Sonic here. Ready to go fast." ⚡

Install as a Claude Code plugin

If you work inside Claude Code, install the plugin instead (or in addition):

# from a local clone
/plugin install /path/to/sonic-agent-package/claude-code-edition/sonic-agent

# or from the private repo
/plugin install lebtiga/sonic-agent#main:claude-code-edition/sonic-agent

This adds:

• The sonic agent (invoke with /agents sonic or by mentioning Sonic).
• The /sonic-build, /sonic-autopilot, and /sonic-help commands.
• All 17 skills, auto-loaded when relevant.

Recommended launch (skip permission prompts)

A full site build edits many files and runs many shell commands. To avoid a permission prompt on every one, launch with permissions pre-approved in a workspace you trust:

claude --plugin-dir ~/sonic-agent/claude-code-edition/sonic-agent \
       --agent sonic-agent:sonic \
       --dangerously-skip-permissions

Make it a one-word command by adding an alias to ~/.zshrc or ~/.bashrc:

alias sonic='claude --plugin-dir ~/sonic-agent/claude-code-edition/sonic-agent --agent sonic-agent:sonic --dangerously-skip-permissions'

Reload (source ~/.zshrc) and now sonic launches ready to ship.

The one-folder rule (non-negotiable)

One folder per client. Always.

Sonic's memory is scoped to the workspace folder it launches from. Run two clients from the same folder and their memories cross-contaminate: names, briefs, and details from one client leak into another.

Every new client gets its own folder. No in-conversation instruction is as reliable as physical folder separation, so treat this as a hard rule:

mkdir -p ~/clients/<client-slug>
cd ~/clients/<client-slug>
sonic

Each fresh folder gives Sonic clean memory and a clean USER.md.

Where to go next

• How It Works - the brand-first methodology and why the order matters.
• The Build Pipeline - all 8 stages in detail.
• Commands - what /sonic-build and /sonic-autopilot actually do.