Facts.
Architecture, module boundaries, file landmarks, commands, services, and conventions that should not be rediscovered every session.
The codebase. Your style. The decisions. The failures. The reasons. Retrieved before work starts, injected when relevant, and visible under your control.
Architecture, module boundaries, file landmarks, commands, services, and conventions that should not be rediscovered every session.
How you test, name, import, review, and ship, so repeated work keeps the same shape.
The reason a migration, dependency, constraint, or tradeoff happened, preserved for the next canvas.
Test failures, rejected fixes, repeated loops, and avoid-next-time notes that help the agent stop making the same mistake.
Repo rules, preferred commands, onboarding notes, and model-performance observations for the current workspace.
Before planning, Picasso loads the structured memory store, retrieves relevant account, workspace, repo, pinned, and stale-but-useful records, and injects the selected context into the provider messages. The agent gets targeted memory without flooding the prompt or pretending old chat history is understanding.
After a run, Picasso summarizes what happened, classifies useful lessons, filters secrets and private values, and writes structured fact, style, decision, failure, workflow, repo-rule, or model-performance records when the outcome is worth remembering.
Files changed, commands run, outcomes, decisions, and failure patterns become candidate memories.
`query_memory` and `write_memory` are available to the agent under the selected permission policy.
Readable `.picasso/memory/*.md` summaries mirror the structured store without becoming the source of truth.
Memory is retrieval, not model training.
Memory is never shared with sponsor systems.
Memories are isolated per account and workspace.
Environment values, private keys, credentials, and raw secrets are blocked from memory writes.
Memory added through the CLI appears in the TUI and Mac app. Memory added through the Mac app is available to CLI and TUI runs through the shared local backend and optional sync path.
picasso memory initpicasso memory add "Always use pnpm for this repo."picasso run "what package manager should I use?"/memorypicasso memory listpicasso memory inspect <entry-id>picasso memory edit <entry-id>picasso memory delete <entry-id>picasso memory pin <entry-id>picasso memory export > memory.jsonlpicasso memory clear --all| System | Persistence | Semantic retrieval | User control | Decision history |
|---|---|---|---|---|
| Tabnine memory. | Yes. | Limited. | Limited. | – |
| Devin Wiki. | Yes. | Wiki style. | Some. | Some. |
| CLAUDE.md. | File based. | Manual. | File edits. | Manual. |
| Picasso memory. | Yes. | Vector plus graph. | List, inspect, edit, delete, export. | Yes. |
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.