Plan.
Understand the request, inspect the files, retrieve useful memory, and write the path before touching code.
A Picasso session is not a single answer. It is a traceable loop across a 1M context window: read the repository, draft a path, act through tools with edit-loop auto-diagnostics, study the result, and continue only when the next step is justified.
Understand the request, inspect the files, retrieve useful memory, and write the path before touching code.
Use create_file and str_replace with auto-diagnostics, shell commands, git worktrees (/worktree), MCP tools, and subagents inside the mode you chose.
Read inline syntax-highlighted diffs, auto-diagnostics, tests, /diff main, /review-branch, logs, and failures in the CLI or Reasoning | Changes inspector.
Decide whether to continue, switch routes with /model or /provider, re-plan, ask for approval, write memory, or stop.
Search. Read. Edit with auto-diagnostics. Isolate in a git worktree. Review a branch. Ask an MCP server. Dispatch a subagent. Picasso can run independent work in parallel, then bring the result back to one visible decision.
Commands run under explicit sandbox and approval policy, with output folded back into the session.
create_file and str_replace stay scoped to the workspace and attach syntax and typecheck diagnostics in TypeScript, JavaScript, Python, JSON, and Swift.
/worktree create|apply|remove and Mac Worktree mode isolate parallel threads, while /diff main and /review-branch review changes before a PR.
External tools use declared capability profiles and appear in the same audit trail.
| Signal | Used for |
|---|---|
| Plan. | Next action and user approval. |
| Observations. | Errors, output, screenshots, and diffs. |
| Memory. | Relevant facts, style, and prior decisions. |
| Goal contract. | Completion criteria, budget, and stop conditions. |
Review before writes.
Parallel work with isolated contexts.
Persistent retrieval across sessions.
Run the loop against a completion contract.
Ask Picasso to repair a failing auth test. It reads the test, opens the module, drafts a plan, patches the validation path, runs the targeted suite, reads the next failure, updates the regression case, reruns the check, and reports the changed files. The point is not the first answer. The point is the visible path to a verified result.
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.