You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/configuration/config-files.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,4 +160,4 @@ When configuring the Kimi Code platform using the `/setup` command, search and f
160
160
161
161
If `~/.kimi/config.toml` doesn't exist but `~/.kimi/config.json` exists, Kimi Code CLI will automatically migrate the JSON configuration to TOML format and backup the original file as `config.json.bak`.
162
162
163
-
Configuration files specified via `--config-file` are parsed based on file extension. Configuration content passed via `--config` is first attempted as JSON, then falls back to TOML if that fails.
163
+
`--config-file`specified configuration files are parsed based on file extension. `--config` passed configuration content is first attempted as JSON, then falls back to TOML if that fails.
Copy file name to clipboardExpand all lines: docs/en/configuration/data-locations.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,13 +63,13 @@ Session data is grouped by working directory and stored under `~/.kimi/sessions/
63
63
64
64
### `context.jsonl`
65
65
66
-
Context history file, stores the session's message history in JSONL format. Each line is a message (user input, model response, tool calls, etc.).
66
+
Context history file, stores the session's message history in JSON Lines (JSONL) format. Each line is a message (user input, model response, tool calls, etc.).
67
67
68
68
Kimi Code CLI uses this file to restore session context when using `--continue` or `--session`.
69
69
70
70
### `wire.jsonl`
71
71
72
-
Wire message log file, stores Wire events during the session in JSONL format. Used for session replay and extracting session titles.
72
+
Wire message log file, stores Wire events during the session in JSON Lines (JSONL) format. Used for session replay and extracting session titles.
Copy file name to clipboardExpand all lines: docs/en/customization/wire-mode.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ interface JSONRPCError {
73
73
Legacy clients can skip this request and send `prompt` directly.
74
74
:::
75
75
76
-
-**Direction**: Client → Agent
76
+
-**Direction**: client → agent
77
77
-**Type**: Request (requires response)
78
78
79
79
Optional handshake request for negotiating protocol version, submitting external tool definitions, and retrieving the slash command list.
@@ -233,7 +233,7 @@ If no turn is in progress:
233
233
234
234
### `event`
235
235
236
-
- **Direction**: Agent → Client
236
+
- **Direction**: agent → client
237
237
- **Type**: Notification (no response needed)
238
238
239
239
Events emitted by the agent during a turn. No `id` field, client doesn't need to respond.
@@ -254,7 +254,7 @@ interface EventParams {
254
254
255
255
### `request`
256
256
257
-
-**Direction**: Agent → Client
257
+
-**Direction**: agent → client
258
258
-**Type**: Request (requires response)
259
259
260
260
Requests from the agent to the client, used for approval confirmation or external tool calls. The client must respond before the agent can continue execution.
0 commit comments