Kiro CLI 2.34.0: More Control for MCP and Workflows
Kiro CLI 2.34.0 expands the V3 features for agentic development workflows. The version was released on October 23, 2026, and above all brings more control to situations in which an ongoing MCP call requires additional information.
At first, this sounds like a minor detail. In practice, however, it determines whether a workflow simply continues or gets stuck waiting for input.
MCP Calls No Longer Have to Start Over
MCP tools can request additional input during an ongoing call. To do this, they can display a form or a link. Users can provide the requested information, complete an action on another page, or reject the request.
Afterward, the MCP call continues without having to be restarted. Especially in longer or automated workflows, Kiro removes a rather unspectacular but annoying break in the process. The operation stays open, the input is added, and things continue.
This is less a grand AI demonstration than solid workflow engineering. A tool asks a question, the user responds, and the existing operation continues. Without the digital “Please start the process again.”
More Control for Workflows and Stored Memories
With Kiro CLI 2.34.0, users also gain more control over workflows. The version improves workflow recovery and adds further features for automated development workflows.
Stored memories can now also be deleted via /memories. This provides a direct way to manage this stored content instead of simply leaving it in the background indefinitely. What exactly should be deleted remains the user's decision.
There is also an editor for model selection. Kiro thus expands the options for editing the models used within development workflows. The editor is included alongside the new workflow controls and memory management, rather than being buried somewhere in the fine print of the release notes.
Sessions and Sign-In Are Expanded for Longer Workflows
According to the announcement “MCP Elicitation, Workflow Controls, and Memory Deletion,” headless MCP sign-in, stored sessions, and accessibility have also been improved. Improved workflow recovery is included as well.
The individual changes target situations in which Kiro is used for more than a short, isolated call. Stored sessions and recoverable workflows fit longer-running coding sessions, while headless MCP sign-in concerns workflows without a visible user interface. There is not much more to read into the details, but the direction is clear: The workflow should be less likely to break at the first interruption.
The announcement remains brief on accessibility. All that is clear is that it has been improved. The material does not name any specific changes.
For Operators of Their Own Projects, the Smoother Workflow Matters Most
The version is relevant for operators of their own websites or projects who use Kiro with MCP services, automated workflows, and longer-running coding sessions. For them, this is not merely a new version number, but several adjustment points around ongoing operations.
Additional input can be requested during an MCP call without restarting the call. Workflows can be recovered more effectively, sessions are stored, memories can be deleted via /memories, and model selection gets its own editor.
The grand AI magic is absent, though. In return, everyday work becomes a little less awkward, and for agentic development workflows, that is probably the more welcome news.
Sources
See more of us in Google search results: add us as a preferred source.
Add as preferred source on GoogleWritten by
Daniel Böhmel has been developing software for over 20 years and has been self-employed since 2007. He started out with interactive web design back in the Flash era; later, he built his own online projects, such as a fitness forum and a supplement store, including the editorial content. Today, his…
View the profile of Daniel BöhmelParticipate now!
Don’t have an account yet? Register yourself now and be a part of our community!