Skip to content

Commit ddee8be

Browse files
authored
docs(guide): Command Code chat needs the session herdr reports, and none does yet (#1647)
<!-- See CONTRIBUTING.md for checks, translations, contract tests and the changelog (a file in changelog.d/, never CHANGELOG.md). --> ## Change `docs/guide.md` lists Command Code's chat as a native session file "resolved through herdr". No released herdr resolves it. `cmdTranscriptPath` reads the session herdr reports for the pane, as pi does (`server/cmd.ts`, `session.source === "herdr:cmd"`). herdr keeps a reported session only for the agents in `is_official_agent_source` (`src/agent_resume.rs`), and Command Code is not among them, so the report Command Code sends is dropped and `agent_session` stays absent for the pane. Measured on herdr 0.9.5 + Command Code 1.87.1: ``` herdr agent get <cmd pane> → "agent":"cmd", "title":"Domain Modeling", "tokens":{"model":…} (no agent_session) /api/pane/conversation → {"source":"scrollback","turns":[]} ``` Status, title and model arrive from the same reporter over the same socket, so the pane looks fully integrated while its conversation stays out of reach, and the row promised a chat that cannot appear. The bridge reads the conversation only from the file herdr names — the alternatives (newest file in the project directory, joining herdr's pane title to `<id>.meta.json`) pick the wrong conversation when two `cmd` panes share a folder — so the pane opens in Terminal. This writes that limit where the row points, in the shape the Devin row already uses for its own case. It also notes the part that does work: the permission prompt cards are read off the screen (`server/dialogs/cmd.ts`), not from the session file, so they answer from the chat either way. No code change. `server/cmd.ts` is right; the herdr half was never built. Upstream ask with the exact contract gap: herdrdev/herdr#3333 (herdrdev/herdr#3333 (comment)) ## Validation Docs only — no `src/`, `server/` or `shared/` change, so per AGENTS.md this PR asks for no CodeRabbit review. - `bun test scripts/changelog-fold.test.ts scripts/conventions.test.ts` — 21 pass, 0 fail. - No changelog fragment: nothing a user notices changes, and docs-only commits have none (`302b9eae`, `4555859d`). - Checked the claim against the rest of the tree: README and the site's agent chips list Command Code as an agent the app works with, which stays true (terminal, status, alerts and prompt cards all work); only the guide asserted the chat resolves.
1 parent 4a4bdaa commit ddee8be

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

‎docs/guide.md‎

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ Every agent herdr runs shows up with its live status, terminal and alerts. The c
160160
| **omo** | Native session file, found through the pane's process tree | ✓ the `/model` list (picked for the session); other menus — use Terminal |
161161
| **gjc** | Native session file reported by the web UI's GJC extension, verified against the pane's process | — use Terminal |
162162
| **pi** | Native session file, resolved through herdr; after `/tree`, the branch in play | ✓ its dialogs: a question, a confirmation, an answer typed in |
163-
| **Command Code** (`cmd`) | Native session file under `~/.commandcode/projects/`, resolved through herdr; after `/tree`, the branch in play | ✓ its permission prompts: Yes / Yes, don't ask again / No |
163+
| **Command Code** (`cmd`) | Native session file under `~/.commandcode/projects/`, named by the session herdr reports for the pane (see below); after `/tree`, the branch in play | ✓ its permission prompts: Yes / Yes, don't ask again / No |
164164
| **OpenCode** | Native session in OpenCode 2's own database, resolved through herdr: `~/.local/share/opencode/opencode.db` (`%USERPROFILE%\.local\share\opencode\opencode.db` on Windows), or where the server's `XDG_DATA_HOME` or `OPENCODE_DB` puts it | ✓ its questions on OpenCode 2.0 or later, answered through its background service (`~/.local/state/opencode/service.json`, or under the server's `XDG_STATE_HOME`) one question at a time, with Back to change an earlier one; other prompts, and OpenCode 1 — use Terminal |
165165
| **Devin CLI** | Native SQLite session, showing the active branch when herdr or the live process explicitly identifies the session; otherwise terminal text | — use Terminal |
166166
| **Grok** | Linux native update log. Any Grok executable named `grok` or `grok-…` that holds the `events.jsonl` for the session Herdr reported in exactly one directory, with a newer write time than every other held session. Older open files do not hide it; ambiguous IDs, tied times, and a held file that may be a renamed events file use Terminal. After a `/resume` Herdr does not hear about, Chat can keep showing the previous conversation until the resumed session writes; it then uses Terminal until Herdr names that session. macOS and Windows use Terminal. See [Grok setup and limits](grok-chat.md). | — use Terminal |
@@ -197,6 +197,14 @@ which follows GJC's provider child: a finished turn can stay on working, so no d
197197
comes and no INPUT shows for an open question. Install the extension and restart GJC to
198198
get both chat and done alerts back.
199199

200+
Command Code chat needs the session herdr reports for the pane. Command Code sends that report
201+
and herdr keeps only the sessions of the agents it knows natively, so no released herdr accepts
202+
it yet: the pane's status, title and model arrive, its conversation does not. Without it the
203+
bridge cannot tell which file under `~/.commandcode/projects/` a pane is showing, and two `cmd`
204+
panes in one folder are indistinguishable, so Command Code opens in Terminal. Its permission
205+
prompt cards are read off the screen, not from the session file, so they answer from the chat
206+
either way.
207+
200208
Devin sessions are never selected by directory or recency alone. A plain `devin` shows the
201209
terminal text, since herdr does not report its session without its Devin integration; a session
202210
started with `devin --resume <id>` (or `-r <id>`, as Devin suggests when it exits) is a chat.

0 commit comments

Comments
 (0)