Your next favorite terminal companion
Let's get you
a little more pop.
A native app for your project, not another tab to keep open. Here's what is available, what you'll need, and where to start.
Still in the soda lab.
Public binary downloads and package-manager installs are not enabled on this site yet. The source-build path is available for developers; it needs the prerequisites below.
All available installation commands:
Source: macOS / Linux: make build
Source: Windows: bash scripts/build.sh
Source builds use the existing Sodapop public OAuth client configuration. Do not borrow another application's credentials or put tokens in project files.
Your first few steps
- Get the appRead the build prerequisites and create a local build from a source checkout.
- Open a projectLaunch
sodapopfrom the directory you want to work in. - Bring your accountRun
/loginand authorize in your browser. You need an eligible GitHub account with Copilot access. - Choose a model and settle inPick an available model, start a conversation, and approve tool actions as needed.
The platform picture
| Platform | Processors | Distribution design |
|---|---|---|
| macOS | Apple silicon / Intel | Native archive, Homebrew, npm |
| Linux | ARM64 / x64, glibc | Native archive, Homebrew, npm |
| Windows | x64 | Native ZIP; npm when included in the published release |
This table describes supported build targets, not a claim that every channel is published. npm installs only the native platforms declared by that published package version; Windows requires its qualified ZIP payload. Node.js is required for the npm launcher. Native downloads and Homebrew do not require Go or a separate Copilot installation. Windows ARM64 and musl-based Linux are not supported targets.
A few things worth knowing
Read the permissions and privacy guide for account requirements, approvals, and the limits of cancellation.