Back to Changelog
v4.5.141
This release rolls up the Ops AI Desktop work that landed across 4.5.136-4.5.141 plus the matching backend 1.0.213 changes - new session controls, an explicit OAuth setup gate, and a stack of crash fixes.
New Features
2- Ops AI Desktop windows now expose one-click Continue Latest, plus inline controls for model (sonnet/opus/haiku/auto), thinking effort (low/medium/high/xhigh/max), and permission mode (default/plan/acceptEdits). Three slash command shortcuts (clear, compact, cost) in the running window header send the command straight to the Claude PTY.
- Six new per-session options accepted on the Claude WebSocket start frame: continue_latest, model, effort, permission_mode, fork_session, and session_name. ResumeSessionID still takes precedence over ContinueLatest so specific UUIDs win over newest-pick.
Improvements
2- First time you open a Claude expert on a freshly installed server, a clear Sign in to Claude Code setup card explains that Claude Code keeps its own authentication separate from your Panelica login. Clicking the card starts the OAuth flow; the panel no longer drops you into the auth provider picker by surprise.
- Backend 1.0.213 ships these changes server-side; frontend 4.5.141 ships them client-side. Both must be applied together for the new controls and gates to take effect.
Bug Fixes
4- Loading the Ops AI Desktop no longer crashes when an older saved layout in your browser localStorage references an app that has since been removed. Orphan window entries are filtered out during hydration.
- The status badge now knows about the new sign-in-needed phase. Earlier builds threw Cannot read properties of undefined (reading color) on first render because the badge map was missing an entry.
- Clicking Sign in to Claude Code no longer leaves you stuck on the Claude login started banner. The xterm terminal now mounts even when its container first appears after the OAuth setup card is dismissed.
- xterm no longer crashes with Cannot read properties of undefined (reading dimensions) when its host element is freshly inserted into the DOM. The terminal now waits for its container to settle before initialising and falls back gracefully if layout never reports a non-zero size.