Skip to content

docs(studio-app): add the Windows install steps - #6445

Merged
miguel-heygen merged 1 commit into
mainfrom
docs/studio-app-windows
Oct 26, 2026
Merged

miguel-heygen merged 1 commit into
mainfrom
docs/studio-app-windows

Conversation

@miguel-heygen

@miguel-heygen miguel-heygen commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

What changes for readers

The Studio app docs now say Windows is available. "Install the Studio app" has a Windows tab (download from hyperframes.dev/studio, run Install-HyperFrames.exe, the publisher reads HeyGen) and says Windows is 64-bit Intel and AMD only, with Windows on Arm not available yet. "Mac and Linux" becomes "Mac, Windows and Linux" in the Studio app intro, the FAQ, the quickstart (its description and its "In the Studio app" line, which said Windows was coming soon) and the three agent guides (Claude Code, Codex, Cursor). The FAQ's Windows answer no longer says the app is Mac and Linux only.

What I measured

  • The installer name and the Windows entry come from the live release feed: Install-HyperFrames.exe answers 200 with the same byte count as the feed's windows entry.
  • Nothing automated: the repo's oxfmt takes no .mdx files ("Expected at least one target file"), so formatting is unchecked beyond reading the diff.

What I did NOT exercise

  • I did not run the installer on a Windows computer, so the steps after "run it" are limited to what the release names: the file, and HeyGen as the publisher. They say nothing about prompts Windows may show.
  • The "Where your work is kept" section still names only the Mac and Linux settings folders; the Windows one is not stated here.
  • The Mintlify preview was not built.

Why under 100 lines

The change is wording across six docs files (about 30 changed lines) so the Windows launch is not contradicted by a page that still says Windows is coming soon; there is nothing to split.

@mintlify

mintlify Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
hyperframes 🟢 Ready View Preview Oct 26, 2026, 4:47 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@miguel-heygen
miguel-heygen merged commit d0c5477 into main Oct 26, 2026
62 of 63 checks passed
@miguel-heygen
miguel-heygen deleted the docs/studio-app-windows branch October 26, 2026 16:42

@heygengenesis heygengenesis Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: COMMENT (post-merge) · Ready with one follow-up · 0 blocker · 1 important · 0 nits · head aa4f2238

Post-merge advisory review (this PR is already merged into main as d0c5477). The finding below is a follow-up, not a merge gate.

  • important / should-be-follow-up: the PR missed the most-read page. docs/quickstart.mdx:29 still says "For Mac (Apple Silicon or Intel) and Linux; Windows is coming soon." docs/quickstart.mdx:3 (its description, used in search and link previews) still says "Studio app for Mac and Linux". Both are unchanged on main. A Windows reader who opens Quickstart is told the app isn't out yet, and one click later /studio-app and /faq say it is. Fix: use the same wording as studio-app/index.mdx, i.e. Mac, Windows (64-bit Intel and AMD) and Linux, plus the Windows on Arm caveat.
Scope

I read all 5 changed files in full. I grepped docs/ at the merge commit for "Mac and Linux", "Mac or Linux" and "Windows … coming soon". The only remaining hits are quickstart and dated changelog and weekly-update entries; those entries are historical and are correct as written. The new copy is consistent across all 5 files, and /studio-app resolves to the Windows tab added here. I did not run the installer or the Mintlify preview, and the PR body says it didn't either.

This branch was successfully deployed

1 active deployment
staging - docs — aa4f2238 Deployed Oct 26, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant