0d57df430e
* feat(cli): add `honcho session view` transcript command Adds a read-only transcript view for a session, with three paging modes: a tail window (`--last N`, the default), server pages (`--page N --size M`), and the whole conversation (`--all`). `--reverse` selects newest-first in every mode, `--ids` exposes message IDs, and `-p` scopes to one peer. JSON mode emits the same shape as `message list`. The renderer is deliberately literal: content and identifiers go through `rich.text.Text` rather than Markdown or console markup, so newlines, tag delimiters like `<thinking>`, and bracketed text survive intact — this is a debugging surface, so it has to show what was actually stored. Timestamps are converted to UTC (not just stripped of their offset) and keep millisecond precision. Nothing is truncated with an ellipsis: a displayed message ID is always usable with `honcho message get`. Flags are validated before the client is built, and the session is constructed directly instead of via the get-or-create `client.session()`, so an invalid or mistyped invocation never reaches — or creates — anything server-side. `--size` is bounded locally to the server's 100-item ceiling rather than surfacing a raw 422, and the "more:" hint echoes back the size and ordering actually in use so following it lands on the adjacent window. Also fixes `honcho message list --last N`, which stopped at the first page of 50: both commands now share the page-walking helper, so the same flag returns the same window either way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(cli): regenerate command reference for `session view` Adds the generated `session view` accordion to the docs snippet and points the session-debugging workflows at it. Trims the docstring to plain prose — the RST double-backticks were rendering literally in `--help`, where every other command uses unmarked flag names — and stops the generator emitting a trailing blank line that tripped end-of-file-fixer on every regeneration. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(cli): carry invocation scope into the next-page hint Addresses CodeRabbit review on #1006. The "more:" hint echoed only `--page`, `--size`, and `--reverse`, so copying it off a scoped invocation dropped `-w`, `-p`, and `--ids` — landing on a different workspace or an unfiltered transcript. Hint construction moves into `_next_page_command` in the command module, which knows the invocation; the renderer now just prints the string it's handed and no longer needs to know CLI flag syntax. Only flags passed explicitly are echoed, since anything from the environment or config resolves the same way on the next run. Also rejects non-positive `--last` on `honcho message list`, which slice semantics turned into a silently empty result. `session view` already errored on it; the two now agree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(cli): read next-page hint scope from effective flag overrides Addresses the second CodeRabbit pass on #1006. `-w`/`-p` parse at group and top level as well as command level, all landing in `_global_overrides`, so reading the command-level params dropped the scope from `honcho session -w ws2 view ...`. The hint now reads the effective overrides via a new `get_flag_overrides()`, which deliberately excludes environment and config values since those resolve the same way on the next run. Also shell-quotes the hint's identifiers with `shlex.join`. Note this is hardening rather than a live injection fix: the API constrains IDs to `^[a-zA-Z0-9_-]+$`, so an ID carrying a space or metacharacter fails the fetch before any hint is printed. `validate_resource_id` is looser than the server though, so quoting is the cheaper invariant to hold locally. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| changelog | ||
| images | ||
| logo | ||
| snippets | ||
| v1 | ||
| v2 | ||
| v3 | ||
| README.md | ||
| bun.lock | ||
| docs.json | ||
| favicon.svg | ||
| package.json | ||
README.md
Honcho Docs
These docs are built using Next.js via mintlify.
Setting Up Honcho's Docs Locally
- Clone the repository:
git clone git@github.com:plastic-labs/honcho.git
- Navigate into the
docsfolder:
cd honcho/docs/
The docs folder contains the markdown files that make up the documentation. The majority of the files are in the pages directory. Some notable files in this folder include:
- Verify that you have Node.js and npm installed in your system. You can check by running:
node --version
npm --version
-
If not installed, download Node.js and npm from the respective official websites.
-
Once you have Node.js and npm running, proceed to install
pnpm- another package manager that helps to manage project dependencies:
npm install -g pnpm
- Install the project dependencies using pnpm:
pnpm i
- After the successful installation of the project dependencies, start the local server:
pnpm dev
Now, you should be able to view the docs on your local environment by visiting http://localhost:3000. You can explore the different markdown files and make changes as you see fit.