gstack 1.81.0.0

1.81.0.0

Aside is the browser gstack drives first

Changed 5
  • Aside is now the first browser driver for all browsing skills, with gstack's headless browser as automatic fallback
  • Skills /qa, /qa-only, /design-review, /scrape, /benchmark, /canary, /browse, /devex-review, /land-and-deploy post-deploy check, and /design-consultation competitor research now run inside the Aside AI browser
  • PDF rendering, diagram rendering, and design-html viewport screenshots now render through Aside
  • Skills that previously used the WebSearch tool now use Aside's own read-only agent in your real browser
  • Browser renderer now picks Aside when running and falls back to bundled Chromium otherwise, and prints which one was used

From gstack

Aside is the browser gstack drives first. Every browsing skill, the PDF and diagram renderer, and web research go through it. gstack's own headless browser stays as the automatic fallback, so nothing stops working without Aside. Since v1.72 Aside was the recommended driver for third-party sites. This release makes it the first driver everywhere. /qa, /qa-only, /design-review, /scrape, /benchmark, /canary, /browse, /devex-review, /land-and-deploy's post-deploy check, and /design-consultation's competitor research now run inside the Aside AI browser (macOS 15+, aside.com), in the sessions you are already signed in to. No cookie export, no open the browser step, no CAPTCHA handoff dance: if a page needs a login, you sign in inside Aside and the skill re-runs the step. /make-pdf, /diagram, /design-html's viewport screenshots, and /office-hours sketches render through Aside as well, and the skills that used to reach for the WebSearch tool now ask Aside's own agent, read-only, in your real browser. When Aside is not there, nothing breaks. Every browsing skill carries a fallback section that translates its Aside steps onto gstack's own headless Chromium ($B), step for step: same evidence lines, same report, same consent rules, with cookie import or a handoff for authenticated pages. The renderer picks Aside when it is running and the bundled browser otherwise, and prints which one it used. Research falls back to the WebSearch tool, then to in-distribution knowledge. Linux and Windows users keep the bundled browser exactly as before; the Third-Party Web Actions contract keeps gstack's visible browser as its fallback driver.

View original

Upgraded? How did it go?

Discussion