Analysis docs for large work (brindle Pro), and a smoother first run
Large work leaves an analysis doc. A goal with 2 or more milestones, a heavy or advanced task, or a handoff/assign with analysis_doc=true gets a rule to write a short doc before reporting: what was built, the decisions and rejected alternatives, how it was verified, known gaps and follow-ups.
The doc is written outside the repo, in ~/.brindle/docs/<repo>/<branch>/, and never committed.
On Free (or in air-gap mode) it stays there, and the folder is added as a Knowledge source so local search finds it. Nothing is sent.
brindle docs manages the library: list, show, delete, share / unshare (with team:<group id> or org:<org id>), and export (--format md|docx|zip, --out).
Your own switches, brindle docs on|off --switch <name>:store (the default), share, assist (briefs), import_upload and prompt_analysis. On paid plans the first four start on and prompt_analysis is opt-in. A switch your organisation enforces can't be overridden.
Briefs from your library (optional, the assist switch). New large work can get a brief of what earlier docs say about it, marked as untrusted reference data, not instructions.
Agents read and update living docs. New MCP tools:
read_analysis_doc reads a library doc and pins the version read; the agent is told when it changes, and its result waits until it has read the newer version.
edit_analysis_doc saves an edit to a draft for the session and branch: published when the branch merges, dropped if it's removed unmerged. Snapshot docs aren't edited; a new doc supersedes them.
request_doc_read asks you to read a doc (optionally at a section) with a one-line reason, as a "Doc to read" item in your Inbox that stays until you dismiss it.
Reviewers see the docs that cover the branch they review.
Org controls for admins:brindle account org docs shows the org's analysis-doc policy and your effective switches; brindle account org docs <switch> <off|default_on|enforced_on|enforced_off> [--group ID] sets one for the org or a team. Enforced settings win over personal choices.
The Inbox drops cards that can no longer be acted on: permission asks that can't be answered, and plan approvals for anything other than a plan-first worker with a supervisor.
On Pro and Team, docs go to your personal library when their branch merges, stored encrypted. The local copy is deleted once the upload succeeds and kept if it fails. The first upload prints a one-time notice; brindle docs off stops storing.
First-run fixes
The installer's PATH note checks your shell's own PATH. When ~/.local/bin isn't on it, the script ends with "Open a new terminal, or run: source ~/.local/bin/env" and, if it installed uv, says which shell files uv updated. The stale BRINDLE_VERSION example is gone; the comment points to PyPI's release history.
Claude Code install hints lead with the official installer (curl -fsSL https://claude.ai/install.sh | bash), with npm as the alternative, in the installer, brindle doctor, preflight and the provider picker. The picker's install now runs it through a shell.
The tmux install hint fits your platform:brew install tmux on macOS, or your distro's package manager on Linux (apt, dnf, pacman, zypper or apk); the installer and brindle doctor give the same command.
brindle init treats its own uncommitted .brindle/ as a next step ("commit .brindle/ to share this config with your team", with the command), not a working-tree warning.
brindle demo no longer prints the --autopilot deprecation notice.
brindle doctor with Claude Code signed out no longer shows a "subscription login" line or a quota note; it says there's no credential yet, and the identity line is a warning instead of a green check.
brindle audit --help no longer names a source file.
Documentation
The README's first screen says who brindle is for, what it adds over running an agent CLI directly, the CLI's requirements (macOS, Linux or Windows through WSL2; tmux and at least one signed-in agent CLI), the license (source-available, not open source) and Free/Pro/Team pricing, ahead of the demo.
The desktop app is macOS and Linux. On Windows, use the CLI inside WSL2; the README no longer offers the app for Windows.
README fact fixes: the default reviewer is Claude (review_profile set to reviewer-codex or reviewer-local for a second model); the install script installs tmux itself only on macOS; brindle needs at least one agent CLI, not Claude Code specifically; the pricing link points to pawdelta.com/brindle/pricing.
Desktop app 0.2.9
Knowledge › Docs: your analysis docs by scope, topic and kind, with search, a results panel, and a reader with Share, Export and Delete.
Export to Download (Markdown, Word, or a zip with appendices), and to Google Docs or SharePoint when your organisation's policy allows them. The online sign-in lasts for the session; tokens are kept in memory only.
Knowledge › Map: explore code areas, documents, local decisions and folders around chosen code paths.
Add to library for an imported folder (optional, per folder): you confirm the exact list of files first, and anything that looks like a secret is skipped and listed.
Sessions show one docs line in the goal panel, linking to the docs that session wrote or used. A session's "Doc to read" requests appear in the Inbox.
Settings: an Analysis docs section with your switches (ones your organisation enforces are shown locked), and a Team destination section for owners and admins to set where the organisation's docs are exported.