mirror of
https://github.com/MoonshotAI/kimi-code.git
synced 2026-08-11 01:37:31 +00:00
47cd55b731
Single-instance reliability: - Journal: preserve content on write failure with sticky JournalStorageError, per-batch fsync, last-header open, and zero-write cold reads - Broadcaster: writeFailure gate, deterministic dispose drain, replay failure now triggers resync_required; graceful close ordering in start.ts - fswatch: per-connection monotonic seq, pinned truncated semantics, and gitignore double-cache invalidation; __global__ session made volatile Cross-process lock unification: - agent-core-v2 CrossProcessLockService: parameterized lock modes (heartbeat-TTL implemented), token-guarded release/update, rename-isolated stale takeover, creation window, PID-reuse detection (conservative on macOS) - config.toml and workspace registry locked read-modify-write; mcp.json watch - kap-server lock protocol aligned (lock_id, process_started_at, three-layer stale detection); minidb release ownership fixed, legacy cleanup removed Multi-instance session ownership (gated by multi_server flag): - Session leases with write fencing; 40921 SESSION_HELD_BY_PEER with typed details (routable/creating/holder-unresponsive/held-by-local-instance) and unregistered-writer detection; write-authority registry hard gate in AppendLogStore, session metadata, and flush paths - kimi-web redirect to the holder with pending approvals/questions replay; klient transparent redirect with loop guard - session.list_changed cross-instance discovery via two-layer fs watch; ownership field on GET /sessions Stale-write fencing and skill hot reload: - Session file ledger + agent file fencing: hard gate with the flag on, advisory note with it off; dirty-tick signals from fs watch - Skill root watcher hot reload: catalog reload, turn-boundary listing reminder, and skill_catalog.changed volatile event to web clients |
||
|---|---|---|
| .. | ||
| kimi-code | ||
| kimi-inspect | ||
| kimi-web | ||
| vis | ||
| vscode | ||