Version 1.1.14
2026-06-16Sharper memory recall, in-page reattach, role-model mapping
- Memory recall v2.2 — a cross-encoder reranker (bge-reranker-base) is now the precision gate on top of the cosine + BM25 + entity candidate pool. On real Onevium memory the old cosine path ranked unrelated same-project memories ABOVE the relevant one at 0.70+ similarity; the reranker pushes those down to ≤0.10. When the model is still warming up your chat falls back to the v2.1 path automatically — no first-message wait.
- In-page reattach to running turns — open any chat with a server-side turn still running and the reply continues inline, the input is locked while it streams, and the sidebar shows a per-session in-progress indicator so you can find it. No more 'background finished but the page is dead' state.
- Per-provider role-model mapping — custom Anthropic-compatible providers now expose an editable role → model table (opus / sonnet / haiku) in Settings → Providers. Useful for company gateways that default to a model you don't want; raw env_overrides still win, and built-in presets are unchanged.
- Long-task protocol split — the system prompt now distinguishes self-monitoring background work from foreground build / test commands, so a long build is no longer pushed into a `run_in_background` slot that will be reaped before it finishes.
- Workflow card persistence — inline sub-agent cards remember their expand state across stream → persistence handoff and across navigation, eliminating the auto-reexpand jump and the visible list shift when a workflow completes.
- Streaming polish — the backdrop-blur over streaming content is gone (was causing visible flicker in split chat columns), and sidebar session polls dedupe identical responses so the list no longer rerenders on each tick.
- Preview teardown — the `web-preview:get-view-for-session` IPC handler now tears down idempotently, fixing the 'Failed to Start' dialog seen on some Electron lifecycle races.
- Auto-continue surfaces simplified — the 'auto-armed waiting' inline row was a misfeature (users stopped typing to wait for it). Auto-armed fallback suspensions are now an invisible safety net; promised work still resumes itself, just without an interruptive UI affordance.