Version 1.2
Prism 1.2, released 3 August 2026: an in-panel notification area for update notices and service messages, and panel analytics that surface failures without waiting for a report.
1.2 is the current release, out on 3 August 2026. It is the version to be running today. The panel shows the version you are running, and tells you when a newer one exists.
Notifications in the panel
Until 1.2 the panel could not tell you anything. A newer panel version, or a problem on our side, was something you found out about elsewhere or not at all. 1.2 adds a notification area under the panel header.
Notifications stack, so one never hides another, and color means state: amber is a warning, red is a problem, green is resolved.
| Kind | What it is | When it appears |
|---|---|---|
| Update notice | A newer panel is available | Whenever the server is ahead of the panel you have installed |
| Service message | Maintenance or a problem on our side | Only while we have set one |
| Detected problem | Something Prism has measured going wrong | The slot ships in 1.2, the first rules are in testing |
Update notices
The server updates on its own, the panel does not. When the server is ahead of your panel, the panel says so and offers Update now, which opens the License Portal — the panel download is there, on every plan. You can collapse the notice. It comes back after a few minutes and keeps coming back until the panel is actually updated, because an out-of-date panel is the one thing a server release cannot fix for you.
Service messages
If there is maintenance or an outage, we can put one message into every open panel from the server. When there is nothing to say, nothing is shown. This needs no panel update, which is the point of it.
Detected problems
The third kind is for problems Prism measures rather than problems you report. The notification area that carries them ships in 1.2. The first rules that feed it — a host that cannot run scripts, a low or empty Prism AI balance — are in testing and have not been released. They run in the panel, so they arrive with a panel update rather than a server one.
The panel reports on itself
Prism records how the panel and its tools are used: whether the panel opened, which tab you opened, whether activation succeeded, and the typed reason when it failed. Errors inside the panel are recorded as they happen.
This closes a real gap. Before 1.2, someone who installed the panel and never got past the license screen was invisible to us, because the failure happened before anything reached the server. One customer sat in exactly that state for five days. It is now a state we can see, which means it is one we can fix without asking you for anything.
Where session recording is enabled, everything you type is masked, including the license key field. Recording is fail-silent by design: it cannot block, slow or break the panel, and it can be switched off from the server without you reinstalling.
What is not collected: your project file, your compositions, your footage, your renders, and your conversation with your AI client — that conversation happens inside your own AI app and never reaches Prism. Your license key and session tokens are stripped before anything is stored. Records are tied to your license record. The privacy policy states this in full.
Smaller changes
- The license screen is easier to read: the key field reads as an input, and the version and purchase link sit in the footer.
- The version is stamped from a single source across the server and the panel, so the version you are shown is the version you are running. Previously the two could drift apart.
Related
- 1.1: the release before this one.
- Install: installing or updating the panel.
- Known issues: what is still open.
- Privacy policy: what is recorded and what is never received.
Use cases
Real ways designers and studios use Prism: caption a video, cut to the beat, animate a logo from an SVG, and re-skin a template to a brand.
Version 1.1
Prism 1.1, released 3 August 2026: the panel is listed as After Effects MCP in Window → Extensions, billing webhook verification was corrected, and the server began recording how tools are used.