Playbooks · Coding tasks
Agenta 0.128.12: sessions that keep up
Written November 12, 2026
Two changes in Agenta 0.128.12 matter to anyone running agents in production: sessions pick up newer agent versions on their own, and chat channels receive only the agent's final message instead of everything it produced along the way.
Sessions move to newer agent versions
The Agenta 0.128.12 release notes list a feature that applies newer agent versions to sessions automatically. A long-running session no longer has to stay pinned to the version it started with: when a newer version of the agent exists, the session takes it up. For a team that ships agent revisions often, that removes a quiet failure mode where old sessions keep answering with old behaviour long after the fix has landed.
Channels get the final message only
A companion fix sends only the agent's final message to chat channels. Intermediate output stays out of the channel, so the people watching a Slack or chat integration see the answer, not the working. Together with the session change, this is the release's theme: what a running agent shows the world now tracks the current version and its finished output.
The rest of the patch
- The navigation rail can be dragged by its edge to collapse and open it.
- A warning appears above the composer when credits run low, and a new organization with no credit rows no longer triggers a false credit alert.
- Secret values are entered on the dock instead of in a dialog.
- The playground session page is lighter, a performance change aimed at the page teams spend their day in.
- The runner now shows ChatGPT usage-limit and unsupported-model errors to the user instead of swallowing them, and refreshes the run credential for platform tool calls on long turns.
- A Claude setup token split by a terminal line wrap is now accepted, and line breaks survive in table cells when the rich-text editor saves.
- Dependency updates include pyasn1 0.6.5 in services and MCP SDK, Vite and Vitest bumps in the runner.
Limits
- The notes describe the session and channel changes in single lines. How automatic version uptake treats a session mid-conversation, and whether it can be turned off, are not spelled out in the release list.
- Most of this patch is frontend and runner work. Teams using only the API surface will feel the credential refresh and the error display more than the interface changes.
- 0.128.12 is a patch in a fast-moving line: 0.128.11 and 0.128.10 shipped in the same list, largely carrying interface parity work. Read this release as incremental, not as a platform change.
Related playbooks
- Agenta 0.128.13: tool budgets extend the watchdog
- MCP's July spec killed sessions — tooling may not know
- Audit apps that installed agent plugins for you
- Baseten Sandboxes keep agents running for days
Sources
Back to: Coding playbooks hub · MCP Gateway Registry 1.37 tightens wildcards