Studio placements.
Around memory, sessions, plans, goals, replay, and account state.
For sponsors
Support the builders who ship.
Sponsors help keep a serious developer tool accessible. Their message appears in respectful, labeled surfaces around moments of learning, debugging, testing, planning, and shipping.
∠maintools4ctx28k / 200kcost$0.00modesafewaiting
High-intent, developer-respectful surfaces.
Picasso is used when builders are deep in real work. Sponsor placement belongs around that work, not inside it.
Studiolabeled sponsor support
memoryplansgoalssessions
◇ SponsoredClearly labeled sponsor message.Shown in the Studio. Outside code generation.
◇ Sponsoredone-line terminal disclosuredismissible
Terminal presence.
One line, dismissible, and clearly marked `◇ Sponsored`.
Relevant context.
Developer tools, infrastructure, education, cloud, security, and open-source support.
Clear labels. Clear limits.
Sponsor content never appears in generated code, model output, tool results, or plan documents. It never influences routing, tools, memory, or subagent selection.
trust boundaryoutside the agent loop
generated codeclean
model outputclean
tool resultsclean
plan documentsclean
routingnot influenced
memoryretrieval only
Always labeled.
Sponsor surfaces are never disguised.
Never in output.
Code and agent responses stay clean.
Never in routing.
Sponsors do not steer the agent.
Sponsor delivery fails closed.
Sponsor inventory can return no fill or a house disclosure when validation fails. Creative checks require a named sponsor, acceptable landing URL, disclosure text, and policy review before serving.
Validated slots.
Slot requests are checked before a sponsor surface appears.
Terminal restraint.
Terminal placements reject shorteners and keep disclosure visible.
Paranoid mode.
Paranoid mode returns no terminal sponsor content.
The Studio is the main surface.
The Studio is where developers review memory, sketches, goals, canvases, replay, and account state. It is also the primary home for sponsor experiences.
Studiomemory / plans / goals / replay
memorysketchescanvasesgoals
memoryauth module uses argon2id
plan3 files, 2 risks, 4 checks
goal62 percent complete
replay48 strokes recorded
Memory context.
Placement near facts and preferences.
Session context.
Placement around review and replay.
Goal context.
Placement near long-running work and progress.
Sponsored model unlocks.
Sponsors can help managed users access model capacity in the Studio. Unlocks are explicit, labeled, attributed, and separate from generated code or agent output.
Managed user value.
Sponsors help builders keep working.
Visible patronage.
Support is clear and attributed.
No output injection.
Unlocks do not place sponsor text in code or responses.
Attribution without crossing the boundary.
Sponsored unlocks can be tied to the sponsor, disclosure decision, managed usage ledger row, route decision, and revenue line while keeping sponsor systems away from code, prompts, tools, memory, and provider credentials.
Disclosure evidence.
Approval and disclosure requirements are recorded around the unlock decision.
Ledger link.
Managed usage rows can connect the unlock to cost, revenue, and margin evidence.
Redacted export.
Sponsor attribution artifacts can be reviewed without exposing developer work.
Trust is the reason the model works.
Picasso is not selling distraction. It is building a patron model for software creation, with boundaries that protect the developer and the sponsor.
Builder aligned.
Sponsorship funds access.
Premium context.
Placement around serious engineering work.
Long-term value.
Good sponsors become part of why the tool can exist.