mirror of
https://github.com/MoonshotAI/kimi-code.git
synced 2026-10-23 07:00:12 +00:00
c3bf6f9d2d
Tower mode is now entered only manually — /tower on, or /tower <base-branch> to also pin the local branch missions merge back into. The agent can no longer enter it on its own: TowerInit refuses while the mode is off and points at the slash command. /tower <base-branch> is deterministic end to end: a missing base branch is created from the current checkout (uncommitted changes committed onto it as a labeled WIP snapshot), the checkout switches to it, and the tower workspace is initialized immediately instead of relying on the model to apply the base. With an existing workspace the tower rebases onto the requested base when no missions are open and refuses naming the blocking missions otherwise. The base rides the tower_mode.enter event into the new tower.base state key and TowerInit falls back to it. Tower agent deaths (failed/timed_out/killed/lost) are recorded in the tower protocol: TowerStatus marks dead roster entries and warns about missions whose owner died, with a resume hint. The tower console prompt now requires a per-worker deliverables summary before TowerTeardown. The session profile REST surface accepts tower_base so web clients can turn tower mode on with /tower <base-branch> instead of sending the argument as a prompt. Co-authored-by: konghuanjun <konghuanjun@moonshot.ai> |
||
|---|---|---|
| .. | ||
| src | ||
| CHANGELOG.md | ||
| package.json | ||
| tsconfig.json | ||
| tsdown.config.ts | ||
| vitest.config.ts | ||