gstack's browser skills work again in Codex and Cursor
2 days ago
gstack 1.99.1.0 and 1.99.2.0: browser skills, question preferences and Windows /review and /ship work again in Codex, Cursor and other hosts; brain sync catches secrets in UTF-16 and binary files; gstack-uninstall stops before deleting unsaved worktrees; /ship finishes after an owner's ruling; huge pull requests pass the sealed-output guard. Changelog 1.99.1.0: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#19910---2026-11-11 Changelog 1.99.2.0: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#19920---2026-11-12 Commits: https://github.com/garrytan/gstack/commits/main gstack: https://github.com/garrytan/gstack
Ask about this presentation
Chapters
Show transcriptHide transcript
If you run gstack from Codex or Cursor, its browser skills stopped with an error saying Playwright wasn't installed, even when it was. They now use the Playwright in your gstack checkout, so they start again.
Codex, Cursor and the other hosts had two more gaps. The question-preference helper couldn't find two of its own scripts. And on Windows, /review and /ship stopped before they started.
Brain sync used to skip files git calls binary, so an AWS key inside a UTF-16 note got pushed. It now reads those files, catches a key split across two lines, and decodes JSON escapes. A pre-commit hook from an older gstack needs refreshing.
Uninstall used to check only the top-level worktrees, so one nested inside another was deleted along with its edits. It now checks every checkout in every folder it removes, and checks again after you confirm.
When a fix-check finds a new critical issue, your ruling now lets /ship finish, with the finding listed as an open note in the pull request. A follow-up review that starts after a docs commit now counts too.
The sealed-output guard held a whole patch in memory, so a pull request with about 4 million lines of fixtures was always refused. It now reads one line at a time from a temporary file, which needs free disk space about the size of the patch.
If you run gstack from Codex or Cursor, I'd update today to get the browser skills back. On Claude Code, the secret scan alone makes it worth taking. The full notes are in the gstack changelog.
Up next
1:26gstack 1.99.4.0: /ship keeps its second-model review when OpenAI refuses it
@gstack
9 hours ago
0:57gstack 1.99.3.0: /ship stops refusing Next.js and SvelteKit route files
@gstack
1 day ago
3:18gstack 1.98.0.0 drops /investigate and /plan-eng-review, and new installs go stable
@gstack
1 week ago
3:11gstack 1.97.0.0’s browser stops trusting compromised certificates, and /investigate can demand a root cause
@gstack
1 week ago
3:12gstack’s /land-and-deploy now waits for you to type it, and /runaway-stopper catches runaway agents
@gstack
1 week ago
3:18gstack’s browser moves to Chromium 156, and /ship stops pushing merge conflicts
@gstack
1 week ago
3:21gstack’s new Claude Code hooks pick the right skill and check it finished
@gstack
1 week ago
1:37gstack’s /autoplan now runs a CEO review that asks you nothing
@gstack
1 week ago
1:59gstack now installs into Gemini CLI, and draws mockups with Gemini
@gstack
1 week ago
2:43gstack merge trains now land pull requests in any repo
@gstack
1 week ago
1:37gstack’s /ship stops re-reviewing your whole diff on every pass
@gstack
2 weeks ago
1:56gstack now auto-runs only four skills, so it stops colliding with other skill packs
@gstack
2 weeks ago






