Install Picasso.
One binary. A terminal-first start on macOS, Linux, and Windows — these paths go live the day the doors open.
One binary. A terminal-first start on macOS, Linux, and Windows — these paths go live the day the doors open.
brew install picassopicasso --versionnpm install -g @picasso/climacOS.
Use the package path your team standardizes on, then verify the installed binary before connecting a provider.
brew install picassopicasso --versionLinux.
Install from the shell, confirm the binary on your path, and run the doctor command before opening a production repository.
npm install -g @picasso/clipicasso --versionpicasso doctorWindows.
Use a Windows package manager where available, then launch Picasso from the terminal in the repository you want it to inspect.
winget install picasso.picassoscoop install picassopicasso --versionNode package managers.
Use the npm package when your workstation already manages global developer tools through Node.
npm install -g @picasso/clipnpm add -g @picasso/clipicasso --versionMac app.
Picasso for Mac is a universal app for macOS 13 and later. It shares the same runtime, memory, goals, and approval queue as the CLI and TUI. The download link goes out to the waitlist the day the doors open.
From source.
Source installs are for contributors and teams that want to inspect the code before running it. Clone the repository, install dependencies, build the workspace, then run the CLI from the package script.
git clone https://github.com/picasso/picasso.gitcd picassopnpm installpnpm buildpnpm picassoVerify your install.
A good first run proves three things: the binary is reachable, the local environment is healthy, and Picasso can see the repository boundary. Release artifacts can also be checked with package signatures, checksums, or provenance when your install path provides them.
picasso --versionpicasso doctorpicasso auth statusSystem requirements.
Picasso needs a modern terminal, Git for repository workflows, and the package manager or runtime your project already uses for tests and builds.
First run.
Run `picasso` with no arguments to open the first-light flow. Choose managed, subscription, API-key, or local mode, then ask for a plan before the first edit.