mirror of
https://github.com/MoonshotAI/kimi-code.git
synced 2026-08-27 17:46:38 +00:00
6595955b31
Some checks are pending
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 / 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 / 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 / Native release artifact (push) Blocked by required conditions
Release / Publish native release assets (push) Blocked by required conditions
Release / Release (push) Waiting to run
Release / Deploy docs (push) Blocked by required conditions
* fix(kap-server): report run_in_background on the task wire The /tasks wire now carries the task's detached flag as run_in_background (schema in both the kap-server local copy and the public protocol package). A running foreground subagent used to be indistinguishable from a background one on this surface — clients that defaulted the missing field to true would treat it as background. * chore: add changeset for the run_in_background wire fix * fix(kap-server): make run_in_background a required wire field The field is always emitted (ghost-restored records pre-dating it read true: the persisted store only lists terminal-and-detached or running tasks, which all carry a concrete flag). Making the contract required means a producer that omits it fails as an ordinary protocol error instead of clients silently re-interpreting the row as foreground * fix(protocol): keep run_in_background optional in the public task schema The public schema types the agent-core v1 task service too, which does not emit the field — making it required there is a breaking protocol change (and broke agent-core's typecheck). kap-server's own local schema stays required: it is the sole writer of the /tasks response and always emits. Consumers apply the foreground fallback when the field is absent |
||
|---|---|---|
| .. | ||
| src | ||
| CHANGELOG.md | ||
| package.json | ||
| tsconfig.json | ||
| tsdown.config.ts | ||
| vitest.config.ts | ||