Release notes
A rate limit waits in one row
A rate limit shows as one countdown, and Vortex keeps trying for ten minutes before it pauses the run. A foreground command that outlives its block window stays in the transcript. A session that needs attention stays ahead of idle history.
New
- A rate limit, or a provider that is down, collapses into one live countdown. Vortex follows the provider's reset hint when it sends one, and otherwise waits longer between tries, up to a minute apart. It keeps probing for ten minutes, then pauses the run so the turn is not held open. Docs: Models and keys.
Fixed
- A foreground command that passed the block window disappeared from the live narrative while it was still running. It stays until it finishes, including on a remote host. Stopping the run stops that command too.
- A command card saved as unknown could stay that way after the job had actually finished. The next status from the owner repairs it. A job the owner cannot find is the only one marked unknown.
- The terminal could go blank after its pane was hidden. It redraws when the pane is shown again.
- A background run that needs you could look idle, and an idle chat could sort above one that still needs attention. The sidebar dot, the sort order, and the mind map share one answer. A session that needs attention stays ahead of idle history without taking focus.
- A question that arrived before its chat was loaded could be missed. That session is marked so you can find it.