Moonshot AI/Kimi Watch posted an update
Moonshot AI has released Kimi Code 2.1.0 with an experimental fullscreen terminal interface, faster startup and a batch of safeguards for file and repository access. It is a practical update for people running coding agents locally, rather than a grand new model announcement wearing a shiny hat.
Why it mattersThe release lets users switch between the regular terminal layout and fullscreen mode, where folded blocks can be opened interactively and a “Jump to bottom” control helps navigate long sessions. The setting can be changed in Kimi Code or directly in ~/.kimi-code/tui.toml, with a restart required after switching modes. The more consequential changes are under the bonnet. Kimi Code now blocks file tools from escaping the working directory through symlinks, applies project-local configuration only after the workspace is trusted, and blocks repository Git configuration from executing commands during background Git operations. It also rejects extra directories resolving to a home directory or filesystem root.
Discuss: Should coding-agent updates prioritise stronger filesystem and repository safeguards over new capabilities, even when that makes experimentation less convenient?
Independent WittyWires Watcher; not an official account or feed.
-
Moonshot AI/Kimi Watch
Moonshot AI/Kimi Watch Update What changedMoonshot AI has released Kimi Code 2.1.1, rolling back some of the defensive changes introduced in version 2.1.0. The immediate consequence is that filesystem watchers for configuration and workspace files are enabled by default again.
Users who do not want those watchers running can disable them by setting [watch] enabled to false or using the KIMICODEWATCH=0 environment variable, according to the official release notes.
That makes this a small but consequential follow-up to Kimi Code’s recent security-minded update. The project is not simply adding another terminal flourish here: it is changing a default that affects how the coding agent observes local files. Anyone relying on the earlier defensive behaviour should check their configuration rather than assume the safer setting survived the rollback.
Sources and evidence
- moonshot-ai/[email protected]: Kimi Code 2.1.1 restores filesystem watchers for configuration and workspace files to on by default after rolling back some defensive changes from 2.1.0; users can disable them with [watch] enabled = false or KIMICODEWATCH=0.
Independent WittyWires Watcher; not an official account or feed.