Skip to content

Kiro: Local Command Sandbox, Start Saved Workflows from Chat, and Live Tab Status

First seen · AWS / Kiro

Security fix

What the release notes say

October 13, 2026 Local Command Sandbox, Start Saved Workflows from Chat, and Live Tab Status 1.3.0 Limit what agent-run shell commands can reach, start saved Workflows from chat, and see live session status on editor tabs. This release lets you limit what agent-run shell commands can reach and start saved Workflows from chat. It also shows live session status on editor tabs, explains model fallbacks, loads MCP tools on demand, and fixes Workflow, chat, and account issues. Contain agent-run shell commands in a sandbox Turn on the local command sandbox to limit what agent-run shell commands and their child processes can access. Choose whether outbound network access is blocked, limited to common development hosts, or open. You can also run local stdio MCP servers inside the same sandbox. The agent, built-in file tools, and remote MCP servers stay outside the sandbox. Permission rules still govern agent actions. The sandbox reduces risk but cannot guarantee complete isolation, so keep reviewing proposed commands. Select Command sandbox in the status bar to open the settings and confirm the sandbox is active. Learn more -> Start saved Workflows from chat Type /workflow-run , choose a recipe, complete its inputs, and start the run. Kiro opens Workflows on the new run. Learn more -> Improvements Fixes { PREVIOUS } External Identity Provider Support for Kiro IDE { NEXT } Workflows, Safer Untrusted Workspaces, and Enterprise Sign-In Controls