Prism Desktop 0.5.30: personal logins stay personal

Prism Desktop 0.5.30 is mostly about boundaries: what belongs to a person, what belongs to an organisation, and what the desktop app is allowed to reach.

What changed

• Your personal Claude Code stays yours. Its terminal login, account choice and provider credentials remain on your device. Where an organisation uses Anthropic models, that use goes through the organisation's own API access, not through your personal login.
• The desktop app uses only the public Prism API. Service data and service credentials stay on the server side and never reach a customer's computer.
• Support requests reach operators sooner. Authorised operators get a notification when a support request arrives. The notification carries no customer content.
• No background daemon. The app refreshes its contact with the service only while you are signed in and the app is running. Nothing keeps running after you quit, and the server never probes your device.
• Release of shared media is a deliberate act, with a confirmation step and an exact check of what is being released.

Browser, terminal, vault, store, workflows and update consent are unchanged.

The reasoning behind these boundaries is set out in what is data custody in AI and on the security page. Early access is through the waitlist.