Repository navigation
ci: release packages - #4053
ci: release packages#4053github-actions[bot] wants to merge 1 commit into
Conversation
13f4b8e to
6e24730
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6e24730972
ℹ️ 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".
| { | ||
| "name": "@moonshot-ai/kimi-code", | ||
| "version": "2.1.1", | ||
| "version": "2.2.0", |
There was a problem hiding this comment.
This release ships engine changes that the VS Code extension also embeds: its build aliases the SDK source and always bundles @moonshot-ai/*, while KimiRuntime constructs an in-process SDK harness. However, apps/vscode/package.json remains at 0.8.1, so this push takes the vscode-publish.yml unchanged-version path and exits without rebuilding or publishing a VSIX. Existing VS Code users will therefore retain the previous engine and miss this release's engine fixes and behavior changes; increment the extension version (and its changelog) so the marketplace artifacts are published.
Useful? React with 👍 / 👎.
af2e299 to
a7956df
Compare
a7956df to
bd05254
Compare
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
49c4a58 to
ce84923
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce8492352f
ℹ️ 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".
|
|
||
| ### Minor Changes | ||
|
|
||
| - [#4058](https://github.com/MoonshotAI/kimi-code/pull/4058) [`5b93669`](https://github.com/MoonshotAI/kimi-code/commit/5b936697670ed15444bcb4720bd91e6ee776a941) Thanks [@liruifengv](https://github.com/liruifengv)! - Add an `allow_ignored_globs` option to the workspace `fs:list` request: matching entries are listed even when gitignored, ignored ancestor directories of a match stay traversable, and dot-path allowances require `show_hidden: true`. |
There was a problem hiding this comment.
@moonshot-ai/agent-core-v2 is private, so this generated 0.5.0 entry is never published, while apps/kimi-code/src/cli/sub/web/run.ts starts kap-server and the 2.2.0 CLI therefore ships both the new allow_ignored_globs request and the changed matching of existing glob inputs. Because neither item appears in apps/kimi-code/CHANGELOG.md, npm and native kimi web API consumers receive a contract and behavior change with no public release note. Restore and retarget these changesets to @moonshot-ai/kimi-code before regenerating the release.
AGENTS.md reference: AGENTS.md:L85-L86
Useful? React with 👍 / 👎.
ce84923 to
caad315
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: caad315aaf
ℹ️ 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".
|
|
||
| - [#4061](https://github.com/MoonshotAI/kimi-code/pull/4061) [`20a2cea`](https://github.com/MoonshotAI/kimi-code/commit/20a2cea72f5d2c4be3a3845e4ff24ce302a6630e) Thanks [@chengluyu](https://github.com/chengluyu)! - Cap the agent's in-turn wait for background tasks at 90 seconds (longer timeouts are no longer accepted), discourage repeated waits, and let a new message end the wait immediately. | ||
|
|
||
| - [#3998](https://github.com/MoonshotAI/kimi-code/pull/3998) [`09af3b4`](https://github.com/MoonshotAI/kimi-code/commit/09af3b483faac51a767aee50adb1bc1a8de4cc53) Thanks [@tpoisonooo](https://github.com/tpoisonooo)! - Tower mode: a message sent while the agent is running aborts the in-progress turn and runs as its own turn. |
There was a problem hiding this comment.
For Tower users submitting a message during a normal coordinator turn, this note promises that the active turn will be aborted, but towerService.ts:153-161 assigns wakeTurnId only to turns whose origin is the tower_inbox injection, and towerService.ts:180-189 cancels only when that ID exists. All other running turns retain their previous behavior, so narrow the published 2.2.0 entry to inbox-wake turns rather than advertising this for every in-progress Tower turn.
AGENTS.md reference: AGENTS.md:L98-L100
Useful? React with 👍 / 👎.
caad315 to
25b515a
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 25b515a1c1
ℹ️ 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".
|
|
||
| ### Patch Changes | ||
|
|
||
| - [#4081](https://github.com/MoonshotAI/kimi-code/pull/4081) [`06ebfc8`](https://github.com/MoonshotAI/kimi-code/commit/06ebfc821e304bd4ca3f828ae739954166463d65) Thanks [@sailist](https://github.com/sailist)! - Fix shifted turns and lost replies when a UserPromptSubmit hook injects text; hook JSON output without a "message" field is no longer added to the conversation. |
There was a problem hiding this comment.
This release records engine-backed fixes such as the UserPromptSubmit hook correction only for @moonshot-ai/kimi-code, while packages/node-sdk/package.json remains at 0.20.0. Because the public KimiHarness build bundles @moonshot-ai/agent-core-v2, SDK consumers will not receive this fix—or the media-resume, WaitFor, provider, and other bundled engine changes—when only CLI 2.2.0 is published. Add an SDK changeset/version bump and corresponding release notes before consuming these changesets.
AGENTS.md reference: AGENTS.md:L21-L23
Useful? React with 👍 / 👎.
2a740f1 to
09d9a85
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 09d9a8587f
ℹ️ 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".
| { | ||
| "name": "@moonshot-ai/kimi-code-sdk", | ||
| "version": "0.20.0", | ||
| "version": "0.21.0", |
There was a problem hiding this comment.
When the release workflow runs pnpm changeset publish, this version bump will not reach npm because the same manifest still has "private": true; Changesets documents that this setting prevents publication, regardless of publishConfig.access (Changesets configuration). Although an earlier review requested the SDK bump, the fresh evidence is that the bump leaves this publication blocker intact, so npm users remain on 0.20.0 while the repository records 0.21.0 and its new recovery-snapshot API. Remove the private marker or add an explicit SDK publishing path before releasing.
AGENTS.md reference: AGENTS.md:L22-L22
Useful? React with 👍 / 👎.
|
|
||
| - [#4145](https://github.com/MoonshotAI/kimi-code/pull/4145) [`242ac23`](https://github.com/MoonshotAI/kimi-code/commit/242ac230006447f8601e1678c49182bfbae89fe9) Thanks [@wbxl2000](https://github.com/wbxl2000)! - Add `kimi app [path]` to open a new desktop chat in the current or specified directory. | ||
|
|
||
| - [#4061](https://github.com/MoonshotAI/kimi-code/pull/4061) [`20a2cea`](https://github.com/MoonshotAI/kimi-code/commit/20a2cea72f5d2c4be3a3845e4ff24ce302a6630e) Thanks [@chengluyu](https://github.com/chengluyu)! - Cap the agent's in-turn wait for background tasks at 90 seconds (longer timeouts are no longer accepted), discourage repeated waits, and let a new message end the wait immediately. |
There was a problem hiding this comment.
For agents waiting on background work longer than 90 seconds, the previous schema accepted timeouts through the 600-second background-task limit, whereas this release rejects every value above 90. The entry names that lost behavior, but there is no config, environment variable, or flag that preserves the old limit; before publishing this removal, add an escape hatch or record the required explicit maintainer approval.
AGENTS.md reference: AGENTS.md:L102-L104
Useful? React with 👍 / 👎.
d5df6ef to
07e2f92
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 07e2f923ee
ℹ️ 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".
| @@ -1,5 +1,55 @@ | |||
| # @moonshot-ai/kimi-code | |||
|
|
|||
| ## 2.2.0 | |||
There was a problem hiding this comment.
The 2.2.0 release includes parent commit c151d5a, which adds the user-facing KIMI_CODE_LLM_HEADERS_TIMEOUT_MS escape hatch for requests whose response headers take longer than the client's default 300 seconds, but that commit added no changeset and this release section contains no corresponding entry. Consequently, CLI users affected by long non-streaming thinking will receive the feature without the release notes telling them how to avoid those timeouts; add a CLI-targeted changeset/changelog entry before publishing.
AGENTS.md reference: AGENTS.md:L85-L86
Useful? React with 👍 / 👎.
07e2f92 to
89cf0b5
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 89cf0b552a
ℹ️ 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".
| @@ -1,5 +1,55 @@ | |||
| # @moonshot-ai/kimi-code | |||
|
|
|||
| ## 2.2.0 | |||
There was a problem hiding this comment.
The release includes parent commit 7f0ff53, which changes kimi web --remote-control and /remote-control so taking the machine offline from the relay now terminates the local web server, but the 2.2.0 section has no entry for that user-visible fix; the private remote-control package's generated changelog only lists a dependency update. Add a CLI-targeted changeset/changelog entry before publishing so Remote Control users can discover the new shutdown behavior.
AGENTS.md reference: AGENTS.md:L85-L86
Useful? React with 👍 / 👎.
|
|
||
| - [#4031](https://github.com/MoonshotAI/kimi-code/pull/4031) [`33e368a`](https://github.com/MoonshotAI/kimi-code/commit/33e368a1eff8d958856af8e2fb64f4db122b2247) Thanks [@Grapedge](https://github.com/Grapedge)! - Add sticky user message summaries in fullscreen mode; click a summary to jump to the original message. | ||
|
|
||
| - [#4074](https://github.com/MoonshotAI/kimi-code/pull/4074) [`c9f01f0`](https://github.com/MoonshotAI/kimi-code/commit/c9f01f07388abc2cdca40c9c5267f58c65086710) Thanks [@tpoisonooo](https://github.com/tpoisonooo)! - Tower mode: deterministic orchestration with TowerRebase and LLM-free status, goal/tower mutual exclusion, and workspace protection. |
There was a problem hiding this comment.
Tower remains an experimental, default-off feature (towerFlag.default is false), but this new orchestration entry neither labels it experimental nor tells users to enable KIMI_CODE_EXPERIMENTAL_TOWER=1 or [experimental] tower = true before running /tower on. As a result, users discovering these advertised capabilities in 2.2.0 cannot activate them from the release note; add the activation steps required for experimental-feature changesets.
AGENTS.md reference: AGENTS.md:L85-L86
Useful? React with 👍 / 👎.
8e6df6e to
d053091
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d053091a0a
ℹ️ 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".
|
|
||
| ### Patch Changes | ||
|
|
||
| - Updated dependencies [[`e5b4b88`](https://github.com/MoonshotAI/kimi-code/commit/e5b4b88ba93d5a27aa9a36cf847eed4f1aa39c48)]: |
There was a problem hiding this comment.
For VS Code users with UserPromptSubmit hooks, 0.8.2 includes commit 06ebfc8's direct changes to apps/vscode/src/runtime/replay-adapter.ts and apps/vscode/src/utils/hook-parts.ts, which keep injected hook text from shifting transcript messages, but this release section lists only SDK and migration dependency updates. The fresh evidence after the earlier version-bump finding is that the extension is now bumped and will publish, while its changelog still omits its own user-visible fix; add a VS Code-targeted release entry so marketplace users can discover the changed hook behavior.
AGENTS.md reference: AGENTS.md:L85-L86
Useful? React with 👍 / 👎.
|
|
||
| ### Minor Changes | ||
|
|
||
| - [#4159](https://github.com/MoonshotAI/kimi-code/pull/4159) [`0a3a2fb`](https://github.com/MoonshotAI/kimi-code/commit/0a3a2fbafab473df9e9f6609f825af78d2c1ce6d) Thanks [@RealKai42](https://github.com/RealKai42)! - Add an opt-in NotifyUser progress update feature (off by default): new sessions can show the agent's mid-turn progress with an optional one-line title, enabled in the TUI `/experiments` or the web/Desktop settings' Lab section; set `[experimental] notify_user = true` or `KIMI_CODE_EXPERIMENTAL_NOTIFY_USER=1` to turn it on. |
There was a problem hiding this comment.
For kimi web users enabling notify_user, the server now advertises the update_panel capability and exposes NotifyUser, but the committed dist-web tree is byte-identical to the 2.1.1 release bundle, predates 0a3a2fb, and contains no NotifyUser handling. Consequently, the published CLI cannot provide the promised web progress-row display from this entry; sync and commit the code-app bundle before releasing this feature.
AGENTS.md reference: AGENTS.md:L18-L18
Useful? React with 👍 / 👎.
|
|
||
| - [#4074](https://github.com/MoonshotAI/kimi-code/pull/4074) [`c9f01f0`](https://github.com/MoonshotAI/kimi-code/commit/c9f01f07388abc2cdca40c9c5267f58c65086710) Thanks [@tpoisonooo](https://github.com/tpoisonooo)! - Tower mode: deterministic orchestration with TowerRebase and LLM-free status, goal/tower mutual exclusion, and workspace protection. | ||
|
|
||
| - [#4059](https://github.com/MoonshotAI/kimi-code/pull/4059) [`1f6f0b1`](https://github.com/MoonshotAI/kimi-code/commit/1f6f0b1fa2117cc9374c1be62c534b4a4d60e412) Thanks [@7Sageer](https://github.com/7Sageer)! - Add the KIMI_CODE_TRUST_WORKSPACE environment variable to mark the workspace as trusted. |
There was a problem hiding this comment.
When KIMI_CODE_TRUST_WORKSPACE=1 is used with the multi-workspace kimi web server, every WorkspaceTrustService reads the same process-wide bootstrap value, so roots added later through /api/v1/workspaces are also trusted and the /untrust endpoint still reports them as trusted. This entry describes trusting “the workspace,” which can lead users who intended to trust only the startup folder to silently enable project MCP servers and instructions from every subsequently opened folder; either scope the override to the intended root or explicitly disclose that it trusts all workspaces in the process and cannot be revoked until restart.
AGENTS.md reference: AGENTS.md:L118-L120
Useful? React with 👍 / 👎.
d053091 to
b36fd1c
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b36fd1cbda
ℹ️ 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".
|
|
||
| - [#4164](https://github.com/MoonshotAI/kimi-code/pull/4164) [`3395f5b`](https://github.com/MoonshotAI/kimi-code/commit/3395f5bea6c77feb6a835d1ca3f4935970f96c6b) Thanks [@huangzheng2016](https://github.com/huangzheng2016)! - Show a "Shutting down" status hint while shutdown hooks run during exit, and let a Ctrl+C during that window force an immediate exit instead of waiting for the hook timeout. | ||
|
|
||
| - [#4033](https://github.com/MoonshotAI/kimi-code/pull/4033) [`eec9bbd`](https://github.com/MoonshotAI/kimi-code/commit/eec9bbd94958248034f5dbf109a639970308f05e) Thanks [@Grapedge](https://github.com/Grapedge)! - Feedback surveys now appear less often. |
There was a problem hiding this comment.
For TUI users who resume sessions, parent commit e5b4b88 changes SurveyController from counting only post-mount turns to seeding the count from resumeState.agents.main.userTurnCount, so prior turns now contribute to survey eligibility. That user-visible fix was consumed only as an SDK recovery-snapshot entry; this CLI release section's sole survey note covers eec9bbd and only says surveys appear less often. Add a CLI-targeted release entry describing the corrected behavior for resumed sessions.
AGENTS.md reference: AGENTS.md:L84-L85
Useful? React with 👍 / 👎.
|
|
||
| - [#4091](https://github.com/MoonshotAI/kimi-code/pull/4091) [`21406fb`](https://github.com/MoonshotAI/kimi-code/commit/21406fb4c805cc8c715e6d1f16ad3fb5f25f4fe3) Thanks [@sailist](https://github.com/sailist)! - Omit max_tokens for models without an explicit output limit, fixing repeated 400 errors on strict serving stacks (e.g. bare vLLM) when the model's max output size is unknown. | ||
|
|
||
| - [#4184](https://github.com/MoonshotAI/kimi-code/pull/4184) [`cbd7540`](https://github.com/MoonshotAI/kimi-code/commit/cbd754049a114ee36d1b27675c82819e4963c692) Thanks [@7Sageer](https://github.com/7Sageer)! - Remove the never-implemented `executor = "kaos"` option from MCP stdio server configuration; configs using it now fail validation at load time. |
There was a problem hiding this comment.
When an existing user or project .mcp.json contains executor: "kaos" alongside otherwise valid servers, cbd7540's narrowed enum makes loadMcpServers() reject the whole file; WorkspaceMcpConfigService then catches that initialization error and leaves its server map empty, so the valid MCP servers are silently skipped too. In 2.1.1 the file parsed and only the kaos client raised not_implemented, so this 2.2.0 upgrade broadens one unsupported entry into loss of all MCP configuration. Preserve the legacy value long enough to isolate and diagnose that server, or migrate/filter it before publishing.
AGENTS.md reference: AGENTS.md:L117-L119
Useful? React with 👍 / 👎.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@moonshot-ai/kimi-code@2.2.0
Minor Changes
#4159
0a3a2fbThanks @RealKai42! - Add an opt-in NotifyUser progress update feature (off by default): new sessions can show the agent's mid-turn progress with an optional one-line title, enabled in the TUI/experimentsor the web/Desktop settings' Lab section; set[experimental] notify_user = trueorKIMI_CODE_EXPERIMENTAL_NOTIFY_USER=1to turn it on.#4145
242ac23Thanks @wbxl2000! - Addkimi app [path]to open a new desktop chat in the current or specified directory.#4061
20a2ceaThanks @chengluyu! - Cap the agent's in-turn wait for background tasks at 90 seconds (longer timeouts are no longer accepted), discourage repeated waits, and let a new message end the wait immediately.#3998
09af3b4Thanks @tpoisonooo! - Tower mode: a message sent while the agent is running aborts the in-progress turn and runs as its own turn.#4031
33e368aThanks @Grapedge! - Add sticky user message summaries in fullscreen mode; click a summary to jump to the original message.#4074
c9f01f0Thanks @tpoisonooo! - Tower mode: deterministic orchestration with TowerRebase and LLM-free status, goal/tower mutual exclusion, and workspace protection.#4059
1f6f0b1Thanks @7Sageer! - Add the KIMI_CODE_TRUST_WORKSPACE environment variable to mark the workspace as trusted.Patch Changes
#4183
c15638bThanks @RealKai42! - Cancel in-flight video uploads when a media read is interrupted.#4081
06ebfc8Thanks @sailist! - Fix shifted turns and lost replies when a UserPromptSubmit hook injects text; hook JSON output without a "message" field is no longer added to the conversation.#4154
419acedThanks @7Sageer! - Fix media file reading on the first turn after resuming a session.#4083
f409caaThanks @sailist! - Cron tasks from the source session no longer fire inside a forked session.#4152
f0bc988Thanks @7Sageer! - Forked subagents now inherit the parent's available agent types, including custom agents.#4057
a940f2fThanks @huangzheng2016! - Fix the permission mode switch in the goal-start approval prompt not taking effect on the v2 engine.#4081
06ebfc8Thanks @sailist! - Fix messages rendering out of place in sessions with a UserPromptSubmit hook.#4153
7091138Thanks @RealKai42! - Let the agent write one- or two-sentence progress notes between tool calls instead of bare status lines; in the experimental Updates panel (KIMI_CODE_EXPERIMENTAL_NOTIFY_USER=1), stop asking the agent to repost its mid-turn text as an update and remind it to post updates less often.#4054
4fbe065Thanks @RealKai42! - Stop prompting the agent to send NotifyUser updates when a session is opened in a host that does not display them.#4091
21406fbThanks @sailist! - Omit max_tokens for models without an explicit output limit, fixing repeated 400 errors on strict serving stacks (e.g. bare vLLM) when the model's max output size is unknown.#4184
cbd7540Thanks @7Sageer! - Remove the never-implementedexecutor = "kaos"option from MCP stdio server configuration; configs using it now fail validation at load time.#2919
0f052feThanks @duyphan154! - Sanitize foreground Bash tool output so captured terminal escape sequences no longer change the host terminal state.#4164
3395f5bThanks @huangzheng2016! - Show a "Shutting down" status hint while shutdown hooks run during exit, and let a Ctrl+C during that window force an immediate exit instead of waiting for the hook timeout.#4033
eec9bbdThanks @Grapedge! - Feedback surveys now appear less often.#4160
72fc1d0Thanks @kimi-agent-bot! - Show "Working…" in the status spinner while thinking.#4056
395d537Thanks @7Sageer! - Replace inline MCP commands in the workspace trust prompt with activation summaries and configuration paths for manual inspection.#4076
e3bf50cThanks @7Sageer! - Remove interruption reminders from the conversation when their interrupted turns are undone.#4031
33e368aThanks @Grapedge! - Replace the user message bullet ✨ with ❯.@moonshot-ai/agent-core-v2@0.5.0
Minor Changes
5b93669Thanks @liruifengv! - Add anallow_ignored_globsoption to the workspacefs:listrequest: matching entries are listed even when gitignored, ignored ancestor directories of a match stay traversable, and dot-path allowances requireshow_hidden: true.Patch Changes
5b93669Thanks @liruifengv! - Match workspace fs globs (include_globs,exclude_globs,allow_ignored_globs) with the standard picomatch engine:a/**/bno longer matches paths likea/xxb, anda/**now also matchesaitself.@moonshot-ai/kimi-code-sdk@0.21.0
Minor Changes
#4184
cbd7540Thanks @7Sageer! - Remove thekaos/persistenceKaossession options and thecreateSessionWithKaos/resumeSessionWithKaosclient methods, which were already ignored at runtime.#4156
e5b4b88Thanks @Grapedge! - Add cumulative main-agent user-turn counts to session recovery snapshots.@moonshot-ai/pi-tui@0.85.0
Minor Changes
33e368aThanks @Grapedge! - Add fullscreen layout effects that settle render requests before terminal output.kimi-code@0.8.2
Patch Changes
cbd7540,e5b4b88]:@moonshot-ai/acp-server@0.0.2
Patch Changes
5b93669,5b93669]:@moonshot-ai/kap-server@0.2.4
Patch Changes
5b93669,5b93669]:@moonshot-ai/klient@0.1.3
Patch Changes
5b93669,5b93669]:@moonshot-ai/migration-legacy@0.1.17
Patch Changes
5b93669,5b93669]:@moonshot-ai/remote-control@0.0.1
Patch Changes
5b93669,5b93669]: