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.69

Release notes

Act on a pull request from the tab, and a plan checklist that ticks while it works

0.2.0-beta.69 · September 21, 2026

Merge, revert, close, reopen, mark ready, and convert to draft from the pull request tab, and Merge says why it cannot. Checks name what is required and what blocks the merge. A sequential plan build advances the checklist as it goes, instead of sitting at 0 of N until the last step. Another chat's run no longer narrates the one you are looking at.

Fixed

  • A sequential plan build only moved the checklist when the model called update_todos, and a busy model batched that into one final call. The Tasks card and the plan file both read 0 of N for the whole run.
  • Opening another chat could adopt that chat's live run, so the transcript showed the other chat's status and tasks.
  • The strip of agents in other chats also listed the chat you were already in.
  • A fan-out of child runs was headlined Running 3 tools. It now names the subagents, and the recap counts them per child — a best_of_n of three is three runs, not one call.
  • A run that started before its session was known was dropped. A later event could then write that run's plan into whichever chat was focused.
  • Merge disappeared with no explanation when the pull request was a draft or checks had not passed. The result of a merge, revert, close, or reopen lived only in a toast you could miss.
  • The Changes list is the remote pull request, and it looked like the local checkout. There was no way to filter by added, modified, deleted, or renamed.
  • Human reviews and the comment thread could render the same conversation twice.

New

  • Pull request actions: Merge, Revert, Mark ready, Convert to draft, Close, and Reopen, with a durable result row. Merge stays visible and says why it is blocked. Request reviewers by GitHub login. Docs: GitHub pull requests.
  • Checks open with a decision — merge blocked, still running, or passed — and badge required and merge-blocking runs. Refresh, Retry, and Details sit on the row.
  • Changes can be searched and filtered by status, and the header says the diff is this pull request, not the local checkout.
  • Commits can be searched, the SHA copied, and opened on GitHub, including the compare against the pull request's base.
  • The planning card shows this run's plan. Other plans in the workspace sit behind their own disclosure and are not read from disk until you open it. While a build is running, the checklist stays mounted if you scroll back through the turn. Docs: Plan files.
  • Settings model cards show a per-million price when the catalog has one (OpenRouter, models.dev, or the built-in list). A missing price stays blank. Docs: Models and keys.
  • An identical tool that keeps firing without changing the work is nudged, then stopped, and the stop names the unresolved verification when there is one.
Newer release Tabs you can click, and a checklist that stays on screen Older release List every plan in the workspace, and a review that can actually finish

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.