Skip to content

docs(changelog): sync 0.41.0 from apps/kimi-code/CHANGELOG.md - #3551

Merged
wbxl2000 merged 1 commit into
mainfrom
docs/changelog-sync-0.41.0
Sep 4, 2026
Merged

docs(changelog): sync 0.41.0 from apps/kimi-code/CHANGELOG.md#3551
wbxl2000 merged 1 commit into
mainfrom
docs/changelog-sync-0.41.0

Conversation

@wbxl2000

@wbxl2000 wbxl2000 commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

Related Issue

N/A — post-release docs maintenance

Problem

The docs-site changelog has not yet been synced for 0.41.0 after the npm release.

What changed

  • Synced 0.41.0 from apps/kimi-code/CHANGELOG.md into docs/en/release-notes/changelog.md
  • Translated the new English increment into docs/zh/release-notes/changelog.md
  • Verified with pnpm --filter kimi-code-docs run build (vitepress build passes)

Checklist

  • I have read the CONTRIBUTING document.
  • I have linked a related issue, or explained the problem above.
  • I have added tests that prove my feature works. (N/A — docs-only sync)
  • Ran gen-changesets skill, or this PR needs no changeset. (No changeset — docs sync is out of bundle)
  • Ran gen-docs skill, or this PR needs no doc update. (This PR is the dedicated changelog sync)

@changeset-bot

changeset-bot Bot commented Sep 4, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: cbc8bea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@wbxl2000
wbxl2000 merged commit 2fbb271 into main Sep 4, 2026
14 of 15 checks passed
@wbxl2000
wbxl2000 deleted the docs/changelog-sync-0.41.0 branch September 4, 2026 13:15

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cbc8bea1e4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".


- Fix print mode (`kimi -p`) losing session records when the run exits on an error or a termination signal.
- Fix print mode (`kimi -p`) ignoring the `KIMI_DISABLE_TELEMETRY` environment variable.
- Tower mode (experimental): fix tower mode never starting when enabled through `[experimental] tower = true` in config.toml instead of the environment variable, and make `/tower` work in directories that are not git repositories; enablement errors now name the actual blocker.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Warn that /tower commits every existing file

When a user runs /tower in a populated non-Git directory, the 0.41 implementation runs git init and commits every present file; the upstream release entry at apps/kimi-code/CHANGELOG.md:67 explicitly documents this behavior. Saying only that /tower now works there leaves users liable to commit .env credentials, large binaries, or generated files without warning, so preserve the initialization and snapshot caveat in both locales.

AGENTS.md reference: docs/AGENTS.md:L18-L21

Useful? React with 👍 / 👎.

- Fix resuming a subagent by its agent id after the session is reopened in a new process; the resumed subagent follows the current permission mode and is matched by its own profile in permission rules.
- web: Fix per-turn file change previews showing added/removed lines that never existed and inaccurate line counts when the same file is edited multiple times in one turn; change cards now show only exact line statistics.
- web: Fix the default thinking effort in settings not being settable to the highest level (Max).
- Fix several known issues and make various refinements. See the [changelog on GitHub](https://github.com/MoonshotAI/kimi-code/blob/main/apps/kimi-code/CHANGELOG.md) for more technical entries.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the unconditional file-history change

For users who left turn-level file history at its default-off state or explicitly disabled KIMI_CODE_EXPERIMENTAL_FILE_HISTORY, 0.41 starts recording file snapshots unconditionally and removes that flag, as stated in apps/kimi-code/CHANGELOG.md:9. Folding this behavior into the catch-all gives no notice that upgrades begin persisting copies of edited files and that the opt-out no longer works; retain an explicit entry and its Chinese translation.

AGENTS.md reference: docs/AGENTS.md:L18-L21

Useful? React with 👍 / 👎.

- 修复 `kimi -p` 忽略 `KIMI_DISABLE_TELEMETRY` 环境变量的问题。
- 修复 tower 模式(实验)在 config.toml 中通过 `[experimental] tower = true` 启用时不生效的问题;`/tower` 现可在非 git 仓库目录使用;启用失败时报错会指明具体原因。
- 修复后台提问在 Agent 回合结束即被取消的问题。
- 修复会话在新进程重开后无法按 agent id 恢复子 Agent 的问题;恢复的子 Agent 遵循当前权限模式。

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Translate the resumed-agent permission-rule behavior

For Chinese users who resume a subagent after reopening a session and rely on profile-scoped permission rules, this translation omits the English entry's statement that the resumed subagent is matched by its own profile. That behavior is a separate part of the fix and affects which permission rules apply, so translate it rather than reducing the entry to only inheriting the current permission mode.

AGENTS.md reference: docs/AGENTS.md:L18-L21

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants