Kiro Release Notes

Follow

168 release notes curated from 1 source by the Releasebot Team. Last updated: Nov 19, 2026

Get this feed:
  • Nov 18, 2026
    • Date parsed from source:
      Nov 18, 2026
    • First seen by Releasebot:
      Nov 19, 2026
    Kiro logo

    Kiro

    GitLab Installs, Permission Request Hooks, and Organization Sign-In for MCP

    Kiro adds GitLab power and skill installs, scripted responses to permission prompts, and one-time sign-in for eligible organizational MCP servers. It also lets users move chats between the sidebar and editor and adjust Memory settings.

    This release lets you install powers and skills from GitLab, answer permission prompts with a script, and sign in once to your organization's MCP servers. It also lets you move chats between the Side Bar and Editor Area and choose Memory settings from the Memories view. Install powers and skills from GitLab Paste a public GitLab URL to install a custom power or import a skill, the same way you do from GitHub. To use a self-hosted GitLab instance, add its host to the kiroAgent.powers.trustedGitLabHosts setting first. Answer permission prompts with a script Create a Permission Request Hook in the Hook editor to run a command just before Kiro would ask you to approve a tool call, so a script can answer routine prompts in a session nobody is watching. Pre Tool Use Hooks can also replace a tool call's input before it runs, and any approval prompt shows the final arguments. Sign in once to your organization's MCP servers Eligible HTTP MCP servers can share one sign-in through your organization's identity provider, instead of asking you to sign in to each server. Add the identity provider your administrator gives you to your user MCP configuration, then select Sign in on the Organization sign-in row in the MCP Servers view.

    Original source
  • Nov 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 19, 2026
    Kiro logo

    Kiro

    Organization MCP Sign-In and Custom Login Portals

    Kiro adds organization-based sign-in for MCP servers in V3 sessions, letting users authenticate once across supported servers, plus a configurable browser portal for CLI login that administrators can manage.

    This release adds organization sign-in for MCP servers in V3 sessions and a configurable portal for kiro-cli login. One sign-in through your organization's identity provider now covers every server set to use it, and you or your administrator choose where browser sign-in starts. Sign in to MCP servers through your organization In a V3 session, every MCP server you set to organization sign-in shares one sign-in through your organization's identity provider instead of a separate browser flow per server. Run kiro-cli mcp idp setup with your provider's issuer and client ID, then open /mcp and press Enter to sign in once; those servers stay disconnected until you do. For an HTTP server whose owner issued Kiro a client ID, use the --oauth-client-id <client-id> flag on kiro-cli mcp add, except when your organization's registry manages that server's OAuth. Choose the sign-in portal kiro-cli login opens Set auth.portalUrl and kiro-cli login opens that portal in your browser instead of the default one. Administrators can set the portal for their users through the AuthPortalUrl policy or auth_portal_url in managed-settings.json. If Kiro cannot use that value, it falls back to the default portal.

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Kiro and hundreds of other software products.

    Create account
  • Nov 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    • Modified by Releasebot:
      Nov 18, 2026
    Kiro logo

    Kiro

    Local Sandbox Controls in Enterprise Management

    Kiro adds preview enterprise controls for local sandboxing in the IDE and CLI, letting administrators require sandboxing and set file and network defaults while enforcing organization policies. Available in US East for supported identity profiles and recent client versions.

    Enterprise administrators can now set local sandbox controls for Kiro IDE and Kiro CLI. In Controls, require sandboxing for commands and local stdio MCP servers, and choose file and network defaults. Developers cannot turn off a required sandbox through client settings or change organization-set modes. Their allow rules cannot override organization deny rules, and tool permissions still decide which commands may run. Credential stores stay closed by default, but a file allow rule that covers them can open them.

    Enterprise Management is in preview in US East (N. Virginia) (us-east-1) for profiles using IAM Identity Center or an external identity provider. Developers need Kiro CLI 3.4.0 or later or Kiro IDE 1.4.215 or later.

    Original source
  • Nov 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    • Modified by Releasebot:
      Nov 18, 2026
    Kiro logo

    Kiro

    Migrate Existing Profiles to Controls

    Kiro now lets enterprise admins move existing profiles to Enterprise Management in a one-way preview for US East, with settings mapped to Controls.

    Enterprise administrators can now move existing Kiro profiles to Enterprise Management. The preview covers US East (N. Virginia) (us-east-1). Profiles can use IAM Identity Center or an external identity provider.

    When Settings offers Migrate to the new experience, preview the mapping. Kiro copies your current settings to Controls. Overages, the encryption key, and member account subscriptions stay on Settings. The move is one-way.

    Original source
  • Nov 16, 2026
    • Date parsed from source:
      Nov 16, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    • Modified by Releasebot:
      Nov 18, 2026
    Kiro logo

    Kiro

    Fork Conversations, Workflow Credits, and Cloud Sessions in Europe (Frankfurt)

    Kiro adds chat forking, workflow credit visibility, clearer Memory levels, parallel custom-agent and Plan chats, and IDE cloud sessions in Frankfurt.

    This release lets you fork a chat from any turn, so you can try a different prompt from the same point without losing the original. It also shows the credits a workflow run reports, gives the Memory levels clearer names, and lets chats that use a custom agent or Plan run at the same time as other chats. Kiro profiles in Europe (Frankfurt) can also use cloud sessions from the IDE.

    Original source
  • Similar to Kiro with recent updates:

  • Nov 16, 2026
    • Date parsed from source:
      Nov 16, 2026
    • First seen by Releasebot:
      Nov 17, 2026
    • Modified by Releasebot:
      Nov 17, 2026
    Kiro logo

    Kiro

    Terminal in Kiro Web

    Kiro Web now adds a workspace terminal, letting users run builds, tests, and commands alongside their conversation.

    You can now run commands in your session's workspace right in Kiro Web. Open a terminal beside the conversation or below it to run builds and tests, check output, or try a command yourself.

    Original source
  • Nov 16, 2026
    • Date parsed from source:
      Nov 16, 2026
    • First seen by Releasebot:
      Nov 17, 2026
    • Modified by Releasebot:
      Nov 17, 2026
    Kiro logo

    Kiro

    Hooks That Rewrite Tool Inputs and Answer Permission Prompts

    Kiro adds hooks that can rewrite tool inputs or approve and deny permission requests in V3 sessions, helping teams apply rules automatically. The release also brings more memory choices, broader cloud session support, and fixes across several workflows.

    This release adds hooks that rewrite a tool call's inputs before it runs or answer its permission prompt, so a script can apply your team's rules to every tool call in V3 sessions instead of waiting on you to approve each one. It also offers four /memories choices, resumes and lists cloud sessions in more places, and fixes headless, context window, MCP, search, /tangent, /rewind, and display issues.

    Rewrite a tool call or answer its permission prompt from a hook

    In a V3 session, a PreToolUse hook can now return updatedInput to replace a tool call's inputs before the tool runs, alongside its allow, ask, or deny decision. A new PermissionRequest hook runs when a tool call would ask you for permission and can answer with allow or deny, so a script grants or refuses a call that would otherwise wait on you. A deny from any hook wins over an allow, and a hook's permission answer applies to that one tool call only.

    Original source
  • Nov 16, 2026
    • Date parsed from source:
      Nov 16, 2026
    • First seen by Releasebot:
      Nov 17, 2026
    • Modified by Releasebot:
      Nov 17, 2026
    Kiro logo

    Kiro

    Real-time events and private connectivity

    Kiro now lets Enterprise administrators export richer activity data to observability tools through real-time OpenTelemetry events, daily metrics, and CSV reports. Exports track usage and outcomes while excluding prompts, responses, code, and files, with public or private delivery options.

    Kiro Enterprise administrators can now send richer activity data to their observability tools. Stream each LLM request and completed tool call as a real-time OpenTelemetry event, or use daily CSV reports and OpenTelemetry metrics for reconciled trends. Track credits, models, conversations, response times, tool outcomes, client versions, and agent modes. Real-time events and private connectivity are available for Kiro profiles in US East (N. Virginia) and Europe (Frankfurt).

    Daily metrics move to 00:30 UTC on November 26, 2026. Until then, Dynatrace and Grafana Cloud reject them as too old. The CSV report stays at 02:00 UTC.

    Choose public delivery, AWS PrivateLink, or Amazon VPC Lattice for OpenTelemetry. Private connections never fall back to public delivery. Exports include usage data and user identifiers. They exclude prompts, responses, code, and files. Turn on and test each export in the Kiro console.

    Original source
  • Nov 13, 2026
    • Date parsed from source:
      Nov 13, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    • Modified by Releasebot:
      Nov 18, 2026
    Kiro logo

    Kiro

    Kiro Web in Europe (Frankfurt)

    Kiro expands Kiro Web availability to profiles in Europe, hosted in Frankfurt.

    Kiro Web is now available for Kiro profiles in Europe (Frankfurt) (eu-central-1).

    Original source
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 14, 2026
    Kiro logo

    Kiro

    Kiro Mobile for Android

    Kiro launches its Android mobile app on Google Play, bringing cloud coding sessions, live agent updates, image attachments, file diffs, and pull request status to your phone. Existing sessions, repositories, and model choices sync with Kiro Web, the IDE, and CLI.

    Kiro Mobile is now available on Google Play, so you can work in Kiro cloud sessions from your Android phone. Your laptop doesn't need to stay on. Sign in with your Kiro account, and your sessions, connected repositories, and model choices are already there. Kiro Mobile requires a Pro, Pro+, Pro Max, or Power plan.

    Follow, Steer, and Review Sessions from Your Phone

    Start a cloud session, or pick up one you started in Kiro Web, the IDE, or the CLI. Choose your repositories and a model, and turn on Build with spec to plan first. In Autonomous mode, the model selector shows Auto and cannot be changed. Follow replies and tool activity live, attach images, answer the agent's questions, or stop a run. Each edited file appears as a phone-sized diff card, and each session shows its pull request status. You review and merge in your Git provider.

    Original source
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 14, 2026
    Kiro logo

    Kiro

    Follow Workflow Runs, Skills After Compaction, and Readable Diagrams

    Kiro adds step-by-step workflow tracking, reloads requested guidance after compaction, improves Mermaid readability, and fixes freezes, stalls, and reload issues.

    This release lets you follow a workflow run step by step from its Workflow tab. After Kiro compacts a conversation, the agent now reloads the skills and steering files you asked for. Large Mermaid diagrams in chat also stay readable. Fixes cover freezes after a permissions change, stalls before large file writes begin, and missed reloads after you edit configuration on a Windows network drive.

    Original source
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 14, 2026
    Kiro logo

    Kiro

    Copy Earlier Responses and Choose When Compaction Starts

    Kiro adds flexible copying of earlier responses and recent conversation messages, plus controls for when automatic context compaction starts. The release also improves agent monitoring and workflow recovery, tightens upgraded agent permissions, and fixes several session, voice, clipboard, and display issues.

    This release adds /copy N and /copy last N, so you can copy an earlier response or the last few messages, and lets you choose the context usage at which automatic compaction starts. It also shows each sub-agent's task in the agent monitor, moves the /model search, sort, and edit controls to Up, keeps a V2 agent's allow rules from widening when it is upgraded to V3, reloads a stalled workflow session after an agent restart, and fixes headless, resume, /memories, /goal, voice, clipboard, session, and search display issues.

    Copy an earlier response or the last few messages

    /copy still copies the latest response. Run /copy N to copy the Nth-latest response instead, so /copy 2 copies the one before the latest. Run /copy last N to copy the latest N messages, oldest first, whether they are your prompts or Kiro's replies; each prompt is labeled You: and each reply Kiro:. A reply split around tool calls counts as one message. For the whole conversation, use /transcript.

    Choose when automatic compaction starts

    In a V3 session, run /settings and open Compaction to see the threshold your current session uses and set a global default: the context usage percentage at which Kiro summarizes older history. The editor shows the accepted range and the default, and your value applies to the next session you start or load. The same screen turns automatic compaction on or off. The value is saved as compaction.autoCompactionThreshold, and a workspace cli.json can override it.

    Original source
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Kiro logo

    Kiro

    Audit Kiro Tool Calls with AWS CloudTrail

    Kiro now logs service MCP tool calls in CloudTrail, helping security teams audit requests across supported US and Europe regions.

    Kiro now records calls to Kiro service MCP tools in AWS CloudTrail for Kiro profiles in US East (N. Virginia) (us-east-1) and Europe (Frankfurt) (eu-central-1). Security and audit teams can see who made a request, which tool was called, when it ran, and whether it completed.

    CloudTrail logs privileged tool calls as management events by default. Administrators can also log tool listings and read-only tool calls by enabling data events. Events redact tool arguments and omit results. This logging covers Kiro service tools only, not MCP servers added to Kiro.

    Original source
  • Nov 11, 2026
    • Date parsed from source:
      Nov 11, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Kiro logo

    Kiro

    Output Details and Sign-In Fixes

    Kiro adds configurable tool-call output detail for everyone and fixes Linux sign-in, model fallback, workflows, Skills, search, permissions, and reloads.

    This release brings Output details to everyone: choose in /settings how much detail tool calls show, from one line per call to the full output. It also fixes sign-in on Linux hosts with no graphical session and with Identity Center flags, keeps /model fallback settings working, and fixes workflow, spec, Skills, file search, permissions, and session reload issues.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Kiro logo

    Kiro

    Enterprise Management preview: one policy for every Kiro client

    Kiro introduces Enterprise Management preview for new profiles in US East, letting administrators apply shared policies across the IDE, CLI, Web, and Kiro Crew LTS. The new Crew LTS edition adds organization-specific controls for agent access, messaging, scheduled jobs, and more.

    In preview for new Kiro profiles created in US East (N. Virginia).

    Kiro Enterprise Management is in preview. It is available to newly created Kiro profiles in US East (N. Virginia) (us-east-1): create a profile there and the Controls page is already in your console, with no setup step. Support for existing profiles and for profiles in Europe comes later. Administrators write one policy in the AWS console, and every developer on the profile gets it in the Kiro IDE, Kiro CLI, Kiro Web, and Kiro Crew LTS. Kiro IDE users need version 1.4.154 or later; Kiro CLI users need version 3.1.0 or later. A policy has three parts: rules that allow, deny, or ask before Kiro uses a model, runs a shell command, reads or writes a file, searches the web, or calls an MCP tool; settings such as the default model, prompt logging, and usage reports; and the steering files, Skills, and Powers you choose to distribute to developers. A rule can apply to everyone on the profile, to one group, or to one user. It works with IAM Identity Center, Okta, or Microsoft Entra ID as the identity source.

    Models, API keys, and Kiro Crew messaging and network access are denied until a rule allows them; files, shell, web, MCP, and Kiro Crew scheduled jobs keep Kiro's own default until a rule names them.

    Kiro Crew LTS

    Kiro Crew LTS is the Kiro Crew edition for organizations that govern Kiro with Enterprise Management, and it applies two layers of rules. The first is the same policy every Kiro client gets: your rules for models, shell commands, file reads and writes, and MCP tool calls apply inside Crew too. The second is specific to Crew: which messaging channels the agent may connect to, whether it may message people, which approval modes a user may pick (auto-approve stays off unless a rule allows it), whether scheduled jobs run, which hosts its fetch tool may reach, whether the agent may drive its web browser, whether the dashboard may be opened from other devices on a Tailscale tailnet, and whether users may install third-party dashboard themes. Feature Previews and Debug tools stay off. It installs beside the regular Kiro Crew app and updates only from its own lts channel.

    Before you open Kiro Crew LTS, sign in with Kiro CLI through your organization's single sign-on (IAM Identity Center or your external identity provider), not a personal account. Kiro Crew LTS has no sign-in dialog of its own: if you are not signed in, you may see a gateway error that tells you to sign in from the CLI. Sign in, then choose Retry. It needs a Kiro profile created in US East (N. Virginia) with Enterprise Management on.

    PLATFORM DOWNLOAD

    • macOS (universal) KiroCrew-LTS.dmg
    • macOS (Apple silicon) KiroCrew-LTS-arm64.dmg
    • Linux (x86_64) KiroCrew-LTS-x86_64.AppImage
    • Windows KiroCrew-LTS-Setup.exe
    • Python wheel kirocrew_lts-0.1.0-py3-none-any.whl

    Replace 0.1.0 with latest in the desktop app links for the newest LTS app build. To install Kiro Crew from the command line on the LTS channel:

    curl -fsSL https://download.crew.kiro.dev/cli.sh | sh -s -- --channel lts
    
    Original source
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.