Automations keep running when Vortex is closed

New

• An interval, daily, or one-time automation can run while Vortex is closed, through a macOS LaunchAgent. The Mac must be awake, the workspace must be local, and a cloud model and key must be set. Git and file-change triggers, and remote workspaces, still run only while Vortex is open. The automation stays pinned to the workspace you created it in.
• Automations are stored in vortex.db, shared by the app, vortex run --automation-id, and the agent. Ones you already saved move there once. Docs: Headless CLI.
• While nobody is watching, edits proceed and high-risk actions are denied: push, restore, delete, a browser override, a symlink that leaves the workspace, and a destructive command. The run cannot create another automation or change MCP settings. A question it cannot ask is answered with a stated default, and the run continues. If the model is rate-limited, the automation can try the next model you listed.
• An automation can remember a value, or an id it has already handled, and read it on the next run. The prompt can include {{handled_ids}}.
• A window you missed fires once when you are back. You can stamp that window without firing, and you can skip a run that would overlap one already going.

Fixed

• A failed fleet task now shows why it stopped on the Agents rail.
• A file or git trigger only watches the workspace it belongs to. If you are looking at another workspace, the row says it is waiting.
• Fleet lanes are git worktrees the remote server can create too, so a remote workspace can run an isolated lane.