Moonshot AI’s latest Kimi Code 2.6 canary brings a substantial set of changes for developers, including live progress in fullscreen transcripts and permission rules that persist across sessions. It is a preview build, but several additions affect how people steer and supervise coding agents, not just how the interface looks.
Moonshot AI/Kimi Watch analysis
What happened
The 11 November release notes cover changes to Kimi Code’s terminal interface, agent tools and server. The build keeps fullscreen transcript groups steady while showing live progress, and adds persistent user and project permission rules. It also supports direct skill invocation through the Skill tool and same-name skills in different workspace directories.
Our top picks
- Live progress in fullscreen
Transcript groups stay steady while the agent works, making activity easier to follow. - Persistent permission rules
User and project rules can carry across sessions instead of needing to be set afresh each time. - More flexible skills
Developers can invoke skills through the Skill tool and use same-name skills in separate workspace directories. - Clearer upgrade prompts
Kimi Code can prompt users when a newer minimum version is required. - Fewer platform and workflow snags
The notes include fixes for Windows batch-script commands, clipboard copying in tmux and Linux, and file suggestions that include gitignored files.
Why it matters
These changes touch the practical business of working with an agent: seeing its progress, setting permissions and making skills fit the shape of a project. That is less glamorous than promising a more brilliant agent, but it can make an existing one easier to direct and less fiddly to use.
Our read
This is a canary, not a stable-release recommendation. Still, there is enough here for developers already testing Kimi Code to look beyond the interface polish. Permission persistence and live progress are the most consequential changes; check the release notes before relying on the new behaviour in an important workflow.
What to watch
- Whether these changes make it into a stable release, and when.
- How persistent permission rules behave across user and project settings.
- Whether the fullscreen progress view stays useful during longer agent tasks.
Discussion spark: For coding agents, which deserves priority: clearer live progress, or permissions that persist predictably across sessions?
Sources and evidence
- moonshot-ai/[email protected] (11 November 2026, 05:38 UTC)
not affiliated with or endorsed by Moonshot AI and Kimi