Skip to content

Lens Prism release notes#

Releases of the Lens Prism agent image, newest first. Releases are tagged vYYYY.M.DDHHMMSS — the timestamp of the build — and that tag is the pullable image tag.


v2026.8.10130628 — 10 August 2026#

Scheduled tasks stay quiet when there's nothing to report. A conditional scheduled task — one told to check something and report only if a condition is met — now passes through the same DELIVER/SUPPRESS gate the heartbeat uses, so a run that finds nothing to say sends nothing. A task with unconditional instructions (a daily summary, a fixed reminder) always delivers, even when its text repeats. A run that ends in an error always delivers, so a failure is never swallowed as "nothing to report."


v2026.8.7080521 — 7 August 2026#

Long conversations no longer forget their beginning. A thread previously fed the model only its most recent messages, so older context silently dropped away. Conversations now compact instead: when a turn fills most of the model's context window, the agent summarizes the older history and keeps the most recent messages verbatim. It also happens on demand with /compact in the web UI and the terminal UI.

Start a fresh conversation from the web sidebar. A new-conversation button next to Recents in the web UI opens a clean thread. Repeated clicks reuse the newest empty thread rather than stacking up unused ones.


v2026.8.4071841 — 4 August 2026#

Slack shows when the agent is working. While the agent processes a message you sent it in Slack, it reacts to your message with 👀 and, in a thread, shows a live status — "is thinking…" while it reasons, or the tool it's running — then clears both when it replies. The live status needs Slack's Agents & AI Apps feature and the assistant:write scope; without them the reaction is the cue.


v2026.8.3134735 — 4 August 2026#

See how full the context window is. The web UI composer and the terminal UI status bar now show how much of the model's context window a conversation has consumed, so you can see when compaction is near.

A third inference provider. Bedrock Mantle joins Bedrock and Microsoft Foundry as a provider the runtime can talk to. It is AWS's newer inference endpoint, recommended by AWS for new applications.


v2026.7.31065332 — 31 July 2026#

Messages sent mid-turn reach the running turn. A message that arrives while the agent is already working is now handed to the live turn instead of waiting in a queue, so a mid-thought correction or addition is picked up in the same reply. This release also reorganized the inference-provider code internally, with no change in behavior.


v2026.7.30060034 — 31 July 2026#

Replies are concise by default. In a multi-step turn, only the agent's final message is delivered; the intermediate steps are kept but flagged as internal. Turn on verbose delivery to stream every step. Because every step is still stored, the model's context is unchanged either way — this only affects what you see.


v2026.7.28084404 — 28 July 2026#

The default model is now Opus 5. New agents run on Claude Opus 5 as their main model unless you set a different one. This release also added a boot census and an internal refactor of the provider type, neither of which changes how the agent behaves.


v2026.7.23135032 — 23 July 2026#

The image carries a document toolchain. The agent's container image bakes in Python and the tools the Anthropic document skills need — pandoc, poppler, tesseract, and the Python libraries for PDF, Word, Excel, and PowerPoint — so those skills work out of the box without installing a toolchain at runtime.


v2026.7.15062202 — 15 July 2026#

A cleaner shell environment for the agent. NODE_ENV and Husky variables are stripped from the environment the agent's shell runs in, so commands it runs don't inherit build-time settings that could change their behavior.


v2026.7.10110818 — 10 July 2026#

Claude on Microsoft Foundry. Microsoft Foundry (Azure) joins Bedrock as a selectable inference provider, running Claude through the Anthropic Messages API from a Foundry resource. On Foundry, memory embeddings come from an Azure OpenAI text-embedding-3 deployment.