Skip to main content
Vortex
The loop How it works Control Docs Compare Changelog
Join the waitlist
The loop How it works Control Docs Compare Changelog Join the waitlist
  1. Home
  2. Changelog
  3. 0.2.0-beta.110

Release notes

The agent can record a demo of the browser

0.2.0-beta.110 · October 1, 2026

Ask the agent to demonstrate something in the embedded browser and it records the pane to a private clip, marks the moments worth keeping, and links the result in chat. A control inside a cross-origin iframe can be clicked and typed into. A follow-up question is no longer held back until you press Stop, each chat remembers its own model, and a finished plan shows the review dot.

New

  • The agent can record the embedded browser pane to a private local video with the new record_browser_video tool (macOS 12.3 and later). Starting a recording asks for its own consent and names the reason; an ordinary browser or tool approval never stands in for it. start, stop, status, mark, and trim are separate actions: a take can run up to 30 minutes, mark records a labelled moment in the clip's own timeline, and trim cuts a finished clip down to the spans you keep and publishes a new clip that links its source, leaving the original untouched. A clip is never uploaded, never recorded headless, and never written to an SSH host.
  • A recordings sheet in the browser pane lists every clip for the workspace with a poster frame, duration, size, creation time, markers, and how it was edited, with a search filter. The selected clip plays and seeks, can be saved wherever you choose, and can be deleted. The toolbar button carries a count instead of an empty disclosure.
  • The finished clip is linked in chat as a vortex-video:// chip, and the agent is instructed to always link it. Opening the chip brings up the sheet on that clip. A start row stays compact and offers "Watch recording" rather than mounting a second player beside the stop row's card.
  • browser_action can now reach a control inside a cross-origin iframe, which no ref or selector can address: take a screenshot, then pass its screenshotId with x/y to click or hover there, or focused with type/press to send to whatever the page has focused. That delivers a real OS-level event, so it is blind — the result reports where the event was delivered, never what it hit — and it always needs its own approval. A screenshot stops being addressable after two minutes, and a page that has moved since the screenshot is refused rather than clicked blind.

Fixed

  • A follow-up question or approval request is no longer held back until you press Stop. A request that names the chat you are looking at renders immediately, a run that has gone quiet is polled for pending requests, and a request whose run has already ended settles into "the run ended before this was answered" with no input — so it stops blocking the session and stops offering a Send that could only fail.
  • Each chat remembers its own model. Picking a model in the composer pins it to that chat and no longer moves the default for every other chat, Settings → Models sets the default for new chats, and a new "Set as default for new chats" action promotes a per-chat choice without re-finding it in Settings. The pin survives switching chats, parking a generating chat, and restarting the app.
  • A Plan-mode run that finished by handing back a plan shows the solid amber "Needs review" dot, matching the "Plan ready for review" notification it already sent. A run that is genuinely blocked keeps the pulsing dot.
  • Dropping an image from Finder into the composer works in an SSH workspace. The path came from this Mac, so it is read from this Mac instead of being asked of the host, and a real failure now says why instead of a bare "Couldn't attach". A dropped folder is reported as unsupported rather than silently treated as a file, and the editor previews a dropped local image.
  • The empty strip under the browser toolbar is gone. The recording controls moved into the address bar as a fixed-height chip, so nothing is drawn while idle and the pane's bounds never change — which is what keeps a resize from revoking a recording mid-take.
Older release A finished plan is not a blocked session

All Vortex releases

Join the macOS closed beta

Access is invite-only while we test the macOS closed beta. Add your email and we will send an invite when a place opens.

Join the waitlist
Vortex

You describe the work. Vortex plans, edits, verifies, and ships inside your workspace. The editor, terminal, diffs, and browser are how you watch and steer — not where you are expected to write the solution.

Product

The loop How it works Control Models Get Vortex

Resources

Docs Compare Changelog Release feed FAQ Join the waitlist

Company

Privacy

© Vortex. Made in the EU. Hosted in the EU.

Privacy

Choose your cookies

Strictly necessary storage keeps the site working. Optional analytics stay off until you allow them. See our Privacy Policy.

Strictly necessary

Required for the site to work. Always on.

Always on

Google Analytics measures visits after you allow it.