mirror of
https://github.com/MoonshotAI/kimi-code.git
synced 2026-10-26 00:20:20 +00:00
523d35b54b
Some checks are pending
CI / test (4) (push) Waiting to run
CI / test (5) (push) Waiting to run
CI / test-pi-tui (push) Waiting to run
CI / test-vscode-legacy (push) Waiting to run
CI / test-windows (push) Waiting to run
CI / lint (push) Waiting to run
CI / build (push) Waiting to run
CI / test (1) (push) Waiting to run
CI / test (2) (push) Waiting to run
CI / test (3) (push) Waiting to run
CI / typecheck (push) Waiting to run
Nix Build / Check flake.nix workspace sync (push) Waiting to run
Nix Build / nix build .#kimi-code (push) Blocked by required conditions
Release / Release (push) Waiting to run
Release / Deploy docs (push) Blocked by required conditions
Release / Native release artifact (push) Blocked by required conditions
Release / Publish native release assets (push) Blocked by required conditions
Publish VS Code extension / Publish VSIX to marketplaces (push) Waiting to run
* fix(agent-core-v2): keep background questions open past turn end and inline their answers Background AskUserQuestion reused the generic task pipeline end to end, which broke it in two ways: the pending interaction was still bound to the asking turn, so it was cancelled the moment the agent finished its turn, and the turn-end cancel response was then misread as an answer. On top of that the completion notification only carried a pointer to the task output file, forcing an extra Read round trip for a few bytes of JSON. - Detach background question interactions from the asking turn so they stay pending until answered, stopped, or the agent closes. - Treat cancelled interaction responses as dismissals. - Inline the answer JSON in the question task notification and word the notification as answered or dismissed; fall back to the output file only when the answer exceeds the inline budget. - Trim the background launch result to task id, status, and one next step. - Fold transcript notification summaries before inline answer blocks. * fix(agent-core-v2): fail background questions on tool errors and translate interaction cancellations in the question service Follow-up hardening from review: - The interaction kernel's cancellation response now has a named shape, InteractionCancellation, and SessionQuestionService.request translates it into a dismissal (null) before handing the result to callers. The AskUserQuestion tool no longer inspects answer maps for a cancelled key, so a bare answer map can never be mistaken for a cancellation. - QuestionBackgroundTask settles as failed with the tool's message as the stop reason when the question tool reports an error, instead of writing the error text as completed output. The generic task notification then carries the reason, and the answered/dismissed wording is not used. - The question notification only says answered or dismissed when the task output parses as an answers payload; any other output keeps the generic completed wording. |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| CHANGELOG.md | ||
| package.json | ||
| tsconfig.json | ||
| tsdown.config.ts | ||
| vitest.config.ts | ||