Release v0.19.1 — queued machine sessions jump the line, Codex flag fix · jonwiggins/optio

Added

A queued session on a machine can jump the line. A session waiting for a free agent slot (the machine's "Agents at once" limit) now opens on a Queued panel with its place in line instead of a terminal stuck on "Connecting", and offers Move to front (the next to start when an agent finishes) and Start now (starts at once, past the limit) — on the web, iOS and Android, and as POST /api/local/terminals/:id/front and POST /api/local/terminals/:id/start with { "now": true }. Terminals carry queuePosition while queued.

Agents on your machine skip permission checks by default, the way agents in pods always have: Claude Code starts with --dangerously-skip-permissions and Codex with --yolo, whether a person, a trigger, or Ask Optio started the session. The work form's Permissions field (runs on a machine only) still opts into Auto (Claude's classifier; Codex's workspace-write sandbox, new) or Ask first / Codex's own settings.

Ask Optio turns in the API pod had no controller MCP tools ("the optio-controller MCP tools aren't loaded"): the .mcp.json named /opt/optio/controller-mcp.js, which only the agent images carried. The API image now bakes in the same MCP bridge bundle.
Ask Optio's list_repos returned nothing on a deployment with auth disabled: the assistant's session carries no workspace while every repo row does. A principal without a workspace now sees every repo, as GET /api/repos does.
Codex runs in pods passed --full-auto, which Codex 0.162+ rejects; pods now run codex exec --dangerously-bypass-approvals-and-sandbox. They also no longer hang on "Reading additional input from stdin".

A migration adds local_terminals.queue_priority (default 100).
Restart optio local up on each machine to pick up the new permission default; a daemon from the previous release keeps its old auto default until then.

helm upgrade --install optio oci://ghcr.io/jonwiggins/optio --version 0.19.1 -n optio --reuse-values