* fix(cli): copy only media, font, CSS and JS files from outside the project
Publish, cloud render and feedback now copy an outside reference into _ext/
only when its extension is an image, video, audio, font, CSS or JS type,
taken from studio-server's MIME map (new ./mime subpath; .avif added).
Anything else outside the project is left out with a warning and a
left_out entry whose reason is file_type; telemetry counts it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep the new outside-type file under its package's comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): copy the outside media cloud render re-encodes or converts
The outside allowlist now also takes the video, audio and still-image
extensions cloud render re-encodes or converts (.avi, .ogv, .aiff, .tif,
.bmp and the rest), from one shared list offload imports too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): cloud render --json lists the files an upload leaves out
`cloud render --dry-run --json` now reports `left_out`: each file outside the
project that the upload leaves out, with the file that points at it, the
reference as written, its path from the project, the reason (blocklisted or
received) and how many folders above the project it is. A wrapper can ask
before uploading. A full `--json` run carries the same list in its result and
prints a `{"event":"left_out"}` line on stderr for each, beside the warning a
person reads.
Publish, cloud render and feedback's repro send `cli_upload_left_out` when an
upload leaves something out: counts and folder depths only, never a name or
a path.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(cli): keep the left-out report's comment share at its package's
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): launch Chrome with only the env it needs
Every Chrome HyperFrames starts (render, GPU probe, HDR capture, startup
diagnosis, version and shell probes, CLI browsers, inspector) now gets an
allowlisted environment from @hyperframes/core/chrome-env instead of the
whole process env. HYPERFRAMES_CHROME_ENV_PASSTHROUGH names any extra
variable a host needs.
Refs #7623
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): keep the Chrome env passthrough across repeat filtering
The CLI GPU probe filters its env twice, which dropped the names
HYPERFRAMES_CHROME_ENV_PASSTHROUGH adds, so the probe and the render
saw different envs. Keep the passthrough variable itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): keep Chrome's sandbox on for local renders where the host supports it
Chrome launched with --no-sandbox on every host. Keep the sandbox on
macOS, Windows and non-root Linux outside containers; drop it as root,
in Docker/Podman/Kubernetes, on Lambda and Cloud Run, and where Linux
restricts unprivileged user namespaces. --no-zygote now ships only with
--no-sandbox, since Chrome refuses it while sandboxed. A sandboxed Linux
launch that fails at startup retries once without the sandbox and warns.
HYPERFRAMES_CHROME_SANDBOX=1|0 overrides the choice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(cli): cover the Linux sandbox retry in managed browser launches
The off-macOS closed-pipe case now passes --no-sandbox, so it still
pins "no seatbelt relaunch" rather than the new Linux sandbox retry,
which gets its own case.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): honor HYPERFRAMES_CHROME_SANDBOX=1 and latch the fallback on clear evidence only
With the override set to 1, a sandboxed launch Chrome refuses now fails
instead of retrying unsandboxed. A bare startup exit (TargetCloseError)
retries that launch without the sandbox but only latches the sandbox off
after a second one, so a single unrelated early kill no longer disables
it for the rest of a long-lived process. Chrome naming the sandbox in its
error still latches at once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer,docs): motion blur's compile hint and preview claim say what is measured
The screenshot-mode hint said data-motion-blur="on" always draws with html-in-canvas;
since auto took the filter tier it usually draws with an SVG filter. The guide said 16
preview copies stayed within measurement noise of 32; they stayed under the render
tests' visible-defect threshold, which is a weaker claim.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(motion-blur): 16 preview copies are under the smallest measured defect, not a test threshold
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs: every link to hyperframes.studio carries where the visit began, shared with the homepage
The visit's first source now lives in the homepage's 30-day hf_hub_landing
cookie (.heygen.com) instead of a per-tab sessionStorage key, so a visit that
moves between the homepage and the docs keeps it either way. Pricing,
changelog and community links carry it too; ph_id stays on downloads only.
Tags over 64 characters are left out, as hyperframes.studio drops them.
* docs: tag studio links when the context menu opens; cap saved tags on read
Open in new tab and Copy link take the href as the menu opens, so the source
goes on then (never ph_id). Saved campaign values get the same 64-character
cap as fresh ones.
* docs: a right-click no longer makes a Card's next click drop the source
The menu left the source on the Card's DOM href, so the next click found
nothing to add and returned before following the Card itself, which opens its
own untagged href prop. Compare against the address the link had before the
menu tagged it.
* chore: release v0.9.37
* docs(release): add #7576 to v0.9.37 notes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
0.9.35 made snapshotProject and snapshotFiles fall back to scratch-only
exclusions when .hyperframesignore can't be read. That is right for change
detection, but a host that builds an archive from the same snapshot then
includes files the ignore file meant to exclude, including ones named on its
valid lines.
The snapshot is strict again by default and throws invalid_source_ignore.
Change detection opts in with { lenientIgnore: true }, and projectFingerprint,
which names no files, always reads leniently.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(core): motion blur preview draws fewer filter copies at lower preview quality
The filter tier's preview draws 16 copies at preview quality 1/2 and 8 at 1/4 and
below; renders keep 32. Preview facts now list those levels in lighterAt once the
filter tier has movers, so a host that steps quality down on choppy playback can do
so for a film whose only load is blur.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(core): name the blur preview copies instead of commenting them
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore: release v0.9.35
* docs(release): note the render stop and container 403 from #7563 in v0.9.35
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix: track local Studio sharing CTA intent
* fix: tag local Studio and CLI share upgrade links with where they came from
The local Studio share modal's Upgrade to Pro link opens
/pricing?from=cli&entry=local_studio_share, and hyperframes share's source-files
notice links /pricing?from=cli&entry=cli_share, so the pricing page can tell
which link a visit came from and return the visitor to their terminal. The
modal accepts its own pricing page with any query, still only on
hyperframes.dev's two origins. share_upgrade_clicked carries
cta=share_modal_upgrade.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: name the local Studio upgrade CTA and drop the explaining comments
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the local Studio upgrade link's return page unchanged
Only entry=local_studio_share is added to the local Studio share window's
Upgrade to Pro link. from=cli would have told these buyers to go back to their
terminal after checkout, but they return to a browser tab. hyperframes share's
link keeps from=cli, as the CLI's other upgrade links do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(share): keep change detection working with a gitignore-style .hyperframesignore
The project scan used by change detection now reads .hyperframesignore
through the strict source reader. Cloud render reads the same file as
gitignore syntax and its docs show /exports/, which the strict reader
refuses, so the scan threw and hosts lost change detection, export
freshness and share status for that project.
Change detection now falls back to scratch-only exclusions when the file
cannot be read. Source capture keeps the strict reader and still refuses it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(share): check snapshotFiles tracks the file, not just names it
snapshotFiles returns every requested path, keying an excluded one as
undefined, so key presence alone did not prove the file was tracked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Local Studio mode runs Vite in the resolved @hyperframes/studio folder, so the
project folder decided which config and binary ran. Use it only when the
project resolves to the same Studio the CLI itself resolves (a source checkout
running its own build) or when HYPERFRAMES_LOCAL_STUDIO=1 is set; otherwise
serve the embedded Studio.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): share rendered videos through unified reviews (#7135)
* feat(share): attach editable project sources to reviews (#7137)
* feat(share): measure local sharing outcomes (#7138)
* feat(cli): stage the sixty-day publish transition (#7136)
* feat(studio): share review pages from local preview (#7140)
Advertise the CLI sharing bridge before bootstrapping it so standalone Studio does not
request unsupported routes. Preserve origin and session checks.
Budget the intended sharing artifact: clean main packs at 8,060,519 bytes versus
8,162,979 with sharing (8,169,168 in CI). Required policy and Unicode tables, bundled
sharing code, and Studio controls account for the growth. Set the packed-only budget
to 8,577,627, following the 5% headroom convention; retain the unpacked cap and all
package checks.
* fix(share): persist refusals and improve CLI retry feedback
* fix(ci): restore render diagnostics and include sharing workspace
* fix(cli): keep sharing owner error codes stable
* fix(share): clarify update feedback and align audience changes
* fix(share): clarify updates and avoid scratch-file rerenders
* fix(cli): report active shares and preserve update channels
* fix(cli): resolve update channel when checking registry
* fix(ci): refresh sharing package budgets after rebase
* fix(share): require consent before uploading project files
* docs(variables): say what can be a variable, including a video or sound per account
* docs(variables): render the per-account example from index.html and keep the outline
* feat(engine): decouple transparent background from png capture format
PNG capture used to imply a cleared page background. A new
CaptureOptions.transparentBackground lets lossless opaque PNG capture
(4:4:4 MP4 output) keep the page background. Absent, it still follows
format === "png", so alpha output and motion blur are unchanged.
Opaque PNG skips drawElement, whose verification and worker-encode
paths are JPEG-only.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(engine): add 4:4:4 chroma option to getEncoderPreset
getEncoderPreset takes an optional chromaSubsampling ("420" by
default). "444" returns yuv444p for SDR MP4, so libx264 encodes the
High 4:4:4 Predictive profile and odd sizes need no even padding.
WebM, MOV and HDR presets ignore it. The ChromaSubsampling type is
exported for the producer.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer): chromaSubsampling render option with lossless png capture
RenderConfig.chromaSubsampling ("420" by default) opts an SDR MP4
render into 4:4:4. "444" encodes libx264 yuv444p and captures every
frame as opaque PNG: Chrome's quality-100 JPEG is already 4:2:0 on
beginFrame and screenshot capture, and drawElement can fall back to
screenshot mid-render, so PNG is the only capture that keeps the
colour. drawElement is turned off for these renders.
The probe and main capture options share resolveCaptureSurface, so
they cannot disagree on format, quality or background.
Formats other than mp4, GPU encoding and HDR output are rejected
before any work starts, auto-detected HDR sources fail before capture,
and distributed requests refuse 444. The default render is unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(producer,studio-server): accept chromaSubsampling on render routes
The shared parseEncoderOptions validates chromaSubsampling and answers
400 for "444" with a non-mp4 format, gpu, or force-hdr, so a request
that would come back 4:2:0 never starts a render. The Studio render
route, both Studio adapters and the producer HTTP server forward it.
The producer server also refuses "444" with outputDynamicRange "hdr",
which parseEncoderOptions cannot see.
No Studio UI control; the option is route-level like crf and hdrMode.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): add --chroma-subsampling flag
`hyperframes render --chroma-subsampling 444` opts an SDR MP4 render
into full-resolution chroma (yuv444p with lossless PNG capture). The
default stays 420. The plan rejects 444 with a non-mp4 format, --gpu
or --hdr before anything renders, with a usage error that names the
conflicting flag.
The value reaches the local render request and, only when it is 444,
the Docker argv, so default Docker invocations are unchanged.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: document 4:4:4 chroma subsampling
Add a "4:4:4 masters" section to the rendering guide: when to use
--chroma-subsampling 444, why it captures PNG, the measured chroma gain
(large for text and UI, none for footage and gradients), its limits,
and a player compatibility table to be filled in from testing.
Document the flag in the CLI reference, the built-in rendering docs and
the hyperframes-cli skill reference (with the regenerated skills
manifest), and the chromaSubsampling option in the producer docs.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: add 4:4:4 player compatibility results
Fill the 4:4:4 compatibility table from testing H.264 High 4:4:4
Predictive output. Chrome 155, Edge 155, VLC 3.0, Safari on iOS 26.6
and Safari 26.6 on macOS play it, and so does AVFoundation on macOS
26.6, the framework QuickTime Player plays through. Firefox 157 on
Windows and both Windows media players do not.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: note the measured render cost of 4:4:4 output
Replace the vague "slower capture" note with measured numbers: a text
and UI composition rendered in about twice the default time, full-frame
footage in about three and a half times, because PNG encoding cost grows
with image detail.
Refs #5555
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(producer): reject chromaSubsampling 444 in distributed render config
Distributed configs have no chroma field and validateDistributedRenderConfig
ignored unknown keys, so a JS caller passing chromaSubsampling: "444" to the
Lambda or Cloud Run SDK got a 4:2:0 file with no error. Reject it, and make
the rendering guide say so precisely.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render reaches the encoder as yuv444p
Every helper had tests, but nothing checked the orchestrator passes
chromaSubsampling through, so dropping it from the encoder preset or capture
surface would turn 444 renders back into 4:2:0 with all tests green. Render a
small fixture with "444" and with the default and check pix_fmt with ffprobe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(producer): move the 444 drawElement gate into a helper
Keeps runCompileStage under the fallow complexity threshold.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep comment share at or below the merge-base
comment-ratchet failed on 11 files this PR touched. Keep the 4:4:4
rationale once in chromaSubsampling.ts, move the distributed-render
reason into its error message, and cut the rest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(producer): check a 444 render captures full-resolution chroma
The encoder check alone passes when chromaSubsampling is dropped from the
capture surface: frames are captured as JPEG and encoded yuv444p with
4:2:0 colour. Put a red/blue edge at an odd x, inside a 4:2:0 chroma
pair, and require the two pixels to differ in Cb.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): trim the chromaSubsampling.ts header to the package comment share
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: finish switching to capturesAlpha from #6262
The merge that adopted main's transparent / capturesAlpha left these files
uncommitted, so resolveCaptureSurface still returned transparentBackground.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(engine): use transparent / capturesAlpha from #6262
main added CaptureOptions.transparent and capturesAlpha (#6262), which do
what this PR's transparentBackground did. Use them, keep the PNG check in
drawElementWorkerEncodeEligible, and re-pin test-classification.mjs and
the skills manifest against current main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(producer): cut the 4:4:4 comment blocks to one to three lines
The reasoning lives in the PR description with the measurements.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: reconcile 4:4:4 chroma with latest main
Keep main's video-layer capture overrides, template entry resolution,
ProRes profile parsing and blur-differential tests alongside the chroma
option, and fold the encoder sub-parsers into one loop.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep main's compile-stage tests and regenerate the skills manifest
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(docs): escape catalog preview values and the install command's --vars argument
The catalog preview embeds variable values as JSON that cannot close a
script element or attribute, accepts value messages only from the page
that embeds it, and reads only declared ids with primitive values from
the link. The install command shell-quotes its --vars JSON and keeps
only variable-id keys with primitive values.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(core): fold CSS line endings before decoding escapes in the SVG sanitizer
A browser folds CR LF, CR and form feed into one newline before it reads
CSS escapes, so the whitespace after a hex escape can be a CR LF pair.
The sanitizer now does the same, so an escaped function name split by a
line ending is checked under its real name. The media-use bundle is
regenerated from the source.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(lint): match template ids and CSS rules in linear time
A getElementById template literal is matched against document ids with
an in-order indexOf scan instead of a regex of joined wildcards, so the
time no longer grows with the number of placeholders. The CSS rule
scanners only start a match at the beginning of a brace-free run, which
finds the same rules without rescanning long brace-less text. Lint
results on every HTML file in the repository are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(parsers): keep GSAP writer output inside its script element
String literals and quoted keys the GSAP writers emit now encode a
script closer or comment opener as \u003c, so a value can no longer end
the inline script that holds the timeline. Strings without those
sequences are written exactly as before. The writers also refuse a tween
method outside set, to, from and fromTo, and a motion path whose
coordinates or curviness are not numbers, since both are emitted as code.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(scripts): confine registry asset hosting to files inside the item
The asset hosting script now refuses a manifest path that leaves the
item directory or reaches its file through a symlink, before anything is
read, staged, uploaded or removed. A repository test fails when the
registry tracks a symlink or a manifest path that leaves its item.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(registry): pin the map blocks' d3 and atlas files to exact versions
The five map blocks load d3 7.9.2, the build the d3@7 range serves today,
with a subresource integrity hash, and fetch us-atlas 3.0.1 and
world-atlas 2.0.2, the files their ranges serve today. The bytes are
unchanged, so the blocks render the same. A repository test fails when a
registry item names an npm CDN package by range, tag or no version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(registry): pin map blocks to d3 7.9.0
7.9.0 has been the stable release since 2024; 7.9.1 and 7.9.2 were published days ago. Pin the
long-standing version, with its subresource integrity hash.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(registry): keep the map block PR source-only and formatted
Restore the generated catalog pages and payloads, which the catalog
publish job regenerates from the item sources. Name the us-atlas URL
in us-map-flow so the call fits on one line and formatting is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(scripts): check registry asset containment with one prefix test
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(lint): scan simple CSS rules in linear time
The two CSS-rule scans in the gsap rules took a body that could cross
'{', so a closed style of many '{' with no '}' rescanned to its end from
every brace. A scanner now returns the same selector and body pairs and
remembers the next '}', so each scan is linear. Findings are identical
on every tracked HTML file.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(core): label the form-feed sanitizer case as a guard
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(studio-server): reject cross-origin state-changing requests
Non-GET routes in createStudioApi answer 403 unless the shared
sameOriginPost predicate (lifted into studio-server's ./request-identity
subpath) accepts the request: the Host must be a server identity, a
present Sec-Fetch-Site must be same-origin, and a present Origin must
match the effective host and scheme. Hosts behind Codespaces or tunnels
allow their public name with HYPERFRAMES_PREVIEW_ALLOWED_HOSTS, read by
`hyperframes preview` and the Studio dev server.
Squashed from #6128 (42574a7, 110a300, 89011e1, 41c6626, 27193bb) onto
current main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): the preview server answers only the hosts it is reached by
Every route of `hyperframes preview` (the forwarded studio API, the SSE
stream, /__hyperframes_config and the Studio page) now answers only
loopback names, the HYPERFRAMES_PREVIEW_HOST bind, or a host listed in
HYPERFRAMES_PREVIEW_ALLOWED_HOSTS, the same list the write guard uses.
Only the Host header counts here, since a page can set X-Forwarded-Host
on its own requests and a read carries no Origin to compare it with.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Dextheking1 <Dextheking1@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs(studio-app): the Reference read is paid by Pro or a saved HeyGen API key
ReferenceAnalysis readGate: a saved usable key pays the read; without one
the plan gate opens the plans page (feature video_analysis). The page said
only the API key paid.
* docs(studio-app): a saved key comes first, and a used-up pro allowance opens plan and usage
* docs(studio-app): pro credits pay for the reference read first, a saved key when the plan can't
* docs(studio-app): cloud exports come with the plan, not only an api key
The export page said cloud renders are always paid per minute from a HeyGen API balance. The app
now includes 5 cloud exports a month on Free and unlimited on Pro (plans.ts, cloudFit.mjs).
* docs(studio-app): export destination and api-key billing wording
* docs(mcp): current ChatGPT setup steps, and the hosted render's real output
OpenAI moved custom MCP servers to Plugins > + > Add custom MCP server,
on Business, Enterprise and Edu only. The hosted render takes no format
or fps (render_video has a TODO to expose them), so the page no longer
suggests asking for 30 fps, WebM or MOV there.
* docs(mcp): connect from the claude directory, and name hyperframes in the first prompt
HyperFrames by HeyGen is listed in Claude's connector directory. In a Claude.ai test on 6 Nov
2026, a request without "Use HyperFrames" made Claude write its own video code instead of
calling the connector.
* docs(mcp): where to switch the connector on in a chat
* docs(changelog): weekly digest 2026-11-02-2026-11-09
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* docs(changelog): embed the Nov 2-9 weekly video
* docs(changelog): drop the 2k alias and name fixes as described above
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Follow-ups from review on #7443 and #7444:
- The quote hint returned the first run of words that existed, so a
"Final Cut/" folder hid "Final Cut export.mp4". It now names the longest.
- "--compare=my clip.mp4" got no hint; the value after = now starts a run.
- The telemetry section lists the skill a reverse or templates command ran
for, and the HeyGen session id a recorded reverse run carries.
* fix(core): detect template entries structurally
isTemplateEntry only matched a raw file that starts with <template>, so the
full-document sub-composition shape (<!doctype html><html><body><template>
<div data-composition-id>...</template></body></html>) was not recognised and
resolveEntryHtmlPath compiled the raw file, whose root sits in an inert
template: no timeline, no duration, "Composition has zero duration".
A template entry is now a document whose <template> holds the composition
root with no live composition root outside it. Detection and extraction share
one lookup (locateSceneRoot), the same one readSceneRoot uses.
— Jerrai
* fix(core): drop comments from the template lookup
The comment ratchet allows no net rise in a file's comment share; the PR
description carries the explanation.
— Jerrai
* fix(core): find the scene template among several templates
locateSceneRoot read only the first <template>, so a scene template that
follows another template was treated as not a template entry. Scan every
template and take the first whose content holds a composition root.
* fix(core): drop the added comment (comment ratchet)
* chore: raise the inspector unpacked size budget by 0.5%
The inspector bundles core; the multi-template scene lookup added a few
hundred bytes and put it 10 bytes over the 1% tolerance.
* fix(core): refuse a file with several scene templates, naming them
* chore: trim the inspector size budget bump to what is needed
* fix(core): render the first scene template and lint the ambiguity instead of failing
A file with several scene templates and no live root rendered its first one
before; locateSceneRoot threw and stopped such projects rendering. It returns
the first again, and the multiple_scene_templates lint warning names each.
Co-authored-by: Jerrai <jerrai@heygen.com>
* chore(core): drop the locateSceneRoot comment line the comment ratchet counts
Co-authored-by: Jerrai <jerrai@heygen.com>
* fix(core): one shared scene-template pick for the compiler, the inliner and the loader
A scene template after a card template was detected by locateSceneRoot but
mounted from the first template of any kind, so it rendered blank.
findSceneTemplate picks the first template holding a composition root and
locateSceneRoot, resolveSubCompositionContent and the loader all use it.
Co-authored-by: Jerrai <jerrai@heygen.com>
* feat(cli): reverse and templates report their own runs; commands say which skills are installed
Gaps in what skill telemetry can answer for /reverse-any-video and
/style-sampling:
- The skill's beacon fires only when the agent runs it, and agents often
skip it. `reverse start` and `templates pull` now send `skill_invoked`
with `source: command`; beacons carry `source: beacon`. A person counts
once.
- style-sampling renders were never tagged. A pull marks the project the
episode is built in (only a folder that is already a project).
- Installs of an on-demand skill were invisible. `cli_command` carries
`skills_installed` and `skills_outdated`, the names from the cached
background skills check, so "never triggered" and "not installed" can
be told apart.
- `auth status` signed out exits 1 with a bare "Command failed", which
reads like a login failure. It now carries `NotSignedIn`, and an auth
error its own cause.
And a step that gets lost: a reverse started signed out often goes on
without ever trying to sign in. `reverse start` signed out now prints
`login_command` and a `next` line in the JSON the agent reads, not only
in the skill's reference.
* refactor(cli): keep comment share at the base in the reverse telemetry files
* fix(cli): command runs get their own event, counted once per piece of work
Review on the first cut: `skill_invoked` from the commands doubled the
#7176 beacon's single observation, and it fired before any work.
- `reverse start` and `templates pull` send `skill_command_ran`, not
`skill_invoked`; the beacon is back to its #7176 shape.
- `reverse start` sends it after the probe, with `signed_in` and the
reverse `session_id` that keys a retry; a video it cannot probe sends
nothing.
- `templates pull` sends it only when it downloads; a re-pull or a
refused pull sends nothing.
- A skills check that finds no install forgets the installed names.
- `auth status` failures carry only a code, never the auth error's text.
* feat(skills): reverse-any-video and style-sampling install with the core set
A skill only triggers when it is installed. On demand these two rarely
were, so a request to copy a video or make an episode in a proven style
seldom reached them, and the entry skill named only one of them, in its
closing line.
- isCoreSkill, FALLBACK_CORE_SKILLS and the marketplace `core-skills`
entry include both, so `init` and `skills update` install them. The
`hyperframes` plugin already bundled every skill.
- `/hyperframes` routes to both from the top of its table: a video to
copy or remake, and an episode in a proven style. Its budget takes
+64 B for those two rows.
- `/reverse-any-video` triggers on "remake" and on 「复刻这个视频」
「照着做一个」, inside the 320 B description cap.
- Every catalog surface lists both in the core group: CLAUDE.md,
AGENTS.md, README, the skills guide, skill-lifecycle and the two init
templates (still byte-identical).
* refactor(cli): keep comment share at the base in skillsManifest