@dosu/cli 0.66.1 → 0.67.0-beta.2

package/README.md

@@ -105,7 +105,7 @@ Or right-click the binary, select "Open", and click "Open" in the dialog.
 
 `dosu mcp add` takes `-g, --global` to install for all projects instead of project-local, and `--show-secret` to print the full manual config.
 
-`dosu upgrade` delegates to npm, pnpm, Yarn Classic, or Homebrew only after confirming which manager owns the current installation. Temporary package-runner invocations stay ephemeral, ambiguous or local installs are left unchanged, and standalone binaries receive the latest safe manual download path. After a successful update it hands off to the new version, which re-applies the bundled skills and, only if the update crossed a release that changed the agent config format, runs `dosu setup` (or the non-interactive `dosu mcp refresh` without a TTY). Upgrades done outside `dosu upgrade` (npm, brew, `npx @dosu/cli@latest`) get a safety net: when the new version changed the shape of the MCP entry, the first command on it silently rewrites configured tools' MCP entries and prompts you to run `dosu setup` for the rest; the bundled agent skills are always re-applied on the first command after any version change.
+`dosu upgrade` delegates to npm, pnpm, Yarn Classic, or Homebrew only after confirming which manager owns the current installation. Temporary package-runner invocations stay ephemeral, ambiguous or local installs are left unchanged, and standalone binaries receive the latest safe manual download path. After a successful update it hands off to the new version, which re-applies the bundled skills and, only when a configured agent's MCP entry is out of date, runs `dosu setup` (or the non-interactive `dosu mcp refresh` without a TTY). An entry is out of date when it doesn't match the shape the current provider code writes. Upgrades done outside `dosu upgrade` (npm, brew, `npx @dosu/cli@latest`) get a safety net: on the first command of a new version, the CLI checks each configured provider, silently rewrites only the out-of-date entries, and prompts you to run `dosu setup` for the rest; the bundled agent skills are always re-applied on the first command after any version change.
 
 Dosu also updates itself automatically. When the update check (every six hours) finds a newer release, npm, pnpm, Yarn Classic, and Homebrew installs start the same package-manager update in a detached background process. The current command runs unchanged, and your next command uses the new version, whose first run applies the skill and MCP refreshes above. Hooks, rules, and the status line still need `dosu setup` when a release changes them. Background updates never run for `npx` invocations, standalone binaries, CI, or `DOSU_DEV=true`. A failed install (for example, a global npm prefix that needs `sudo`) falls back to the "Run `dosu upgrade`" notice and is retried after six hours. Turn background updates off with `dosu upgrade --auto off` (and back on with `--auto on`), or with `DOSU_DISABLE_AUTOUPDATE=1` for a single environment.
 
@@ -119,7 +119,7 @@ Once authenticated against a deployment, you can drive the Dosu platform without
 | `dosu knowledge` | Search and browse your knowledge base |
 | `dosu docs` | Manage documents (list, create, update, import, publish) |
 | `dosu threads` | List and manage conversation threads |
-| `dosu review` | Document review workflow, plus `review notifications` to route a Library's or Agent's reviews to a Slack channel |
+| `dosu review` | Document review workflow for the selected Library, plus `review notifications` to route a Library's or Agent's reviews to a Slack channel |
 | `dosu sources` | Manage connected data sources (list, connect, create, sync, update) |
 | `dosu integrations` | List and inspect platform integrations (Slack, GitHub, …) |
 | `dosu topics` | List knowledge base topics and their pages |
@@ -185,15 +185,21 @@ dosu knowledge incognito status                            # which agents are in
 The status line shows one of `📚 Dosu studying…` (a sync run is live), `📚 Dosu on`,
 `👻 Dosu incognito`, `⚪ Dosu paused`, `⚪ Dosu not studying this repo`, or `⚪ Dosu off`. Every
 session is studied unless you limit studying to picked repos under `dosu` → settings → study
-scope. Notes from a session with a known repo and branch are anchored to that branch; the rest are
-unanchored and reach topics immediately. Neither setup nor `enable` replaces a status line you
+scope. In an interactive terminal with more than one repo, `dosu setup` asks which repos' sessions
+to ship before offering the backfill of recent sessions. Selecting every repo clears the scope, so
+new repos are included automatically. The choice is saved as the study scope; change it later under
+`dosu` → settings → study scope or with `dosu knowledge scope set`. Notes from a session with a
+known repo and branch are anchored to that branch; the rest are unanchored and reach topics
+immediately. Neither setup nor `enable` replaces a status line you
 already have; they print the one-liner to add to your own script instead.
 
 `incognito on` is a saved per-agent setting: none of that agent's sessions are studied until you
-turn it off. To keep a single chat out instead, type `/dosu-incognito` in it; setup installs that
-command with the hook. It marks the session's transcript so studying skips it (the whole session,
-and for the rest of it — start a new session to turn Dosu back on) and tells the model not to use
-Dosu tools. See [docs/studying.md](docs/studying.md).
+turn it off. Turning it off resumes studying only new sessions going forward; sessions that
+finished while incognito was on stay unstudied permanently, even if a later sync picks them up.
+To keep a single chat out instead, type `/dosu-incognito` in it; setup installs that command with
+the hook. It marks the session's transcript so studying skips it (the whole session, and for the
+rest of it — start a new session to turn Dosu back on) and tells the model not to use Dosu
+tools. See [docs/studying.md](docs/studying.md).
 
 ### Telemetry and privacy