Terminal first.
The shell remains the center of the workflow.
Picasso reads the repo, plans safely, retrieves memory, edits files, runs commands, fixes failures, writes tests, and keeps the whole canvas visible.
Open the full TUI when you want status, approvals, model state, budget, tools, memory, goal progress, subagents, replay, and session history in view. Use the short command when the task is direct.
picasso plan "repair failing auth tests"picassopic "write a plan for the auth refactor"picasso run "explain the failing test" --jsonThe shell remains the center of the workflow.
Model, tokens, tool calls, memory use, permission mode, goal state, and budget state stay on screen.
Run interactive or non-interactive work from the same harness.
Picasso handles real repository work: feature edits, refactors, test repair, debugging, migrations, dependency issues, and CI failures.
Follows existing patterns instead of inventing a new style.
Uses the repo's tests, lint, typecheck, build, and scripts.
Errors become evidence for the next edit.
The final report says what changed and what remains.
When risk rises, Picasso enters a read-only architecture pass. It can inspect files, configs, dependencies, entry points, and data flow, then writes a reviewable `plan.md` you can approve, edit, or reject before implementation starts.
The plan names files to inspect, create, modify, or leave untouched.
Assumptions, edge cases, permissions, and open questions are called out early.
Checks are part of the composition, not an afterthought.
Picasso supports workspace containment, approval gates, shell allowlists and denylists, network controls, secret detection, and audit logs.
Sensitive shell commands and writes ask first.
Work stays inside the workspace boundary you choose.
Important actions leave a record.
Every session is a canvas. Persist it, resume it, fork it, replay it, sync it to the Studio, or open the same state from the native Mac app.
Pick up where the agent left off.
Try another path without losing the original.
Inspect plans, provider calls, commands, approvals, edits, memory writes, and results.
Use hooks, slash commands, and MCP to fit your repo.
The agent is the brush. Everything around it is the studio — and it ships in the box.
`/schedules` runs recurring work on your clock — queued when due, gated by the same approvals as everything else.
`/skills` keeps a local registry of the moves your team repeats — create, validate, and toggle them without leaving the terminal.
On the Mac, speak the prompt. `/voice` turns dictation into the same composer text, with microphone permission honored end to end.
Point the Mac app at localhost, pick a device, capture a screenshot — and route it through the approval queue like any other evidence.
Picasso for Mac is almost here — a coding agent that looks the way serious tools should, and costs what creative freedom should: nothing. Leave your email and be first on the canvas.
Sponsors and labs — the early canvas is yours. Choose Sponsor or Lab above and we'll reach out before launch.