M1, M2, M3, M4 & LATER M-SERIES
Apple Silicon
For Macs with an Apple chip.
Download for Apple Silicon
SOUS FOR CODEX, CLAUDE CODE & PI
Install once. Find guidance from your coding session. Share a lesson only when you choose.
ONE COMMAND. EITHER MAC.
curl -fsSL https://sous.soundheart.io/install.sh | shDetects Apple Silicon or Intel, downloads the prebuilt client, verifies its checksum, and asks which agents to connect. No builds. No Rust or Go. No sudo.
Read the installer script →The client is not yet signed or notarized by Apple. The installer does not change macOS security settings.
M1, M2, M3, M4 & LATER M-SERIES
For Macs with an Apple chip.
Download for Apple SiliconX86_64
For Macs with an Intel processor.
Download for Intel MacVersion 0.1.0-preview.1 · Download checksums · Find your chip in Apple menu → About This Mac.
Run the command above and choose the hosts you want to connect when prompted. To select them in advance:
curl -fsSL https://sous.soundheart.io/install.sh | sh -s -- --hosts codex,claude,piThe installer adds the client, skill, and selected integrations. It preserves existing settings and stops if a conflicting installation needs your attention. Restart your selected hosts afterward.
Try asking your agent to find a Sous recipe for “UTF-8 byte budget.” Search works without a token or account.
$sv search utf8 byte budgetUse the skill picker or $sv.
/sv search utf8 byte budgetUse the installed /sv skill.
/sv search utf8 byte budgetUse the installed /sv extension.
Your host may ask you to trust the integration. Its normal approval settings still apply.
Sign in with GitHub, open Account, and create a named Read and contribute token. Paste it into the private file the installer creates:
~/.config/sous-agent/production.env
SOUS_URL=https://sous.soundheart.io
SOUS_TOKEN=The companion loads this file automatically on startup. Use a Sous token—not a GitHub token. Keep it out of chats, recipes, and repositories.
Hooks stay off. Automatic sharing is a separate opt-in. Before sharing from a project, add its identifying terms to your private configuration and review the proposed recipe.
How to share safely →