Prism Desktop 0.5.33: every agent gets its own setup

Prism Desktop 0.5.33 makes it explicit who owns what when you run several agents on one machine.

What changed

• One model and account per agent. Each agent that Prism manages can choose its own model and its own account. You can run several Codex agents side by side, each on a different model, without them sharing settings.
• A private setup for each agent. Managed Codex, Claude Code and Grok agents get their own private place for instructions, skills, extensions, tool servers, permissions and working files. One agent's setup does not leak into another's.
• Your own logins stay yours. Prism's configuration sits on top as a private layer. It never moves or rewrites the login that the vendor's own program keeps on your computer.
• Full external harnesses wait to be asked. Goose, Hermes, OpenClaw and similar tools stay dormant until you choose them, and then start with their own profiles unchanged. Saved settings or catalogue entries can no longer start one by themselves.
• Honest account states. If an account is still loading, unavailable, in conflict or out of date, Prism now says so, instead of implying it controls a choice it cannot enforce.

Why it matters

Most people who use more than one AI tool end up with one tangled personal setup that every agent inherits. Separating them means you can give one agent database access and another only a design skill, and know that is all each of them has. There is more on this idea in skills, plugins and tool servers explained and in bring your own AI subscription.

Nothing else changes in this release: browser, terminal, vault, store, workflows and update consent behave as before. Prism Desktop is on Linux first, and early access is through the waitlist.