You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7cb6018
Browse filesBrowse the repository at this point in the historyBrowse files
feat(cli): surface outdated CLI and skills to agents; add hyperframes update --check (#7094)
* feat(cli): surface outdated CLI and skills to agents; add hyperframes update
Single commit of #7094 on top of main (no merge commits through the signed
GraphQL path). Includes: 2h update/skills check interval and stale-cache
recheck; `_meta.checkedAt`, `_meta.skillsOutdated`, `_meta.skillsMissing`;
`_meta.updateNotice`, one sentence for the agent to relay to the person, at
most once a day per project (brew/npx-aware command, omitted under CI, the
update-check opt-out and agent plugins); `hyperframes update [--check]
[--yes] [--json]` (CLI then skills at the installed CLI's tag; brew
version read back); doctor names the running binary and its channel; the
hyperframes-cli skill gets one line to pass the notice on, naming no
command. Keeps main's install-target skills check (#7120) in updateSkills.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* fix(cli): update notice names a command that moves this install
- `_meta.updateNotice` (and `update --check`'s skills command) now name a
command that moves the running install: a global npm/pnpm/bun/brew CLI
runs its own `hyperframes update` (or just its manager's command when
only the CLI is behind), since `npx hyperframes` would run a project's
copy or a fresh npx one; a project-local CLI moves with its project's
manager by lockfile (`npm install`/`pnpm add`/`bun add`/`yarn add
hyperframes@<v>`), which `update --yes` now names too instead of
`npx hyperframes@latest`.
- `update`'s confirmation hint states a fact and names no step for the
agent: "Updating is the person's call; `update --check` only reports."
- `upgrade --json`, `upgrade --project --json` and every `skills` JSON
output leave out `_meta.updateNotice` (NO_UPDATE_NOTICE), like `update`.
- dailyNotice: a null/non-object file reads as empty and is repaired; a
future timestamp is stale; writes go through a 0600 tmp file + rename;
withMeta never throws from the notice.
- Docs: --json without --yes exits 2; plugin `update` exits 1
(plugin_managed); full `_meta` sample; per-install notice commands.
`update --check` says "npm registry not reached" instead of "latest".
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
`validate`, `inspect`, and `layout` still work but are
@@ -59,15 +59,42 @@ second call:
59
59
"_meta": {
60
60
"version": "0.1.4",
61
61
"latestVersion": "0.1.5",
62
-
"updateAvailable": true
62
+
"updateAvailable": true,
63
+
"checkedAt": "2026-11-03T08:00:00.000Z",
64
+
"skillsOutdated": 2,
65
+
"skillsMissing": 0,
66
+
"updateNotice": "For the user: HyperFrames CLI 0.1.5 is available (this run is 0.1.4), and 2 installed HyperFrames skills are out of date. To update both, run: hyperframes update"
63
67
}
64
68
}
65
69
```
66
70
67
-
The version numbers come from a cache refreshed at most once a day, in a
71
+
The version numbers come from a cache refreshed at most every two hours, in a
68
72
background process, and never under CI or `HYPERFRAMES_NO_UPDATE_CHECK=1`.
69
-
`--json` never makes a network request of its own. Deprecated commands add
70
-
`_meta.deprecated: true`.
73
+
`checkedAt` says when npm answered. A cached latest older than the running CLI
74
+
is left out and rechecked on the next run. `skillsOutdated` counts the installed
75
+
HyperFrames skills that are behind this CLI's release, and `skillsMissing` the
76
+
core skills that are not installed, from the same background check; both are
77
+
absent until that check has run for this version, once it is more than a day old
78
+
(as when `HYPERFRAMES_NO_UPDATE_CHECK=1` stops the checks), and under
79
+
`HYPERFRAMES_SKIP_SKILLS=1`. `--json` never makes a network request of its own.
80
+
Deprecated commands add `_meta.deprecated: true`.
81
+
82
+
`updateNotice` is one sentence for the agent to pass on to the person when the
83
+
CLI or the skills are behind: what is newer and the command that updates it.
84
+
The person decides whether to run it. The command moves the install that is
85
+
running:
86
+
87
+
| Install | CLI behind | Skills behind too, or only them |
88
+
| --- | --- | --- |
89
+
| npm, pnpm, bun or Homebrew global | the manager's command (`npm install -g [email protected]`, `brew upgrade hyperframes`, …) |`hyperframes update` (the global CLI's own; `npx hyperframes` would run a project's copy or a fresh one) |
90
+
| project `node_modules`| the project's manager, by lockfile: `npm install`, `pnpm add`, `bun add` or `yarn add [email protected]`| that, then `npx hyperframes update`; skills only: `npx hyperframes update`|
91
+
|`npx`|`npx hyperframes@latest update` (npx's cache may hold the old CLI) | the same; skills only: `npx hyperframes update`|
92
+
93
+
The skills half is left out when no skill is behind or under
94
+
`HYPERFRAMES_SKIP_SKILLS=1`. The notice appears at most once a day per project,
95
+
while the numeric fields stay on every result. It is never added under CI,
96
+
`HYPERFRAMES_NO_UPDATE_CHECK=1`, or an agent plugin (`HYPERFRAMES_PLUGIN_VERSION`),
97
+
and the output of `update`, `upgrade` and `skills` leaves it out.
71
98
72
99
A failure under `--json` always prints one JSON object on stdout, with a
73
100
machine-readable `code` and, when there is a next step, a `hint`:
@@ -127,7 +154,8 @@ notice; `HYPERFRAMES_NO_AUTO_INSTALL=1` turns off only the install.
127
154
**Skills notice.** When installed HyperFrames skills are out of date or missing,
128
155
a command ends with one line on stderr naming `npx hyperframes skills update`.
129
156
It shows at most once a day per project. In an unattended run it shows only when
130
-
a core skill is missing. `HYPERFRAMES_SKIP_SKILLS=1` turns it off. No notice
157
+
a core skill is missing; outdated skills reach agents as `_meta.skillsOutdated`
158
+
and `_meta.updateNotice` instead. `HYPERFRAMES_SKIP_SKILLS=1` turns it off. No notice
131
159
follows a usage error.
132
160
133
161
## Create a project
@@ -1976,6 +2004,7 @@ npx hyperframes doctor --json
1976
2004
hyperframes doctor
1977
2005
1978
2006
✓ Version 0.1.4 (latest)
2007
+
✓ CLI binary npm global install · /usr/local/lib/node_modules/hyperframes/dist/cli.js
1979
2008
✓ Node.js v22.x (linux x64)
1980
2009
✓ FFmpeg 7.x
1981
2010
✓ FFprobe 7.x
@@ -1986,7 +2015,9 @@ hyperframes doctor
1986
2015
◇ All checks passed
1987
2016
```
1988
2017
1989
-
It reports CLI version, Node.js, CPU, memory, disk, the extracted-frame cache,
2018
+
It reports CLI version, which binary is running and from where (a global npm,
2019
+
pnpm, bun or Homebrew install, a project's `node_modules`, `npx`, or an agent
2020
+
plugin) with its path, Node.js, CPU, memory, disk, the extracted-frame cache,
1990
2021
the archive extractor, `/dev/shm` on Linux, environment, whisper-cpp, local TTS
1991
2022
and BGM models, FFmpeg, FFprobe, Chrome, and Docker.
1992
2023
@@ -2037,6 +2068,64 @@ duration, element counts by type, track count, and total size.
2037
2068
`npx hyperframes compositions` lists every composition in the project with its
2038
2069
ID, duration, resolution, and element count. Both take `--json`.
2039
2070
2071
+
### `update`
2072
+
2073
+
```bash
2074
+
npx hyperframes update --check # report the CLI and the skills, install nothing
2075
+
npx hyperframes update --check --json # the same, for agents
2076
+
npx hyperframes update --yes # update both without prompting
2077
+
```
2078
+
2079
+
`update` asks npm for the latest CLI (past the two-hour cache) and checks the
2080
+
installed skills against the manifest at this CLI's release tag, in one call.
2081
+
`--check` only reports. Without it, `update` upgrades the CLI the way
2082
+
`upgrade --yes` does (an `npx` run gets `npx hyperframes@latest` to run instead,
2083
+
and a project-local run the project manager's command, such as
2084
+
`npm install [email protected]`) and then runs `skills update` at the release
2085
+
tag of the CLI that is now installed. Homebrew installs whatever its formula
2086
+
has, which can trail npm, so `update` reads the installed version back and
2087
+
reports `unchanged` when the formula has not moved. Without `--yes` or
2088
+
`--check`, an unattended run and any `--json` run exit 2, with the hint
2089
+
"Updating is the person's call; `update --check` only reports." Under an agent
2090
+
plugin, `update --check` reports, and `update` itself exits 1 with
2091
+
`plugin_managed`: the plugin manager updates it. `HYPERFRAMES_SKIP_SKILLS=1`
2092
+
leaves the skills alone. When npm does not answer, the human report says
2093
+
"npm registry not reached" instead of calling the CLI the latest.
npx hyperframes update --yes # upgrade the CLI, then refresh the skills
204
+
```
205
+
197
206
## Documentation
198
207
199
208
Full documentation: [hyperframes.heygen.com/packages/cli](https://hyperframes.heygen.com/packages/cli)
0 commit comments