@open-agent-toolkit/cli 0.1.59 → 0.1.62

package/README.md

@@ -40,6 +40,20 @@ Additional useful entry points:
 - `oat repo archive sync`
 - `oat doctor`
 
+## Update Notifications
+
+On ordinary interactive command runs, OAT may print a passive notice when npm's stable `latest` CLI version is newer than the installed version. The cache normally limits checks to once every 24 hours and same-version notices to once every 72 hours; overlapping CLI processes can each perform a check or print a notice.
+
+`oat init`, `oat tools install`, and `oat tools update` are different because they copy tools bundled with the running CLI. Before an eligible interactive mutation, a known newer CLI triggers a warning that the current CLI can only install its own bundled tool versions and that the available CLI may bundle newer versions. OAT then offers, defaulting to no, to run `npm install --global @open-agent-toolkit/cli@<validated-version>` for the exact validated stable version. Acceptance updates the CLI package, stops before changing tools, and asks you to rerun the original command. Declining or aborting continues with the current bundle after a warning. An installer failure stops the tool mutation and reports the command you can retry.
+
+This warning does not mean tools installed from the current bundle are incompatible with the current CLI; it only identifies that a newer CLI release may include newer bundled tool versions. Dry-run, JSON, non-interactive, CI, test, source-development, and ephemeral package-runner invocations do not prompt or install. Ordinary eligible commands remain passive.
+
+Set `NO_UPDATE_NOTIFIER` to a truthy value (for example, `1`, `true`, `yes`, or `on`) to suppress checks for one process; empty, `0`, and `false` do not suppress them. Or persist the user-level preference:
+
+```bash
+oat config set updateNotifications false --user
+```
+
 ## Inspection Commands
 
 Use these commands when you want structured runtime/project state out of the CLI:

package/assets/docs/cli-utilities/config-and-local-state.md

@@ -113,6 +113,26 @@ Use `oat config` for repo runtime config inspection and supported key mutation.
 
 Use `oat config dump --json` when you need the whole resolved config in one machine-readable response rather than a single key or a human-oriented list view.
 
+### Update notifications
+
+OAT can passively report when npm's stable `latest` CLI version is newer during an ordinary interactive command run. The cache normally limits checks to once every 24 hours and same-version notices to once every 72 hours; overlapping CLI processes can each perform a check or print a notice. Ordinary eligible commands only show update guidance and do not prompt.
+
+Before eligible interactive `oat init`, `oat tools install`, or `oat tools update` mutations, a known newer stable CLI receives special handling. These commands copy tool versions bundled with the running CLI, so OAT warns that the older CLI can only install its own bundle and that the available CLI may contain newer bundled tools. The default-no prompt offers to install the exact validated version with:
+
+```bash
+npm install --global @open-agent-toolkit/cli@<validated-version>
+```
+
+If accepted, OAT updates the CLI package, stops before changing tools, and asks you to rerun the original command under the new CLI. If declined or the prompt is aborted, OAT warns and continues with the current bundle. If npm fails, the requested tool mutation does not run and the error includes a command to retry. The warning describes possible bundle freshness; it does not claim that tools installed by the current CLI are incompatible with that CLI.
+
+Checks, notices, and the update offer are skipped for JSON, non-interactive, CI, test, source-development, and ephemeral package-runner invocations. Guarded dry-run commands also skip the prompt and installer. Set `NO_UPDATE_NOTIFIER` to a truthy value (for example, `1`, `true`, `yes`, or `on`) to suppress checks for one process; empty, `0`, and `false` do not suppress them. Or disable checks persistently in user config:
+
+```bash
+oat config set updateNotifications false --user
+```
+
+The preference defaults to `true`; run the same command with `true` to re-enable it. Cached check and notice timestamps live in `~/.oat/update-check.json`, separate from the user-authored preference in `~/.oat/config.json`.
+
 Dispatch policy keys are part of this surface, but provider-specific generation
 still belongs to provider commands. Use `oat config describe
 workflow.dispatchPolicy.policy` to inspect capped managed, managed uncapped,

package/assets/docs/cli-utilities/tool-packs.md

@@ -49,6 +49,25 @@ skills can use the utility engine directly.
 
 The `oat tools` command group provides a unified interface for managing installed tools (skills and agents) across scopes.
 
+### CLI updates before bundled-tool mutations
+
+Tool packs ship inside the OAT CLI package. An older CLI can therefore install or update only the tool versions in its own bundle, while a newer stable CLI release may contain newer bundled versions. This is a bundle-freshness warning, not a claim that tools installed by the current CLI are immediately incompatible with it.
+
+Before an eligible interactive `oat init`, `oat tools install` (including pack subcommands), or `oat tools update` mutation, OAT checks the cached stable CLI availability. If a newer version is known, it explains the bundle difference and offers, with a default answer of no, to install that exact validated version:
+
+```bash
+npm install --global @open-agent-toolkit/cli@<validated-version>
+```
+
+- Accepting updates the CLI package only, stops before changing bundled tools, and asks you to rerun the original command under the new CLI.
+- Declining or aborting warns that the current bundle may be older, then continues the requested command.
+- If npm fails, OAT does not run the tool mutation and reports how to retry the CLI installation.
+- Dry-run, JSON, non-interactive, opted-out, CI, test, source-development, and ephemeral package-runner invocations do not prompt or install.
+
+Set `NO_UPDATE_NOTIFIER` to a truthy value (for example, `1`, `true`, `yes`, or `on`) to suppress checks for one process; empty, `0`, and `false` do not suppress them.
+
+Other eligible commands keep the passive update notice and never launch the installer.
+
 ## Install vs. initialize
 
 The `project-management` pack has two lifecycle steps:

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.1.59",
-  "docs-config": "0.1.59",
-  "docs-theme": "0.1.59",
-  "docs-transforms": "0.1.59"
+  "cli": "0.1.62",
+  "docs-config": "0.1.62",
+  "docs-theme": "0.1.62",
+  "docs-transforms": "0.1.62"
 }

package/assets/skills/oat-project-implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-implement
-version: 2.0.40
+version: 2.0.41
 description: Use when plan.md is ready for execution. Dispatches one phase implementer per phase, owns independent phase review and bounded fix routing, and supports plan-declared worktree-isolated parallel phases.
 oat_gateable: true
 argument-hint: '[--retry-limit <N>] [--dry-run]'