From 5d748752cf481487961b0d8fc24d536b35e1e385 Mon Sep 17 00:00:00 2001 From: qer Date: Tue, 7 Jul 2026 14:57:22 +0800 Subject: [PATCH] chore: correct wire-request-trace changeset PR #1448 records a per-request trace in wire.jsonl for debugging, with no user-facing behavior change. Downgrade the CLI bump from minor to patch, drop the unpublished private internal packages (agent-core, kosong), and trim the entry to a single honest sentence. --- .changeset/wire-request-trace.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/.changeset/wire-request-trace.md b/.changeset/wire-request-trace.md index 12e5d8bdb9..dba42f11f3 100644 --- a/.changeset/wire-request-trace.md +++ b/.changeset/wire-request-trace.md @@ -1,7 +1,5 @@ --- -"@moonshot-ai/agent-core": minor -"@moonshot-ai/kimi-code": minor -"@moonshot-ai/kosong": minor +"@moonshot-ai/kimi-code": patch --- -Record a request trace in each agent's `wire.jsonl`: content-addressed snapshots of the tool schemas sent to the model, one record per model request (including retries, strict resends, and compaction rounds) with the effective request parameters, and the raw MCP tool listing per server, so sessions carry enough data to reconstruct every model request for debugging. Chat providers now expose the effective completion-token cap they send on the wire, so the trace records the provider-clamped value rather than the requested budget. +Record a per-request trace in the session wire log, so model requests can be reconstructed for debugging. Not a user-facing feature.