Docs Browse feeds Latest Sign in Create account

AI Coding Assistants Release Notes

Release notes for AI-powered coding assistants, editors and agents

Get this feed:

Latest AI Coding Assistants Updates

September 2026
No date parsed from source.

First seen by Releasebot:
Sep 3, 2026
Claude Code by Anthropic

2.1.259

Claude Code adds managed MCP servers, unattended headless permission controls, GitLab MR recognition, JSON plugin validation, faster startup and workflow views, plus broad fixes for concurrency, resume, permissions, remote sessions, and stability.
Added

Added managedMcpServers managed setting: organizations can provide HTTP/SSE MCP servers to every user (same entry shape as .mcp.json); entries that name a command to run are skipped

Added --permission-prompts none for unattended headless hosts: anything that would prompt is denied automatically while the active permission mode (including auto mode) keeps deciding

Added recognition of glab mr create/merge/close/reopen/note/update so GitLab merge requests show as MR !N in the collapsed tool summary and refresh the footer MR badge

Added --json to claude plugin validate for a machine-readable validation report

Fixed

Fixed concurrent sessions silently reverting each other's ~/.claude.json changes — workspace trust no longer resets and MCP/project state is no longer lost when running many sessions at once

Fixed a conversation whose thinking was rejected once being rejected again on every later turn

Fixed Bash Read() deny rules not covering files given as option values (--ignore-revs-file=.env, -f.env, @file), git diff/git grep file operands, or cd DIR && cat FILE compounds; grep -r/cp -r over a directory holding a denied file now asks

Fixed the prompt cache being invalidated when the OAuth token refreshed in sessions with telemetry disabled

Fixed fullscreen mode showing a blank conversation after a long turn with hundreds of tool calls

Fixed auto mode running a turn on a model it doesn't support when a command or skill's frontmatter model: named one; the turn now keeps the session model

Fixed CLAUDE_CODE_MAX_CONTEXT_TOKENS being ignored for Vertex-style model IDs (@YYYYMMDD suffix) of model versions Claude Code doesn't recognize

Fixed the live output preview of a running shell command hiding its newest lines when an earlier line wrapped

Fixed a background GitHub connection check that ran on every launch for claude.ai users; the result is now remembered across launches

Fixed --resume failing (and --continue opening an empty conversation) when a saved session contains an attachment entry with no payload

Fixed frontmatter model: on custom commands and skills being ignored in interactive sessions

Fixed Artifact publishing failing once with an "unexpected parameter note" error in conversations continued from an older version

Fixed managed forceRemoteSettingsRefresh being ignored at startup when a policy helper configured by MDM or the managed settings file had already run

Fixed worktree isolation refusing hook-created worktrees on machines where git rev-parse fails with a message other than "not a git repository"

Fixed OpenTelemetry metrics and events from cloud sessions missing the user.email, organization.id, and user.account_uuid attributes

Fixed MCP servers that disconnect while their tools are being listed at startup showing as connected with no tools instead of reporting the error

Fixed the file edit permission dialog sometimes showing a changed line cut short with no indication

Fixed repository detection dropping a known repo identity after a transient git probe failure

Fixed managed settings silently going unenforced when the managed-settings file, a drop-in, the MDM plist, or the HKLM value cannot be parsed: Claude Code now refuses to start and names the source

Fixed Stop not actually stopping background agents and workflows in remote-control sessions: killed tasks now stay visible and re-stoppable until their processes exit

Fixed resuming a workflow run while its previous stopped run was still exiting, which could run duplicate copies of its agents

Fixed marketplace repo URLs on github.com with a trailing slash or dangling ?/# producing an unusable .git clone URL

Fixed blocking Stop hooks causing the turn after a block to lose the model's reasoning from that turn and, on some models, miss the prompt cache

Fixed remote (claude.ai) sessions taking 60 seconds to start a turn after a browser-hosted MCP server's page had gone away

Fixed worktree-isolated sessions refusing common Bash loops, xargs pipelines and launcher-wrapped commands that cannot reach the main checkout

Improved

Improved terminal resize and first-render performance for long responses by reusing text measurements

Improved /workflows agent detail: JSON outcomes are pretty-printed with syntax colors and real line breaks, and long outcomes fold behind an expand toggle

Improved headless/SDK session start: the first turn begins up to 50 ms sooner when MCP servers finish connecting

Improved /install-github-app to explain it is GitHub-only and point to the GitLab CI/CD docs when run inside a GitLab repository

Improved nested background subagent results to be saved in the parent subagent's transcript, so resumed subagents keep them and shared transcripts show the delivery

Changed

Changed allowedMcpServers to govern only servers users add: a literal managed-mcp.json server your allowlist used to filter out now loads on upgrade; use deniedMcpServers to keep it off

VSCode

[VSCode] Added an Active quick filter and a status filter menu (Needs input, Working, Completed) to the session list sidebar

Fixed

Fixed remote and scheduled sessions doing nothing after a connector-tool permission prompt was approved while the session was paused

Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 3, 2026
Kilo by Kilo Code

v7.5.9 (release)

Kilo ships minor updates to Agent Manager, VS Code, and the CLI, including local app previews, editable queued messages, richer heartbeat info, clearer background agent status, faster long-session forking, and broader controls for subagents and worktrees.
7.5.8

Minor Changes

#13501 9231c25 - Preview local applications in Agent Manager with embedded developer tools, grouped diagnostics, and review-style element feedback for precise frontend changes.

#13556 52d4247 - Edit queued messages in VS Code before they are sent, while preserving their text and attachments.

#13565 49692a6 - Advertise optional instance kind, process start time, and current Git branch in CLI heartbeats.

#13557 6624c1a - Allow the orchestrating agent to choose a model, provider, and reasoning effort for each subagent task behind an experimental setting.

#13645 cd366ce - Show CLI activity in Agent Manager terminal tabs and worktree indicators, including working, waiting for input, retrying, errors, and completed tasks.

Patch Changes

#13630 242bb18 - Use the Agent Manager panel for terminals by default when no destination is configured, while preserving existing choices.

#13663 17bb54d - Keep finished background agents in the compact header with status icons, and automatically collapse their list when all agents finish.

#13666 2e76572 - Speed up forking long sessions while preserving conversation history and independent child sessions.

#13646 e803815 - Fix the invisible collapse icon in the background agents panel.

#13637 36804b0 - Fix an empty extension sidebar after installing a build with browser automation support.

#13597 915b4a2 - Show live activity indicators for subagent tabs in Agent Manager, including running, retrying, waiting for input, completed, and error states.

#13468 32e4b0a - Release worktree processes and terminals before removing Agent Manager worktrees on Windows.

#13601 438dbe7 - Show deliberately stopped agent sessions as idle instead of finished.

#13641 dd390c1 - Support stopping the main agent without cancelling background agents, and add Stop all to the VS Code background-agent bar.

#13650 a6bdd6f - Keep Agent Manager inspector panels open during state updates when browser automation is disabled.

#13665 bb87cc8 - Open all background agents at once with compact, matching toolbar controls.

#13667 1d8689f - Match answered question text to other tool output and respect the Kilo font size setting.

#13610 b5ee423 - Restore Agent Manager side panels for each project, worktree, and session when navigating, while keeping closed panels closed.

#13605 25d9448 - Stop checking for unsupported legacy Kilo migrations at startup while keeping Roo Code session import available.

#13604 edb929d - Keep background agent spinners animating smoothly during status updates.

#13602 0701c5f - Allow subagent task headers to collapse and share the saved timeline preference with the main agent.

#13603 08757f7 - Reduce empty space below the chat prompt in wide Agent Manager panes while preserving the side margins.

Updated dependencies [7c845aa, dd390c1, 6624c1a]:

@kilocode/[email protected]

@kilocode/[email protected]

@kilocode/[email protected]

@opencode-ai/[email protected]

@opencode-ai/[email protected]

@kilocode/[email protected]

@kilocode/[email protected]

Original source
All of your release notes in one feed

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

Create account
Get updates with:
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 3, 2026
Kilo by Kilo Code

v7.5.8 (pre-release)

Kilo adds Agent Manager and VS Code workflow upgrades, including local app previews, queued message editing, richer CLI and subagent status updates, and better background agent controls, while also improving session handling, Windows cleanup, and overall UI stability.
Minor Changes

#13501 9231c25 - Preview local applications in Agent Manager with embedded developer tools, grouped diagnostics, and review-style element feedback for precise frontend changes.

#13556 52d4247 - Edit queued messages in VS Code before they are sent, while preserving their text and attachments.

#13565 49692a6 - Advertise optional instance kind, process start time, and current Git branch in CLI heartbeats.

#13557 6624c1a - Allow the orchestrating agent to choose a model, provider, and reasoning effort for each subagent task behind an experimental setting.

#13645 cd366ce - Show CLI activity in Agent Manager terminal tabs and worktree indicators, including working, waiting for input, retrying, errors, and completed tasks.

Patch Changes

#13630 242bb18 - Use the Agent Manager panel for terminals by default when no destination is configured, while preserving existing choices.

#13663 17bb54d - Keep finished background agents in the compact header with status icons, and automatically collapse their list when all agents finish.

#13666 2e76572 - Speed up forking long sessions while preserving conversation history and independent child sessions.

#13646 e803815 - Fix the invisible collapse icon in the background agents panel.

#13637 36804b0 - Fix an empty extension sidebar after installing a build with browser automation support.

#13597 915b4a2 - Show live activity indicators for subagent tabs in Agent Manager, including running, retrying, waiting for input, completed, and error states.

#13468 32e4b0a - Release worktree processes and terminals before removing Agent Manager worktrees on Windows.

#13601 438dbe7 - Show deliberately stopped agent sessions as idle instead of finished.

#13641 dd390c1 - Support stopping the main agent without cancelling background agents, and add Stop all to the VS Code background-agent bar.

#13650 a6bdd6f - Keep Agent Manager inspector panels open during state updates when browser automation is disabled.

#13665 bb87cc8 - Open all background agents at once with compact, matching toolbar controls.

#13667 1d8689f - Match answered question text to other tool output and respect the Kilo font size setting.

#13610 b5ee423 - Restore Agent Manager side panels for each project, worktree, and session when navigating, while keeping closed panels closed.

#13605 25d9448 - Stop checking for unsupported legacy Kilo migrations at startup while keeping Roo Code session import available.

#13604 edb929d - Keep background agent spinners animating smoothly during status updates.

#13602 0701c5f - Allow subagent task headers to collapse and share the saved timeline preference with the main agent.

#13603 08757f7 - Reduce empty space below the chat prompt in wide Agent Manager panes while preserving the side margins.

Updated dependencies [7c845aa, dd390c1, 6624c1a]

@kilocode/[email protected]

@kilocode/[email protected]

@kilocode/[email protected]

@opencode-ai/[email protected]

@opencode-ai/[email protected]

@kilocode/[email protected]

@kilocode/[email protected]

Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 3, 2026
Cursor

Self-hosted machines

Cursor adds self-hosted machines for local tool execution, keeping code, builds, and secrets inside your network. It also brings dynamic machine pools, support for cloud agents on existing infrastructure, and computer use on Linux and Mac for browser and desktop control.

Cursor supports self-hosted machines, which let you keep tool execution entirely in your own network.

Your codebase, build outputs, and secrets all stay on internal machines running in your infrastructure, while the agent handles tool calls locally.

Dynamic pool scheduling

My Machines connects a single laptop or VM to your account for personal workflows.

Team pools are named queues of workers for a team or enterprise. Capacity can grow as requests arrive and shrink when workers disconnect, so your self-hosted machines can scale with demand. Pools are not tied to one repository: name the pool, and any available worker can claim the request.

Pools can also hibernate idle machines, then restore within a reconnect window when a follow-up arrives, so you don't keep expensive capacity warm just for the next prompt.

Run on your sandboxes

Cloud agents can now execute on infrastructure you already use, including from AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B.

Computer use on Linux and Mac

Self-hosted workers now support computer use on Linux and Mac. With the right desktop packages, an agent can click, type, take screenshots, and drive the browser. You can watch its desktop or take control from Cursor.
Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 2, 2026
Cursor

Run cloud agents on machines you manage

Cursor adds Self-Hosted Machines for cloud agents, letting teams run agents on their own infrastructure while Cursor still manages planning and orchestration. It also expands pool scaling, sandbox provider support, and Linux computer use for more flexible, secure agent workflows.
Cursor cloud agents can execute on dynamically scheduled pools of machines inside your network. You manage the underlying infrastructure, while agents are still started and managed from Cursor.

This gives teams more control over where agents execute and what infrastructure they use. Agents can work next to internal services and source control, run on custom hardware, or use operating systems and build pipelines that are difficult to package as a Cloud Agent build.

Cloud agents now create more than 60% of the pull requests we merge internally and are taking on a growing share of software work at many of the largest enterprises we work with. As their role expands, the machines they run on matter more too. These new capabilities make it practical for teams to provide and manage that infrastructure at scale.

With Lambda MicroVMs as the compute layer for Cursor Cloud Agents, developers can run AI-powered coding agents in their own AWS account. Each machine launches near-instantly from a snapshot, suspends when idle, and resumes with full state. Your coding agents benefit from Lambda's fast startup, strong isolation, and zero fleet management, while Cursor orchestrates the work.

Control where agents execute

Cursor-hosted environments remain the default for cloud agents. Each session runs on a dedicated VM inside the Cursor cloud, with its dependencies installed and its own network controls. Per-agent isolation, secret redaction, egress controls, and signed commits meet the security requirements of most teams.

Teams generally use Self-Hosted Machines when:

Agent tool execution needs to happen inside their network, with direct access to source control, internal services, and code repositories.

Agents require custom hardware, such as GPUs or Macs for iOS development, or infrastructure such as Kubernetes, sandboxes, or managed VMs.

Their operating system or build pipeline is difficult to package as a Cloud Agent build.

With Self-Hosted Machines, only the execution environment moves while the agent loop, inference, and planning remain in the Cursor cloud. Tool outputs flow back to Cursor for inference and may contain code, and agent transcripts may be processed and stored by Cursor. Teams can continue to access cloud agents from the desktop app, cursor.com, mobile, Slack, GitHub, and Linear.

Workers connect your infrastructure to the Cursor agent loop

With Self-Hosted Machines, tool execution moves from a Cursor-hosted VM to a machine in your environment. That machine holds the working copy of the repository, edits files, and runs commands. A worker connects it to the rest of the agent system.

To register a machine, run a worker by installing the Cursor CLI and running

agent worker start

This opens a long-lived outbound HTTPS connection to the Cursor cloud. When a session begins, Cursor's agent harness handles inference and planning, then sends tool calls to a dedicated worker for execution. The worker returns the results for the next round of inference. Cursor never initiates a connection into your network.

Workers can be configured in two ways.

My Machines. This configuration connects a single laptop or VM to your account and is best suited to personal workflows.

Pools. A pool is a named queue of workers that can serve a team or enterprise. Capacity increases as requests arrive and decreases after workers disconnect, letting your existing cloud infrastructure scale with developer demand.

Developers should have the flexibility to run coding agents on the platform that best supports their workflow, and companies should not have to compromise on control of where agents run and what they can access. The future of development will be built on powerful agents, running in secure, isolated environments.

Cloud agents adapt to your infrastructure

Worker pools can now scale in response to queued requests and serve work from any repository. We have also added support for several sandbox providers and computer use on Linux alongside Mac.

Pools scale with demand and serve any repository

Demand for cloud agents often arrives in bursts and Self-Hosted Machines pools adjust to those bursts automatically. This happens through a controller which watches the request queue and uses a spawn script supplied by the team to start machines as needed.

If a pool has an available worker, that worker claims the request. Otherwise, the request waits until more capacity becomes available, so teams do not have to decide how many machines to leave running.

Teams can set an idle timeout for each worker connection. Once it expires, the machine can reset and re-enter the pool. Teams can also preserve its workspace in case the agent receives a follow-up.

Self-Hosted Machines put teams in control of where Cursor agents run, and Vercel Sandbox makes it effortless. Every task gets an isolated sandbox on demand, no fleet to manage, and nothing sitting idle.

Leaving a machine running while its agent is idle can be expensive. But if the machine is released, the agent may need several minutes to reconstruct its workspace when a follow-up arrives. With hibernation, teams can snapshot and stop an idle machine instead. If a follow-up arrives within the reconnect window, the snapshot is restored and a worker starts with the same ID. Otherwise, the request can move to a new machine.

Pools are not tied to individual repositories. A request only needs to identify the pool, and any available worker can claim it. This lets one pool serve many repositories.

Workers run across supported sandbox providers

Self-Hosted Machines does not require building a custom sandbox layer from scratch. We partner with AWS Lambda, Cloudflare, Coder, Daytona, E2B, Modal, Namespace, and Vercel, allowing workers to be started and orchestrated wherever a team's sandboxes already run.

Cursor Self-Hosted Machines on Modal gives each Cloud Agent session a Modal Sandbox, so you can hand it a machine tailor-made for its task.

Agents control browsers on Linux and Mac

Linux workers now support computer use alongside Macs. With the required computer use dependencies installed, including Chrome or Chromium, an agent can click, take screenshots, and control the browser. You can watch its desktop or take control directly from Cursor.

You can't build iOS or macOS apps without a Mac. Namespace Devboxes spin up a real Mac for each Cursor Cloud Agent, which can now perform that work on Apple silicon.

Bring cloud agents into your environment

Teams have spent years shaping their infrastructure around how they build software. Self-Hosted Machines lets cloud agents fit more naturally into it, and we're excited to see how far teams take them.

To connect a machine or configure a pool, get started in the docs.
Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 2, 2026
opencode by SST

v1.18.27

opencode fixes provider timeout handling and Anthropic compatibility, making slow model startups and streamed reads more reliable while reducing request rejections on older Claude deployments.
Core

Bugfixes

Default provider header timeouts to five minutes so slow model startups fail less often.

Default streamed chunk timeouts to five minutes, with false supported to disable them.

Let Anthropic thinking.blockBinding opt out via config when you need to keep the provider default. (@dkindlund)

Limit Anthropic thinking block binding to Claude 5.1+ models so older deployments do not reject requests.

Avoid unhandled errors when canceling timed-out SSE reads. (@AlexanderWillner)

Thank you to 2 community contributors:

@AlexanderWillner:

fix(provider): handle SSE reader cancel rejections (#44944)

@dkindlund:

fix(opencode): let config opt out of Anthropic thinking blockBinding (#46820)
Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 2, 2026
Devin CLI by Devin

v3000.6.12

Devin CLI fixes a regression in MCP server connections via Streamable HTTP.
Fixed

Repaired a regression connecting to MCP servers via Streamable HTTP that was introduced in v3000.6.11

Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 2, 2026
Kimi Code by Kimi

@moonshot-ai/[email protected]

Kimi Code fixes the kimi-cli migration prompt condition in a patch update.
Patch Changes

#3469 979baad Thanks @sailist! - Fix the condition for showing the kimi-cli migration prompt.

Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 2, 2026
Kimi Code by Kimi

@moonshot-ai/[email protected]

Kimi Code ships web and CLI updates with a new Plugins panel, faster session forks, stronger command safety, improved Tower mode controls, and many fixes for web chat, config handling, and session state.
Minor Changes

#3434 ae7a6dc Thanks @sailist! - The kimi acp subcommand no longer honors KIMI_CODE_LEGACY_FLAG; it always runs on the default agent engine.

#3334 971a8b2 Thanks @7Sageer! - The subagent model pool ([secondary_model]) is enabled by default in every launch mode and remains opt-out via KIMI_CODE_EXPERIMENTAL_SECONDARY_MODEL=0 or [experimental] secondary-model = false.

#3454 913a242 Thanks @wbxl2000! - web: Added a Plugins panel to Settings for browsing the plugin marketplace and installing, enabling, disabling, and removing plugins.

Patch Changes

#3444 b4ae7f8 Thanks @sailist! - Remove the workspace restriction on the Bash tool's cwd parameter.

#3454 913a242 Thanks @wbxl2000! - web: Added a code wrap toggle to the diff panel and streamlined its header.

#3454 913a242 Thanks @wbxl2000! - web: Fixed new content not appearing after auto-compaction (stuck at "Requesting…" above the divider); output after the compaction point now renders below the divider.

#3392 616d510 Thanks @7Sageer! - Preserve comments, key order, and formatting in config.toml when configuration values are updated.

#3348 9d2304c Thanks @liukx0205! - Fix models and providers transiently disappearing when config.toml is saved non-atomically by an external editor while the daemon reloads it.

#3454 913a242 Thanks @wbxl2000! - web: The connecting splash screen now shows the current loading stage and the reason when the connection fails.

#3290 4b9888b Thanks @sailist! - Block dangerous shell commands such as shutdown, reboot, or rm -rf in Auto mode, and always ask before running them in Manual and YOLO modes; disable the guard with [permission] dangerous_command_guard = false or KIMI_CODE_DANGEROUS_COMMAND_GUARD=false.

#3454 913a242 Thanks @wbxl2000! - web: Fixed queued or steered messages being unexpectedly retracted by pressing Esc after they start running.

#3421 9c37feb Thanks @sailist! - Make session forks much faster.

#3454 913a242 Thanks @wbxl2000! - web: Show a refresh button in the right-sidebar file preview when the previewed file is edited mid-turn.

#3454 913a242 Thanks @wbxl2000! - web: Fixed the server-side attachment notice text leaking into your own message bubble after sending a file.

#3454 913a242 Thanks @wbxl2000! - web: Fixed misaligned content in the composer attachment tooltip.

#3454 913a242 Thanks @wbxl2000! - web: Fixed messages sent with Ctrl+S while the agent is running disappearing after a page reload.

#3454 913a242 Thanks @wbxl2000! - web: Fixed sessions occasionally stuck showing "working" after a message is appended mid-turn.

#3377 58b74cf Thanks @chengluyu! - Fix duplicate user messages in transcript clients.

#3454 913a242 Thanks @wbxl2000! - web: Fixed the first pinyin letter being committed as English text in Chinese IMEs after enabling goal or plan mode.

#3454 913a242 Thanks @wbxl2000! - web: Fixed sessions occasionally stuck showing "working" long after the reply had completed.

#3427 442b563 Thanks @sailist! - Honor explicit [experimental] config entries over the KIMI_CODE_EXPERIMENTAL_FLAG master switch, so a flag set to false in config.toml stays off; per-feature KIMI_CODE_EXPERIMENTAL_<NAME> variables still override both.

#3412 7bc5b20 Thanks @7Sageer! - Send the forked-subagent context notice as a system reminder.

#3415 82bf0a8 Thanks @kimi-agent-bot! - Parse git status --porcelain with -z so non-ASCII paths are no longer mangled into bogus quoted directory segments.

#3454 913a242 Thanks @wbxl2000! - web: Pressing Tab in the @ file menu completes the highlighted candidate's name into the input while keeping the menu open for further filtering.

#3454 913a242 Thanks @wbxl2000! - web: Support activating multiple skills from a single message.

#3454 913a242 Thanks @wbxl2000! - web: Background task notification cards now show a "Sent from background · bash" source line and a single "status: task description" body line.

#3454 913a242 Thanks @wbxl2000! - web: Background task notification cards now label the sender as "Sent from background (Bash) / (Agent)".

#3454 913a242 Thanks @wbxl2000! - web: Superseded @ file searches are now cancelled promptly during fast typing, reducing background load.

#3371 9e88152 Thanks @tpoisonooo! - Fix prompts remaining queued forever after reopening a session.

#3454 913a242 Thanks @wbxl2000! - web: Fixed manually typed > quote blocks in messages being misrendered as quote annotations; they now render as plain text.

#3454 913a242 Thanks @wbxl2000! - web: Fixed messages rejected by the server sometimes showing no failure toast.

#3425 ceb5153 Thanks @sailist! - Add the kimi session list command to list sessions from the command line.

#3390 76c1a7a Thanks @Grapedge! - Simplify the built-in system prompt.

#3454 913a242 Thanks @wbxl2000! - web: Selecting a skill from the slash menu now inserts the same skill pill as the @ menu.

#3454 913a242 Thanks @wbxl2000! - web: Fixed stale steered-message bubbles lingering after a transcript refresh.

#3454 913a242 Thanks @wbxl2000! - web: Fixed the file-change summary card appearing too early when a turn is steered while still running.

#3436 0f39b2c Thanks @wbxl2000! - Fix idle sessions briefly showing a "Working" state when opened in desktop and web clients.

#3346 ece9618 Thanks @tpoisonooo! - Tower mode (experimental, KIMI_CODE_EXPERIMENTAL_TOWER=1): spawned workers now start from the base checkout's uncommitted changes instead of missing them, and TowerMerge refuses to merge while the checkout still holds those changes uncommitted. Also, a new session can now enter tower mode after the previous owning session stopped without exiting, instead of being refused while that session stays open. Tower mode now stays on after tower teardown; turn it off explicitly with /tower off. Tower mode is now mutually exclusive with plan mode and swarm mode: entering any one of them exits the others.

#3399 c3bf6f9 Thanks @tpoisonooo! - Tower mode (experimental, KIMI_CODE_EXPERIMENTAL_TOWER=1): the agent can no longer enter tower mode on its own — turn it on with /tower on, or with /tower (also in the web UI) to pin the local branch missions merge back into; a missing base branch is created from the current checkout (uncommitted changes committed onto it as a labeled WIP snapshot) and the workspace is initialized or rebased to it immediately, refusing with guidance while missions are open. Tower agents that die (failed, timed out, killed, or lost) are recorded in the tower protocol — TowerStatus marks them in the roster and warns about missions whose owner died, with a resume hint — and the tower's console instructions now require summarizing every worker's deliverables per mission before teardown.

#3454 913a242 Thanks @wbxl2000! - web: Fixed the context usage ring not refreshing after compaction; session usage now updates live from transcript metadata.

#3391 5f0aa7f Thanks @7Sageer! - Default the workspace trust prompt selection to "Trust this folder" instead of "Don't trust".

#3366 9619277 Thanks @kimi-agent-bot! - Use the Unicode ellipsis "…" in user-facing TUI and VS Code webview text.

#3405 630a11d Thanks @kimi-agent-bot! - Download compressed native update artifacts and decompress them while staging.

Original source
Sep 2, 2026
Date parsed from source:
Sep 2, 2026

First seen by Releasebot:
Sep 2, 2026
Kimi Code by Kimi

0.40.1 (2026-09-02)

Kimi Code fixes the condition for showing the kimi-cli migration prompt.
Bug Fixes

Fix the condition for showing the kimi-cli migration prompt.

Original source