Release notes
A stalled model recovers before it pauses
When a model stalls, Vortex works back from it before pausing. It lowers the reasoning effort, compacts, starts from a fresh summary, and asks for one next step. A path in chat opens the file that owns it.
Fixed
- A stuck reply — repeating text, a reasoning budget spent with no answer, an empty response, or the same short line while the run is not moving — is recovered in that order. Reasoning loops lower the effort first. The timeline names the cause and the step. The looping text is not kept. Repeated lines inside a code block are not treated as a loop. The run pauses only after that ladder makes no progress, and the next time the same cause appears it starts from the step that last helped. A configured fallback model is tried last.
vortex statsprints how often each recovery was tried and how often it got the run moving again. - A path in chat opens the file in the workspace root that owns it, including when the workspace has more than one root and when the files are on an SSH host. Backticks,
file://, and a leading./are ignored. If the lookup fails, the link still opens. - Deleting an agent removes it from the workspace row immediately. Switching workspaces keeps the list you just left instead of blanking it until disk is read.
- A status line from the previous run, such as "Creating plan…", does not carry into the next one. A command the run left running stays.
- The count on the working panel's Open button sits beside the magnifier, so that cell grows to fit it. A two-digit count no longer covers the icon or crowds the first tab. It is announced as a count of changes to review.