Show HN: Discuss CLI – No more reviewing agent plans in the terminal

Discuss CLI Stop reviewing agent plans in the terminal. discuss opens any Markdown file (or piped stdin) in your browser with PR-style comment threads on every paragraph. Your Codex or Claude Code session reads your comments and replies in the margins — same terminal session, no copy-paste. Anchored. Threaded. Bidirectional. No cloud. Why? Markdown is how engineers share everything that isn't code — PRDs, design docs, RFCs, incident post-mortems, analysis notes. But review tools assume the thing being reviewed is a diff. Docs either get copy-pasted into a chat window, marked up in Google Docs comments no agent can read, or ignored. discuss makes the doc itself the workspace: Inline anchored threads — click any paragraph, drop a comment, get a threaded response. Syntax highlighting — tag fenced code blocks with a language (e.g. ```rust, ```diff-typescript) for browser-side highlighting. See Prism's supported languages for the full set. Takes vs replies — the agent posts takes (its view), humans post replies. Rendered distinctly so you can tell who said what at a glance. Bidirectional — the browser writes through a local REST API; the agent reads stdout events and writes back through the same API. No cloud. One Rust binary, one localhost server, one browser tab. Install Pre-built binary (curl | sh) curl -sSL https://raw.githubusercontent.com/codesoda/discuss-cli/main/install.sh | sh Downloads the latest release tarball from GitHub, installs the binary to ~/.discuss/bin/, symlinks ~/.local/bin/discuss, fetches the /discuss skill files into ~/.discuss/skills/discuss/, and links them into every agent root present (~/.claude/skills/, ~/.codex/skills/, ~/.agents/skills/). From a clone git clone https://github.com/codesoda/discuss-cli.git cd discuss-cli ./install.sh Same outcome as the curl path, but builds the binary from source with cargo build --release and links the skill directly out of the clone so git pull updates it. Quick Start With an agent (the main use case) In Claude Code, Codex, or any agent with the /discuss skill, just ask: Can you discuss ./plan.md with me? The agent invokes the skill. If discuss isn't on your PATH yet, it'll prompt before running the installer: discuss isn't on your PATH. Install it now? (runs curl -sSL https://raw.githubusercontent.com/codesoda/discuss-cli/main/install.sh | sh) Confirm — the installer self-bootstraps in the background, the server launches on http://127.0.0.1:7777, your browser opens with the rendered doc, and the agent starts streaming events. Drop an inline thread anywhere and the agent replies with a take. Without an agent discuss ./plan.md Browser opens on http://127.0.0.1:7777. You get the full review UI — inline threads, replies, resolution — without any agent participation. Useful for solo review. Piping markdown via stdin discuss reads from stdin when given - explicitly, or auto-detects a non-TTY stdin when no file argument is supplied. Useful for ad-hoc review of generated markdown without writing a temp file: git diff --cached | render-as-markdown | discuss - echo "# Quick note\n\nReview this." | discuss In stdin mode, session.started reports source_file: "<stdin>" and history archives are written under <history-dir>/unnamed/<timestamp>.json since there's no source path to derive a folder name from. Bare discuss in an interactive terminal still prints help and exits 2. CLI Command Description discuss <file> Open a markdown file in a browser-based review session discuss - Read…

This excerpt is published under fair use for community discussion. Read the full article at GitHub.