agent-dump 1.2.4__tar.gz → 1.2.5__tar.gz

{agent_dump-1.2.4 → agent_dump-1.2.5}/Cargo.lock

@@ -10,7 +10,7 @@ checksum = "320119579fcad9c21884f5c4861d16174d0e06250625266f50fe6898340abefa"
 
 [[package]]
 name = "agent-dump"
-version = "1.2.4"
+version = "1.2.5"
 dependencies = [
  "agent-dump-core",
  "caseless",
@@ -38,6 +38,7 @@ dependencies = [
  "num-bigint",
  "regex",
  "rusqlite",
+ "ruzstd",
  "serde",
  "serde_json",
  "sha2",
@@ -1412,6 +1413,12 @@ version = "1.0.23"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "cf54715a573b99ac80df0bc206da022bcd442c974952c7b9720069370852e21f"
 
+[[package]]
+name = "ruzstd"
+version = "0.9.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a252f5e20f038fe7b4ea53e073e65398d652c864cc162fc77c56c2f13717b888"
+
 [[package]]
 name = "ryu"
 version = "1.0.23"

{agent_dump-1.2.4 → agent_dump-1.2.5}/Cargo.toml

@@ -46,7 +46,7 @@ nix = { version = "0.31", default-features = false, features = ["fs", "user"] }
 
 [package]
 name = "agent-dump"
-version = "1.2.4"
+version = "1.2.5"
 edition = "2024"
 rust-version = "1.90"
 publish = false

{agent_dump-1.2.4 → agent_dump-1.2.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-dump
-Version: 1.2.4
+Version: 1.2.5
 Classifier: Environment :: Console
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Rust
@@ -71,13 +71,22 @@ Follow the generated read commands and cursors until `has_more=false` to cover t
 - **OpenCode** - Open source AI coding assistant
 - **ZCode** - ZCode coding assistant sessions
 - **Claude Code** - Anthropic's AI coding tool
+- **Qoder** - Qoder CLI sessions
+- **Qoder CN** - Qoder CN CLI sessions
 - **Codex** - OpenAI's command-line AI coding assistant
 - **Kimi** - Moonshot AI assistant
+- **Kimi-Code** - Kimi Code CLI sessions
 - **Cursor** - Cursor composer sessions
+- **Droid** - Factory Droid CLI sessions
+- **Grok** - Grok CLI sessions
 - **Pi** - Earendil's AI coding agent
+- **oh-my-pi** - Pi-based coding agent (`omp`)
+- **Gemini CLI** - Google's command-line AI coding agent
+- **DSH** - DeepSeek Harness sessions
 - **DeepChat** - Current local sessions from unencrypted databases
 - **Cherry Studio** - Local 2.x chats and agent sessions
 - **MiniMax Code** - Current CLI sessions from local SQLite storage
+- **Antigravity CLI** - Conversation databases; tool results are not decoded
 - **More Tools** - PRs are welcome to support other AI coding tools
 
 ## Features
@@ -88,7 +97,7 @@ Follow the generated read commands and cursors until `has_more=false` to cover t
 - **Summarize conversations**: Collect all eligible user/assistant text through bounded chunks, or hand the task to an external Agent. Failures are marked as incomplete.
 - **Automate**: Query metadata, capabilities, search evidence, and statistics as JSON; unknown facts remain explicit.
 
-Available formats and message details depend on the source tool. Normalized output does not reproduce every private field or attachment file. Run `agent-dump --providers --json` to inspect capabilities.
+Available formats and message details depend on the source tool. Normalized output does not reproduce every private field or attachment file. Except for MiniMax Code, transcripts drop `system-reminder` and slash-command wrapper tags (`command-*`, `local-command-*`), trim trailing whitespace, and omit messages left empty by that cleanup. Run `agent-dump --providers --json` to inspect capabilities.
 
 ## Installation
 
@@ -196,12 +205,21 @@ Supported URI schemes:
 - `codex://<session_id>` - Codex sessions
 - `codex://threads/<session_id>` - Codex sessions
 - `kimi://<session_id>` - Kimi sessions
+- `kimi-code://<session_id>` - Kimi-Code sessions
 - `claude://<session_id>` - Claude Code sessions
-- `cursor://<requestid>` - Cursor sessions (`requestid` is used as URI identifier)
+- `qoder://<session_id>` - Qoder sessions
+- `qoder-cn://<session_id>` - Qoder CN sessions
+- `cursor://<composer_id>` - Cursor sessions (legacy `cursor://<requestid>` URIs still resolve to the same session)
+- `droid://<session_id>` - Droid sessions
+- `grok://<session_id>` - Grok sessions
 - `pi://<session_id>` - Pi sessions
+- `omp://<session_id>` - oh-my-pi sessions
+- `gemini-cli://<session_id>` - Gemini CLI sessions
+- `dsh://<session_id>` - DSH sessions
 - `deepchat://<session_id>` - DeepChat sessions
 - `cherry://topic-<id>` / `cherry://session-<id>` - Cherry Studio chats / agent sessions
 - `minimax://<session_id>` - MiniMax Code CLI sessions
+- `antigravity-cli://<conversation_id>` - Antigravity CLI conversations
 
 ### Typical Errors
 
@@ -256,37 +274,62 @@ listed and fails when there is nothing to list because no provider has data.
 
 ## Path Discovery
 
-`agent-dump` resolves most session roots in this order: official environment variable, tool default directory, then local development fallback under `data/<agent>`. ZCode currently uses only its macOS/Windows default database path.
+`agent-dump` resolves most session roots in this order: official environment variable, tool default directory, then local development fallback under `data/<agent>`. ZCode currently uses only its macOS/Windows default database path. Path environment variables are trimmed, blank values are ignored, and a leading `~` expands to the home directory.
 
 - **Codex**: `CODEX_HOME` -> `~/.codex` -> `data/codex`
 - **Claude Code**: `CLAUDE_CONFIG_DIR` -> `~/.claude` -> `data/claudecode`
+- **Qoder**: `QODER_CONFIG_DIR` -> `~/.qoder` -> `data/qoder`
+- **Qoder CN**: `QODERCN_CONFIG_DIR` -> `~/.qoder-cn` -> `data/qoder-cn`
 - **Kimi**: `KIMI_SHARE_DIR` -> `~/.kimi` -> `data/kimi`
+- **Kimi-Code**: `KIMI_CODE_HOME` -> `~/.kimi-code` -> `data/kimi-code`. A session is a `sessions/<hash>/<id>/` directory with both `state.json` and `agents/main/wire.jsonl`; sessions without messages are skipped. The working directory comes from `workDir` or `custom.cwd` in `state.json`, then `session_index.jsonl` in the data root.
 - **OpenCode**: `OPENCODE_DB` selects one database (relative to `XDG_DATA_HOME/opencode` or `~/.local/share/opencode`). Otherwise use `opencode.db` there, then the legacy Windows `LOCALAPPDATA`/`APPDATA` location, then `data/opencode/opencode.db`.
+- **Droid**: `FACTORY_HOME_OVERRIDE/.factory` -> `~/.factory` -> `data/droid`. A session is a `<id>.jsonl` file in `sessions/` or one folder below it whose first line is a `session_start` record; sessions without visible messages are skipped, and so are messages marked `llm_only`. The working directory comes from `lastCwd` or `cwd` in `session_start`. Token usage and the model come from the sibling `<id>.settings.json`; custom model ids map through `customModels` in the data root `settings.json`.
 - **ZCode**: macOS `~/.zcode/cli/db/db.sqlite`; Windows `%USERPROFILE%\.zcode\cli\db\db.sqlite`; no Linux default path
-- **Cursor**: Cursor's default user `globalStorage/state.vscdb`
-- **Pi**: `PI_HOME` -> `~/.pi` -> `data/pi`
+- **Cursor**: `CURSOR_DATA_PATH/globalStorage/state.vscdb`; defaults to the `User` directory under macOS `~/Library/Application Support/Cursor`, Windows `%APPDATA%\Cursor`, or Linux `${XDG_CONFIG_HOME:-~/.config}/Cursor`. The working directory comes from the workspace folder in `workspaceStorage/*/workspace.json` that lists the composer.
+- **Grok**: `GROK_HOME` -> `~/.grok` -> `data/grok`. Every `summary.json` under `sessions/`, at any depth, is a session when its `info` has both `id` and `cwd`; messages come from the sibling `updates.jsonl`, and sessions without messages are skipped. Prompts discarded by a rewind are left out of the transcript. See the [Grok reading rules](docs/providers/grok.md).
+- **Pi**: `PI_CODING_AGENT_SESSION_DIR` -> absolute `sessionDir` in the agent directory's `settings.json` -> `<agent directory>/sessions` -> `data/pi`. The agent directory is `PI_CODING_AGENT_DIR`, then `PI_HOME/agent`, then `~/.pi/agent`.
+- **oh-my-pi**: `XDG_DATA_HOME/omp/sessions` when `XDG_DATA_HOME/omp` exists (not on Windows) -> `~/.omp/agent/sessions` -> `data/omp`
+- **Gemini CLI**: `GEMINI_CLI_HOME/.gemini/tmp` -> `~/.gemini/tmp` -> `data/gemini-cli`. `GEMINI_CLI_HOME` is the directory that contains `.gemini`, not the data directory itself.
+- **DSH**: `DSH_HOME` -> `~/.dsh` -> `data/dsh`. Sessions are logs under `sessions/<project>/<session>/`; attachments are read from `attachments/v1` in the data root.
 - **DeepChat**: `DEEPCHAT_USER_DATA_DIR/app_db/agent.db`; defaults to macOS `~/Library/Application Support/DeepChat/app_db/agent.db`, Windows `%APPDATA%\DeepChat\app_db\agent.db`, or Linux `${XDG_CONFIG_HOME:-~/.config}/DeepChat/app_db/agent.db`.
-- **Cherry Studio**: `CHERRY_STUDIO_USER_DATA_DIR/Data/cherrystudio.sqlite`; otherwise the first existing database in the user data directories configured by `~/.cherrystudio/boot-config.json`, then the platform default: macOS `~/Library/Application Support/CherryStudio`, Windows `%APPDATA%\CherryStudio`, or Linux `${XDG_CONFIG_HOME:-~/.config}/CherryStudio` (each with `Data/cherrystudio.sqlite`). The override is provided by agent-dump; use it for portable/dev installations or to select among multiple installations.
-- **MiniMax Code**: `MINIMAX_DATA_DIR` → `MAVIS_DATA_DIR` → `~/.minimax`; the database is `v2/sqlite/runtime-state.sqlite` under the selected root. Only one root is selected; a missing explicit path never falls back to another installation.
+- **Cherry Studio**: `CHERRYSTUDIO_USER_DATA_DIR` or `CHERRY_STUDIO_USER_DATA_DIR`, then `Data/cherrystudio.sqlite`; otherwise the first existing database in the user data directories configured by `~/.cherrystudio/boot-config.json`, then the platform default: macOS `~/Library/Application Support/CherryStudio`, Windows `%APPDATA%\CherryStudio`, or Linux `${XDG_CONFIG_HOME:-~/.config}/CherryStudio` (each with `Data/cherrystudio.sqlite`). Use the override for portable/dev installations or to select among multiple installations.
+- **MiniMax Code**: `MINIMAX_DATA_DIR` → `MAVIS_DATA_DIR` → `~/.minimax`, or `~/.minimax-code` when only that directory has a database; the database is `v2/sqlite/runtime-state.sqlite` under the selected root. Only one root is selected; a missing explicit path never falls back to another installation.
+- **Antigravity CLI**: `AGY_CONVERSATIONS_DIR` -> `~/.gemini/antigravity-cli/conversations` -> `data/antigravity-cli/conversations`. Each `<conversation_id>.db` below it is a session; the optional `conversation_summaries.db` in its parent directory supplies the title, working directory, and update time. Antigravity IDE `.gemini/antigravity/conversations/*.pb` files are not read.
 
 Notes:
 
 - On Windows, prefer configuring the tool's official environment variable when available.
 - The `data/<agent>` fallback is kept for local development and tests.
 
-DeepChat reads saved sessions in the current `agent.db`, including migrated history, ACP sessions, and subagent sessions; drafts are excluded. It supports listing, query, search, stats, collect, and print / JSON / Markdown exports. Structured messages take precedence over the `content` fallback. Text, reasoning, and tool records are normalized; compaction markers do not enter collect. JSON also retains attachment references, links, and other message blocks. Attachment files and offloaded tool output are not read. Token totals come from message records; billing cost is unavailable.
+Codex scans `sessions` and `archived_sessions` and reads only `rollout-*.jsonl` and `rollout-*.jsonl.zst`; when both exist, the uncompressed file wins. Raw export of a compressed rollout writes the decompressed JSONL. Titles come from the title index, then the first line of the first user message in the first 20 records that is not injected context. Developer and system messages, and user messages that contain injected-context markers, are excluded. Token totals add each `token_count` delta once, include remote compaction and subagent usage, exclude history a fork replays from its parent, and record cache reads. Subagent rollouts are listed as separate sessions; when the parent never received a completion notification, the subagent's final reply is inserted into the parent. For uncompressed files over 256 KiB, listing reads only the head and tail, so the message count is unknown.
+
+Claude Code lists `<project>/<session>.jsonl` files and the subagent transcripts under `<session>/subagents/`, including workflow agents in `subagents/workflows/<run>/agent-*.jsonl`. Each subagent is a separate session identified by its agent ID, and the parent message that starts it records `subagent_id`. Sessions without a visible message are skipped. Titles use the latest custom title, then the AI title, the subagent name or description, `sessions-index.json`, and the first line of the first user prompt within the first 20 records. Message counts include visible records only. Token totals keep the last usage of each API request and count cache reads and writes as input.
+
+Qoder and Qoder CN keep the Claude Code project layout under `projects/` and follow the same rules; assistant messages are labeled `qoder` or `qoder-cn`.
+
+Pi reads only the active branch: it follows `parentId` back from the last entry that has an id, so abandoned branches are excluded from exports, search, and counts. Legacy files without entry ids are read in file order. Tool results are merged into their tool calls with status and `details`; bash executions get a status from the exit code and cancellation flag. Only custom messages with `display: true` are kept. Tokens are recorded per message, and input includes cache reads and writes. Sessions without visible messages are not listed. Titles come from the `session_info` name, then a `title` record, the header `title`, and the first user message. For files over 256 KiB, listing reads only the head and tail, so the message count is unknown.
+
+oh-my-pi follows the Pi rules; assistant messages are labeled `omp`. Subagent and advisor transcripts in the directory named after a session file are listed as separate sessions, identified by their header `id`, without a link to the parent session.
+
+Gemini CLI lists `tmp/<project>/chats/*.jsonl` and legacy `*.json` chats, plus subagent chats in `chats/<parent session id>/`. A legacy `.json` chat that was resumed as `.jsonl` is read only from the `.jsonl` file. Files without a `sessionId` and sessions without messages are skipped. JSONL records are replayed in order, including `$set`, `$patch`, and `$rewindTo` updates. The working directory comes from `tmp/<project>/.project_root`. Titles use the chat `summary`, then the first user prompt that does not start with `<session_context>` or `<hook_context>`. User text prefers `displayContent`. Thought summaries become reasoning, and tool calls take results from the call record or a later `functionResponse`. Input tokens include cached and tool-use prompt tokens; output totals include thinking tokens. Subagent chats are listed as separate sessions without a link to the parent.
+
+DSH reads one log per session directory: the newest `session.jsonl`, `session.v<N>.jsonl` or `.jsonl.zstd` file by format version, then modification time. A log counts only in the directories DSH derives from its own working directory and session ID. Logs with an invalid header or non-contiguous sequence numbers and sessions without messages are skipped. A record or zstd frame still being written at the end is ignored, and raw export of a compressed log writes the decompressed JSONL. A forked session excludes the events it inherited from its parent. A streamed step without a final message is rebuilt from its chunks. Tool results are merged into their tool calls with status and metadata. Images are read only when the attachment matches its recorded SHA-256 digest and size; a message whose images are all unavailable shows `Image attachment unavailable`. Titles come from the session title, then the subagent label, the first user message, an inherited title and the working directory name. Input tokens include cache reads and writes, and output tokens include reasoning. Billing cost is never estimated.
+
+DeepChat reads saved sessions in the current `agent.db`, including migrated history, ACP sessions, and subagent sessions; drafts, sessions without messages, and sessions whose parent chain forms a loop are excluded. The update time is the latest of the session, message, block, and usage records. It supports listing, query, search, stats, collect, and print / JSON / Markdown exports. Structured messages take precedence over the `content` fallback, and plain-text `content` becomes message text. Text, reasoning, plan, image, and tool records are normalized; other blocks with text become message text, and compaction markers do not enter collect. Referenced sessions, attachment paths, and links become message text, so search finds them; JSON also keeps the attachment and link records. Attachment files and offloaded tool output are not read. Token totals come from `deepchat_usage_stats`, falling back to message metadata, with cached tokens capped at the input count; billing cost is unavailable.
 
 SQLCipher databases, direct reads of legacy `chat.db`, and raw export are unsupported. The reader does not run DeepChat migrations or Tape recovery. Set `DEEPCHAT_USER_DATA_DIR` to read a custom user data directory.
 
-Cherry Studio supports listing, query, search, stats, collect, and print / JSON / Markdown exports from its current 2.x database, including migrated history. Ordinary chats expose only the active root-to-leaf path; other branches and parallel model replies are excluded from exports, search, and counts. Structural roots and empty reserved user leaves are excluded. Agent sessions are read chronologically and use their workspace as the working directory; ordinary chats have no working directory. Deleted sessions and chat messages are excluded.
+Cherry Studio supports listing, query, search, stats, collect, and print / JSON / Markdown exports from its current 2.x database, including migrated history. Ordinary chats expose only the active root-to-leaf path; other branches and parallel model replies are excluded from exports, search, and counts. Structural roots, records that are neither user nor assistant messages, and messages with neither content nor usage are excluded; sessions left without messages are not listed. Agent sessions are read chronologically and use their workspace as the working directory; ordinary chats have no working directory. Deleted sessions and messages are excluded. File parts become images or `Attachment:` text, and compact summaries become message text. Missing token totals are summed from their details, reasoning tokens are recorded, and recorded USD costs count toward the cost. An unnamed session takes its title from the first user message, then `Cherry Studio`; the update time is the session's last activity.
 
 Text, reasoning, tool calls/results, code, and translations are normalized. JSON retains file references and control events; compaction summaries and internal events do not enter collect or search. Token totals come from message stats. Per-currency costs are preserved in JSON without conversion or an aggregate billing total. The reader never opens attachment files, scans SDK logs, or runs application migrations. Direct reads of 1.x IndexedDB/Redux data and raw export are unsupported.
 
-MiniMax Code supports listing, query, search, stats, collect, and print / JSON / Markdown exports from the current CLI's migrated display messages. Visible conversations, child tasks, and archived sessions are included; hidden and internal peek/channel/cron sessions are excluded. Messages follow database row order and preserve text, reasoning, tool state/results, and attachment references. Compaction, review, and system events do not enter collect or search. The model comes from session metadata and remains unknown when absent; JSON retains recorded per-message token usage without estimating billing cost.
+MiniMax Code supports listing, query, search, stats, collect, and print / JSON / Markdown exports from the current CLI's migrated display messages. Sessions without message rows, hidden root sessions, and internal peek/channel/cron sessions are excluded; hidden child sessions and archived sessions are kept. Untitled sessions use the first non-automated user message, and the update time includes message and token-usage times. Messages follow database row order and preserve text, reasoning, tool state/results, and attachment references; attachments and message errors also become text. Compaction and review events keep their user/assistant role with a label such as `Context compacted`, so they enter search and collect; system events and permission responses do not. A tool fails when its result reports `isError` or `error`, and a task tool's single child session becomes `subagent_id`. The session model comes from session metadata and remains unknown when absent. Token usage comes from `local_runtime_token_usage`: session stats count every row, and a turn with one model attaches its model, tokens (including reasoning), and recorded USD cost to the turn's last assistant message. Billing cost is never estimated.
+
+Set `MINIMAX_DATA_DIR` explicitly for custom profiles or other directories. The reader does not read model-context JSONL or attachment files, run migrations, or recover rewound messages. Raw export, direct legacy storage reads, and desktop data are unsupported. Pending migrations and corrupt sessions produce diagnostics instead of appearing empty. See the [MiniMax Code design and acceptance scope](docs/providers/minimax.md).
 
-Set `MINIMAX_DATA_DIR` explicitly for custom profiles, earlier source builds using `~/.minimax-code`, or other directories. The reader does not read model-context JSONL or attachment files, run migrations, or recover rewound messages. Raw export, direct legacy storage reads, and desktop data are unsupported. Pending migrations and corrupt sessions produce diagnostics instead of appearing empty. See the [MiniMax Code design and acceptance scope](docs/providers/minimax.md).
+Antigravity CLI supports listing, query, search, stats, collect, and print / JSON / Markdown exports. Databases are opened read-only, and only the Protobuf fields for user prompts, assistant text, title updates, tool calls, step times, and token usage are decoded. Tool results are not stored in a known format, so tool calls have status `unknown` and keep the native step type and status in metadata; other unrecognized steps are skipped. Databases without steps are not listed. Titles come from the latest title step, the summary title, then the first user prompt. Steps without a native time use the summary update time or the database modification time and are marked as inferred, so collect does not date them. Usage repeated across retries is counted once and attached to the next assistant message; usage after the last step becomes a usage-only assistant message. Input includes cache tokens and session output includes reasoning; cost is not estimated. Raw export is unsupported. A malformed step or unsupported table fails only that session. See the [Antigravity CLI reading rules](docs/providers/antigravity-cli.md).
 
-OpenCode supports legacy SQLite and 2.x `session_v2/session_message`. When both schemas coexist, V2 wins for the same session ID; legacy-only sessions remain readable. V2 messages follow `seq` order, and counts include system and status records. Synthetic input, system/skill messages, compaction and shell records are excluded from collect. `OPENCODE_DB` selects a custom or channel database; a missing explicit path never falls back, and `:memory:` is unavailable. Attachments stay in JSON metadata without fetching referenced files. Running and archived records remain readable; pending inbox items are excluded. Raw export remains normalized `.raw.json`, not an OpenCode import file. See the [design and acceptance scope](docs/providers/opencode-v2.md).
+OpenCode supports legacy SQLite and 2.x `session_v2/session_message`. When both schemas coexist, V2 wins for the same session ID. Until `migration.v1-v2` is completed, legacy sessions that OpenCode has not copied yet stay listed; after that only V2 is read, so sessions deleted in V2 do not come back. Sessions without visible messages are not listed, and message counts include only visible messages. An empty title falls back to the first user text, then `Untitled Session`. V2 messages follow `seq` order. Image attachments become image parts; other attachments, `@agent`/`@skill` mentions, errors and system, compaction or switch records become labelled text. Only invalid message JSON or a non-array assistant `content` fails a V2 session; other malformed fields are left empty. Input tokens include cache reads and writes, output tokens include reasoning, and legacy parent sessions add their descendants' usage. ZCode uses the legacy reader, skips `subagent_child` sessions and keeps plan and image parts. Synthetic input, system/skill messages, compaction and shell records are excluded from collect. `OPENCODE_DB` selects a custom or channel database; a missing explicit path never falls back, and `:memory:` is unavailable. Referenced attachment files are never opened. Running and archived records remain readable; pending inbox items are excluded. Raw export remains normalized `.raw.json`, not an OpenCode import file. See the [design and acceptance scope](docs/providers/opencode-v2.md).
 
 ## Command-line Arguments
 
@@ -541,7 +584,7 @@ agent-dump --interactive --time-field updated -d 7
 
 `--days` uses the Provider-reported `updated_at` by default, so it finds sessions with activity in the last N days, including sessions created much earlier. Add `--time-field created` to filter by creation time instead. This option is available only for list, search, browse and interactive modes; collect dates and statistics retain their existing meaning.
 
-Activity lists order by updated time before applying a result limit. Human lists and interactive selection retain Provider groups; dates and Today/Yesterday groups use the selected time field. Search still orders primarily by relevance. JSON records retain both original timestamps. Discovery may scan metadata outside the creation-time window to find old active sessions; filtering uses the existing Provider-projected `updated_at` fact without adding a separate file-modification-time filter. Provider coverage and partial-discovery diagnostics remain unchanged.
+Activity lists order by updated time before applying a result limit. Human lists and interactive selection retain Provider groups; dates and Today/Yesterday groups use the selected time field. Search still orders primarily by relevance. JSON records retain both original timestamps. Discovery may scan metadata outside the creation-time window to find old active sessions. File-based Providers skip session files last modified before the window, so a file whose modification time is older than its recorded activity is not found by an activity window; filtering otherwise uses the Provider-projected `updated_at` fact. Provider coverage and partial-discovery diagnostics remain unchanged.
 
 ### Machine-readable output
 
@@ -589,7 +632,7 @@ Give an Agent this single command to obtain instructions and executable commands
 agent-dump codex://SESSION_ID --read-prompt
 ```
 
-`--read-prompt` works with every registered Provider, including Claude Code, OpenCode, ZCode, Kimi, Cursor, Pi, DeepChat, Cherry Studio and MiniMax Code. It validates the URI syntax without discovering sources, reading transcripts, calling a model or creating files. Generated commands use the running native executable's absolute path and require the original Provider path environment variables. Instructions follow `--lang en|zh`. Generating a prompt does not confirm that the session exists or has been read.
+`--read-prompt` works with every registered Provider, including Claude Code, Qoder, Qoder CN, OpenCode, ZCode, Kimi, Kimi-Code, Cursor, Droid, Grok, Pi, oh-my-pi, Gemini CLI, DSH, DeepChat, Cherry Studio, MiniMax Code and Antigravity CLI. It validates the URI syntax without discovering sources, reading transcripts, calling a model or creating files. Generated commands use the running native executable's absolute path and require the original Provider path environment variables. Instructions follow `--lang en|zh`. Generating a prompt does not confirm that the session exists or has been read.
 
 Direct reading is also available:
 

{agent_dump-1.2.4 → agent_dump-1.2.5}/README.md

@@ -47,13 +47,22 @@ Follow the generated read commands and cursors until `has_more=false` to cover t
 - **OpenCode** - Open source AI coding assistant
 - **ZCode** - ZCode coding assistant sessions
 - **Claude Code** - Anthropic's AI coding tool
+- **Qoder** - Qoder CLI sessions
+- **Qoder CN** - Qoder CN CLI sessions
 - **Codex** - OpenAI's command-line AI coding assistant
 - **Kimi** - Moonshot AI assistant
+- **Kimi-Code** - Kimi Code CLI sessions
 - **Cursor** - Cursor composer sessions
+- **Droid** - Factory Droid CLI sessions
+- **Grok** - Grok CLI sessions
 - **Pi** - Earendil's AI coding agent
+- **oh-my-pi** - Pi-based coding agent (`omp`)
+- **Gemini CLI** - Google's command-line AI coding agent
+- **DSH** - DeepSeek Harness sessions
 - **DeepChat** - Current local sessions from unencrypted databases
 - **Cherry Studio** - Local 2.x chats and agent sessions
 - **MiniMax Code** - Current CLI sessions from local SQLite storage
+- **Antigravity CLI** - Conversation databases; tool results are not decoded
 - **More Tools** - PRs are welcome to support other AI coding tools
 
 ## Features
@@ -64,7 +73,7 @@ Follow the generated read commands and cursors until `has_more=false` to cover t
 - **Summarize conversations**: Collect all eligible user/assistant text through bounded chunks, or hand the task to an external Agent. Failures are marked as incomplete.
 - **Automate**: Query metadata, capabilities, search evidence, and statistics as JSON; unknown facts remain explicit.
 
-Available formats and message details depend on the source tool. Normalized output does not reproduce every private field or attachment file. Run `agent-dump --providers --json` to inspect capabilities.
+Available formats and message details depend on the source tool. Normalized output does not reproduce every private field or attachment file. Except for MiniMax Code, transcripts drop `system-reminder` and slash-command wrapper tags (`command-*`, `local-command-*`), trim trailing whitespace, and omit messages left empty by that cleanup. Run `agent-dump --providers --json` to inspect capabilities.
 
 ## Installation
 
@@ -172,12 +181,21 @@ Supported URI schemes:
 - `codex://<session_id>` - Codex sessions
 - `codex://threads/<session_id>` - Codex sessions
 - `kimi://<session_id>` - Kimi sessions
+- `kimi-code://<session_id>` - Kimi-Code sessions
 - `claude://<session_id>` - Claude Code sessions
-- `cursor://<requestid>` - Cursor sessions (`requestid` is used as URI identifier)
+- `qoder://<session_id>` - Qoder sessions
+- `qoder-cn://<session_id>` - Qoder CN sessions
+- `cursor://<composer_id>` - Cursor sessions (legacy `cursor://<requestid>` URIs still resolve to the same session)
+- `droid://<session_id>` - Droid sessions
+- `grok://<session_id>` - Grok sessions
 - `pi://<session_id>` - Pi sessions
+- `omp://<session_id>` - oh-my-pi sessions
+- `gemini-cli://<session_id>` - Gemini CLI sessions
+- `dsh://<session_id>` - DSH sessions
 - `deepchat://<session_id>` - DeepChat sessions
 - `cherry://topic-<id>` / `cherry://session-<id>` - Cherry Studio chats / agent sessions
 - `minimax://<session_id>` - MiniMax Code CLI sessions
+- `antigravity-cli://<conversation_id>` - Antigravity CLI conversations
 
 ### Typical Errors
 
@@ -232,37 +250,62 @@ listed and fails when there is nothing to list because no provider has data.
 
 ## Path Discovery
 
-`agent-dump` resolves most session roots in this order: official environment variable, tool default directory, then local development fallback under `data/<agent>`. ZCode currently uses only its macOS/Windows default database path.
+`agent-dump` resolves most session roots in this order: official environment variable, tool default directory, then local development fallback under `data/<agent>`. ZCode currently uses only its macOS/Windows default database path. Path environment variables are trimmed, blank values are ignored, and a leading `~` expands to the home directory.
 
 - **Codex**: `CODEX_HOME` -> `~/.codex` -> `data/codex`
 - **Claude Code**: `CLAUDE_CONFIG_DIR` -> `~/.claude` -> `data/claudecode`
+- **Qoder**: `QODER_CONFIG_DIR` -> `~/.qoder` -> `data/qoder`
+- **Qoder CN**: `QODERCN_CONFIG_DIR` -> `~/.qoder-cn` -> `data/qoder-cn`
 - **Kimi**: `KIMI_SHARE_DIR` -> `~/.kimi` -> `data/kimi`
+- **Kimi-Code**: `KIMI_CODE_HOME` -> `~/.kimi-code` -> `data/kimi-code`. A session is a `sessions/<hash>/<id>/` directory with both `state.json` and `agents/main/wire.jsonl`; sessions without messages are skipped. The working directory comes from `workDir` or `custom.cwd` in `state.json`, then `session_index.jsonl` in the data root.
 - **OpenCode**: `OPENCODE_DB` selects one database (relative to `XDG_DATA_HOME/opencode` or `~/.local/share/opencode`). Otherwise use `opencode.db` there, then the legacy Windows `LOCALAPPDATA`/`APPDATA` location, then `data/opencode/opencode.db`.
+- **Droid**: `FACTORY_HOME_OVERRIDE/.factory` -> `~/.factory` -> `data/droid`. A session is a `<id>.jsonl` file in `sessions/` or one folder below it whose first line is a `session_start` record; sessions without visible messages are skipped, and so are messages marked `llm_only`. The working directory comes from `lastCwd` or `cwd` in `session_start`. Token usage and the model come from the sibling `<id>.settings.json`; custom model ids map through `customModels` in the data root `settings.json`.
 - **ZCode**: macOS `~/.zcode/cli/db/db.sqlite`; Windows `%USERPROFILE%\.zcode\cli\db\db.sqlite`; no Linux default path
-- **Cursor**: Cursor's default user `globalStorage/state.vscdb`
-- **Pi**: `PI_HOME` -> `~/.pi` -> `data/pi`
+- **Cursor**: `CURSOR_DATA_PATH/globalStorage/state.vscdb`; defaults to the `User` directory under macOS `~/Library/Application Support/Cursor`, Windows `%APPDATA%\Cursor`, or Linux `${XDG_CONFIG_HOME:-~/.config}/Cursor`. The working directory comes from the workspace folder in `workspaceStorage/*/workspace.json` that lists the composer.
+- **Grok**: `GROK_HOME` -> `~/.grok` -> `data/grok`. Every `summary.json` under `sessions/`, at any depth, is a session when its `info` has both `id` and `cwd`; messages come from the sibling `updates.jsonl`, and sessions without messages are skipped. Prompts discarded by a rewind are left out of the transcript. See the [Grok reading rules](docs/providers/grok.md).
+- **Pi**: `PI_CODING_AGENT_SESSION_DIR` -> absolute `sessionDir` in the agent directory's `settings.json` -> `<agent directory>/sessions` -> `data/pi`. The agent directory is `PI_CODING_AGENT_DIR`, then `PI_HOME/agent`, then `~/.pi/agent`.
+- **oh-my-pi**: `XDG_DATA_HOME/omp/sessions` when `XDG_DATA_HOME/omp` exists (not on Windows) -> `~/.omp/agent/sessions` -> `data/omp`
+- **Gemini CLI**: `GEMINI_CLI_HOME/.gemini/tmp` -> `~/.gemini/tmp` -> `data/gemini-cli`. `GEMINI_CLI_HOME` is the directory that contains `.gemini`, not the data directory itself.
+- **DSH**: `DSH_HOME` -> `~/.dsh` -> `data/dsh`. Sessions are logs under `sessions/<project>/<session>/`; attachments are read from `attachments/v1` in the data root.
 - **DeepChat**: `DEEPCHAT_USER_DATA_DIR/app_db/agent.db`; defaults to macOS `~/Library/Application Support/DeepChat/app_db/agent.db`, Windows `%APPDATA%\DeepChat\app_db\agent.db`, or Linux `${XDG_CONFIG_HOME:-~/.config}/DeepChat/app_db/agent.db`.
-- **Cherry Studio**: `CHERRY_STUDIO_USER_DATA_DIR/Data/cherrystudio.sqlite`; otherwise the first existing database in the user data directories configured by `~/.cherrystudio/boot-config.json`, then the platform default: macOS `~/Library/Application Support/CherryStudio`, Windows `%APPDATA%\CherryStudio`, or Linux `${XDG_CONFIG_HOME:-~/.config}/CherryStudio` (each with `Data/cherrystudio.sqlite`). The override is provided by agent-dump; use it for portable/dev installations or to select among multiple installations.
-- **MiniMax Code**: `MINIMAX_DATA_DIR` → `MAVIS_DATA_DIR` → `~/.minimax`; the database is `v2/sqlite/runtime-state.sqlite` under the selected root. Only one root is selected; a missing explicit path never falls back to another installation.
+- **Cherry Studio**: `CHERRYSTUDIO_USER_DATA_DIR` or `CHERRY_STUDIO_USER_DATA_DIR`, then `Data/cherrystudio.sqlite`; otherwise the first existing database in the user data directories configured by `~/.cherrystudio/boot-config.json`, then the platform default: macOS `~/Library/Application Support/CherryStudio`, Windows `%APPDATA%\CherryStudio`, or Linux `${XDG_CONFIG_HOME:-~/.config}/CherryStudio` (each with `Data/cherrystudio.sqlite`). Use the override for portable/dev installations or to select among multiple installations.
+- **MiniMax Code**: `MINIMAX_DATA_DIR` → `MAVIS_DATA_DIR` → `~/.minimax`, or `~/.minimax-code` when only that directory has a database; the database is `v2/sqlite/runtime-state.sqlite` under the selected root. Only one root is selected; a missing explicit path never falls back to another installation.
+- **Antigravity CLI**: `AGY_CONVERSATIONS_DIR` -> `~/.gemini/antigravity-cli/conversations` -> `data/antigravity-cli/conversations`. Each `<conversation_id>.db` below it is a session; the optional `conversation_summaries.db` in its parent directory supplies the title, working directory, and update time. Antigravity IDE `.gemini/antigravity/conversations/*.pb` files are not read.
 
 Notes:
 
 - On Windows, prefer configuring the tool's official environment variable when available.
 - The `data/<agent>` fallback is kept for local development and tests.
 
-DeepChat reads saved sessions in the current `agent.db`, including migrated history, ACP sessions, and subagent sessions; drafts are excluded. It supports listing, query, search, stats, collect, and print / JSON / Markdown exports. Structured messages take precedence over the `content` fallback. Text, reasoning, and tool records are normalized; compaction markers do not enter collect. JSON also retains attachment references, links, and other message blocks. Attachment files and offloaded tool output are not read. Token totals come from message records; billing cost is unavailable.
+Codex scans `sessions` and `archived_sessions` and reads only `rollout-*.jsonl` and `rollout-*.jsonl.zst`; when both exist, the uncompressed file wins. Raw export of a compressed rollout writes the decompressed JSONL. Titles come from the title index, then the first line of the first user message in the first 20 records that is not injected context. Developer and system messages, and user messages that contain injected-context markers, are excluded. Token totals add each `token_count` delta once, include remote compaction and subagent usage, exclude history a fork replays from its parent, and record cache reads. Subagent rollouts are listed as separate sessions; when the parent never received a completion notification, the subagent's final reply is inserted into the parent. For uncompressed files over 256 KiB, listing reads only the head and tail, so the message count is unknown.
+
+Claude Code lists `<project>/<session>.jsonl` files and the subagent transcripts under `<session>/subagents/`, including workflow agents in `subagents/workflows/<run>/agent-*.jsonl`. Each subagent is a separate session identified by its agent ID, and the parent message that starts it records `subagent_id`. Sessions without a visible message are skipped. Titles use the latest custom title, then the AI title, the subagent name or description, `sessions-index.json`, and the first line of the first user prompt within the first 20 records. Message counts include visible records only. Token totals keep the last usage of each API request and count cache reads and writes as input.
+
+Qoder and Qoder CN keep the Claude Code project layout under `projects/` and follow the same rules; assistant messages are labeled `qoder` or `qoder-cn`.
+
+Pi reads only the active branch: it follows `parentId` back from the last entry that has an id, so abandoned branches are excluded from exports, search, and counts. Legacy files without entry ids are read in file order. Tool results are merged into their tool calls with status and `details`; bash executions get a status from the exit code and cancellation flag. Only custom messages with `display: true` are kept. Tokens are recorded per message, and input includes cache reads and writes. Sessions without visible messages are not listed. Titles come from the `session_info` name, then a `title` record, the header `title`, and the first user message. For files over 256 KiB, listing reads only the head and tail, so the message count is unknown.
+
+oh-my-pi follows the Pi rules; assistant messages are labeled `omp`. Subagent and advisor transcripts in the directory named after a session file are listed as separate sessions, identified by their header `id`, without a link to the parent session.
+
+Gemini CLI lists `tmp/<project>/chats/*.jsonl` and legacy `*.json` chats, plus subagent chats in `chats/<parent session id>/`. A legacy `.json` chat that was resumed as `.jsonl` is read only from the `.jsonl` file. Files without a `sessionId` and sessions without messages are skipped. JSONL records are replayed in order, including `$set`, `$patch`, and `$rewindTo` updates. The working directory comes from `tmp/<project>/.project_root`. Titles use the chat `summary`, then the first user prompt that does not start with `<session_context>` or `<hook_context>`. User text prefers `displayContent`. Thought summaries become reasoning, and tool calls take results from the call record or a later `functionResponse`. Input tokens include cached and tool-use prompt tokens; output totals include thinking tokens. Subagent chats are listed as separate sessions without a link to the parent.
+
+DSH reads one log per session directory: the newest `session.jsonl`, `session.v<N>.jsonl` or `.jsonl.zstd` file by format version, then modification time. A log counts only in the directories DSH derives from its own working directory and session ID. Logs with an invalid header or non-contiguous sequence numbers and sessions without messages are skipped. A record or zstd frame still being written at the end is ignored, and raw export of a compressed log writes the decompressed JSONL. A forked session excludes the events it inherited from its parent. A streamed step without a final message is rebuilt from its chunks. Tool results are merged into their tool calls with status and metadata. Images are read only when the attachment matches its recorded SHA-256 digest and size; a message whose images are all unavailable shows `Image attachment unavailable`. Titles come from the session title, then the subagent label, the first user message, an inherited title and the working directory name. Input tokens include cache reads and writes, and output tokens include reasoning. Billing cost is never estimated.
+
+DeepChat reads saved sessions in the current `agent.db`, including migrated history, ACP sessions, and subagent sessions; drafts, sessions without messages, and sessions whose parent chain forms a loop are excluded. The update time is the latest of the session, message, block, and usage records. It supports listing, query, search, stats, collect, and print / JSON / Markdown exports. Structured messages take precedence over the `content` fallback, and plain-text `content` becomes message text. Text, reasoning, plan, image, and tool records are normalized; other blocks with text become message text, and compaction markers do not enter collect. Referenced sessions, attachment paths, and links become message text, so search finds them; JSON also keeps the attachment and link records. Attachment files and offloaded tool output are not read. Token totals come from `deepchat_usage_stats`, falling back to message metadata, with cached tokens capped at the input count; billing cost is unavailable.
 
 SQLCipher databases, direct reads of legacy `chat.db`, and raw export are unsupported. The reader does not run DeepChat migrations or Tape recovery. Set `DEEPCHAT_USER_DATA_DIR` to read a custom user data directory.
 
-Cherry Studio supports listing, query, search, stats, collect, and print / JSON / Markdown exports from its current 2.x database, including migrated history. Ordinary chats expose only the active root-to-leaf path; other branches and parallel model replies are excluded from exports, search, and counts. Structural roots and empty reserved user leaves are excluded. Agent sessions are read chronologically and use their workspace as the working directory; ordinary chats have no working directory. Deleted sessions and chat messages are excluded.
+Cherry Studio supports listing, query, search, stats, collect, and print / JSON / Markdown exports from its current 2.x database, including migrated history. Ordinary chats expose only the active root-to-leaf path; other branches and parallel model replies are excluded from exports, search, and counts. Structural roots, records that are neither user nor assistant messages, and messages with neither content nor usage are excluded; sessions left without messages are not listed. Agent sessions are read chronologically and use their workspace as the working directory; ordinary chats have no working directory. Deleted sessions and messages are excluded. File parts become images or `Attachment:` text, and compact summaries become message text. Missing token totals are summed from their details, reasoning tokens are recorded, and recorded USD costs count toward the cost. An unnamed session takes its title from the first user message, then `Cherry Studio`; the update time is the session's last activity.
 
 Text, reasoning, tool calls/results, code, and translations are normalized. JSON retains file references and control events; compaction summaries and internal events do not enter collect or search. Token totals come from message stats. Per-currency costs are preserved in JSON without conversion or an aggregate billing total. The reader never opens attachment files, scans SDK logs, or runs application migrations. Direct reads of 1.x IndexedDB/Redux data and raw export are unsupported.
 
-MiniMax Code supports listing, query, search, stats, collect, and print / JSON / Markdown exports from the current CLI's migrated display messages. Visible conversations, child tasks, and archived sessions are included; hidden and internal peek/channel/cron sessions are excluded. Messages follow database row order and preserve text, reasoning, tool state/results, and attachment references. Compaction, review, and system events do not enter collect or search. The model comes from session metadata and remains unknown when absent; JSON retains recorded per-message token usage without estimating billing cost.
+MiniMax Code supports listing, query, search, stats, collect, and print / JSON / Markdown exports from the current CLI's migrated display messages. Sessions without message rows, hidden root sessions, and internal peek/channel/cron sessions are excluded; hidden child sessions and archived sessions are kept. Untitled sessions use the first non-automated user message, and the update time includes message and token-usage times. Messages follow database row order and preserve text, reasoning, tool state/results, and attachment references; attachments and message errors also become text. Compaction and review events keep their user/assistant role with a label such as `Context compacted`, so they enter search and collect; system events and permission responses do not. A tool fails when its result reports `isError` or `error`, and a task tool's single child session becomes `subagent_id`. The session model comes from session metadata and remains unknown when absent. Token usage comes from `local_runtime_token_usage`: session stats count every row, and a turn with one model attaches its model, tokens (including reasoning), and recorded USD cost to the turn's last assistant message. Billing cost is never estimated.
+
+Set `MINIMAX_DATA_DIR` explicitly for custom profiles or other directories. The reader does not read model-context JSONL or attachment files, run migrations, or recover rewound messages. Raw export, direct legacy storage reads, and desktop data are unsupported. Pending migrations and corrupt sessions produce diagnostics instead of appearing empty. See the [MiniMax Code design and acceptance scope](docs/providers/minimax.md).
 
-Set `MINIMAX_DATA_DIR` explicitly for custom profiles, earlier source builds using `~/.minimax-code`, or other directories. The reader does not read model-context JSONL or attachment files, run migrations, or recover rewound messages. Raw export, direct legacy storage reads, and desktop data are unsupported. Pending migrations and corrupt sessions produce diagnostics instead of appearing empty. See the [MiniMax Code design and acceptance scope](docs/providers/minimax.md).
+Antigravity CLI supports listing, query, search, stats, collect, and print / JSON / Markdown exports. Databases are opened read-only, and only the Protobuf fields for user prompts, assistant text, title updates, tool calls, step times, and token usage are decoded. Tool results are not stored in a known format, so tool calls have status `unknown` and keep the native step type and status in metadata; other unrecognized steps are skipped. Databases without steps are not listed. Titles come from the latest title step, the summary title, then the first user prompt. Steps without a native time use the summary update time or the database modification time and are marked as inferred, so collect does not date them. Usage repeated across retries is counted once and attached to the next assistant message; usage after the last step becomes a usage-only assistant message. Input includes cache tokens and session output includes reasoning; cost is not estimated. Raw export is unsupported. A malformed step or unsupported table fails only that session. See the [Antigravity CLI reading rules](docs/providers/antigravity-cli.md).
 
-OpenCode supports legacy SQLite and 2.x `session_v2/session_message`. When both schemas coexist, V2 wins for the same session ID; legacy-only sessions remain readable. V2 messages follow `seq` order, and counts include system and status records. Synthetic input, system/skill messages, compaction and shell records are excluded from collect. `OPENCODE_DB` selects a custom or channel database; a missing explicit path never falls back, and `:memory:` is unavailable. Attachments stay in JSON metadata without fetching referenced files. Running and archived records remain readable; pending inbox items are excluded. Raw export remains normalized `.raw.json`, not an OpenCode import file. See the [design and acceptance scope](docs/providers/opencode-v2.md).
+OpenCode supports legacy SQLite and 2.x `session_v2/session_message`. When both schemas coexist, V2 wins for the same session ID. Until `migration.v1-v2` is completed, legacy sessions that OpenCode has not copied yet stay listed; after that only V2 is read, so sessions deleted in V2 do not come back. Sessions without visible messages are not listed, and message counts include only visible messages. An empty title falls back to the first user text, then `Untitled Session`. V2 messages follow `seq` order. Image attachments become image parts; other attachments, `@agent`/`@skill` mentions, errors and system, compaction or switch records become labelled text. Only invalid message JSON or a non-array assistant `content` fails a V2 session; other malformed fields are left empty. Input tokens include cache reads and writes, output tokens include reasoning, and legacy parent sessions add their descendants' usage. ZCode uses the legacy reader, skips `subagent_child` sessions and keeps plan and image parts. Synthetic input, system/skill messages, compaction and shell records are excluded from collect. `OPENCODE_DB` selects a custom or channel database; a missing explicit path never falls back, and `:memory:` is unavailable. Referenced attachment files are never opened. Running and archived records remain readable; pending inbox items are excluded. Raw export remains normalized `.raw.json`, not an OpenCode import file. See the [design and acceptance scope](docs/providers/opencode-v2.md).
 
 ## Command-line Arguments
 
@@ -517,7 +560,7 @@ agent-dump --interactive --time-field updated -d 7
 
 `--days` uses the Provider-reported `updated_at` by default, so it finds sessions with activity in the last N days, including sessions created much earlier. Add `--time-field created` to filter by creation time instead. This option is available only for list, search, browse and interactive modes; collect dates and statistics retain their existing meaning.
 
-Activity lists order by updated time before applying a result limit. Human lists and interactive selection retain Provider groups; dates and Today/Yesterday groups use the selected time field. Search still orders primarily by relevance. JSON records retain both original timestamps. Discovery may scan metadata outside the creation-time window to find old active sessions; filtering uses the existing Provider-projected `updated_at` fact without adding a separate file-modification-time filter. Provider coverage and partial-discovery diagnostics remain unchanged.
+Activity lists order by updated time before applying a result limit. Human lists and interactive selection retain Provider groups; dates and Today/Yesterday groups use the selected time field. Search still orders primarily by relevance. JSON records retain both original timestamps. Discovery may scan metadata outside the creation-time window to find old active sessions. File-based Providers skip session files last modified before the window, so a file whose modification time is older than its recorded activity is not found by an activity window; filtering otherwise uses the Provider-projected `updated_at` fact. Provider coverage and partial-discovery diagnostics remain unchanged.
 
 ### Machine-readable output
 
@@ -565,7 +608,7 @@ Give an Agent this single command to obtain instructions and executable commands
 agent-dump codex://SESSION_ID --read-prompt
 ```
 
-`--read-prompt` works with every registered Provider, including Claude Code, OpenCode, ZCode, Kimi, Cursor, Pi, DeepChat, Cherry Studio and MiniMax Code. It validates the URI syntax without discovering sources, reading transcripts, calling a model or creating files. Generated commands use the running native executable's absolute path and require the original Provider path environment variables. Instructions follow `--lang en|zh`. Generating a prompt does not confirm that the session exists or has been read.
+`--read-prompt` works with every registered Provider, including Claude Code, Qoder, Qoder CN, OpenCode, ZCode, Kimi, Kimi-Code, Cursor, Droid, Grok, Pi, oh-my-pi, Gemini CLI, DSH, DeepChat, Cherry Studio, MiniMax Code and Antigravity CLI. It validates the URI syntax without discovering sources, reading transcripts, calling a model or creating files. Generated commands use the running native executable's absolute path and require the original Provider path environment variables. Instructions follow `--lang en|zh`. Generating a prompt does not confirm that the session exists or has been read.
 
 Direct reading is also available:
 

{agent_dump-1.2.4 → agent_dump-1.2.5}/crates/agent-dump-core/Cargo.toml

@@ -21,6 +21,8 @@ sha2.workspace = true
 tempfile.workspace = true
 walkdir.workspace = true
 rusqlite.workspace = true
+# Codex compresses archived rollouts as `.jsonl.zst`; pure Rust keeps builds free of C toolchains.
+ruzstd = { version = "0.9.0", default-features = false, features = ["std"] }
 num-bigint.workspace = true
 toml_edit.workspace = true
 url.workspace = true

{agent_dump-1.2.4 → agent_dump-1.2.5}/crates/agent-dump-core/src/output/diagnostics.rs

@@ -16,12 +16,12 @@ pub fn record_warning(diagnostic: &RecoverableDiagnostic, zh: bool) -> String {
                 format!("⚠️  Failed to convert message format: {error}")
             }
         }
-        RecoverableDiagnostic::PiRecordConvertFailed(error) => {
+        RecoverableDiagnostic::PiRecordConvertFailed { provider, error } => {
             let error = safe_line(error);
             if zh {
-                format!("警告: 转换 Pi 记录失败: {error}")
+                format!("警告: 转换 {provider} 记录失败: {error}")
             } else {
-                format!("⚠️  Failed to convert Pi record: {error}")
+                format!("⚠️  Failed to convert {provider} record: {error}")
             }
         }
         RecoverableDiagnostic::TitleCacheFailed(error) => {

{agent_dump-1.2.4 → agent_dump-1.2.5}/crates/agent-dump-core/src/output/export.rs

@@ -146,7 +146,15 @@ pub fn raw(
     output: &Path,
 ) -> crate::Result<PathBuf> {
     write(output, session_id, ".raw.jsonl", |file| {
-        io::copy(&mut fs::File::open(source)?, file)?;
+        if !crate::storage::zstd::compressed(source) {
+            io::copy(&mut fs::File::open(source)?, file)?;
+            return Ok(());
+        }
+        let (frames, _) = crate::storage::zstd::frames(&fs::read(source)?)
+            .map_err(|error| format!("{}: {error}", source.display()))?;
+        for frame in frames {
+            file.write_all(&frame)?;
+        }
         Ok(())
     })
 }