Three user-reported failures in the assistant panel, one root cause each:
1. "The chat asks what I'm referring to" when continuing a thread. The
single-call console (general.help, AskConsole -> /api/agent/ask) was
stateless since the 08-20 model-agnostic cutover: conversationId was only
the tool actor id, so every turn was answered blind, reload or not.
The provider-agnostic GenerateTextRequest gains an optional `history`
(real message turns before the prompt, in both the Anthropic-family and
the OpenAI-compatible adapter; absent/empty leaves the request
byte-identical to the single-turn call). The route loads the thread's
earlier turns server-side (loadChatHistory: text only, hidden and tool
rows dropped, alternation repaired, newest 16 rows / 10k chars) before
writing the new question, and hands them to the model.
2. A full page reload (the deploy prompt's "Ladda om") closed the docked
panel and dropped the thread from view. The panel now remembers its open
thread per tab in sessionStorage (lib/agent-panel/session-restore) and
the provider reopens it on mount; the sheet loads it exactly like a pick
from "Tidigare konversationer". Close and "Ny konversation" forget it; a
thread that no longer opens is dropped instead of retried on every reload.
3. "Can't type any more" once the update banner shows. DeployReloadPrompt's
full-width wrapper sits at z-[60] after the panel in DOM order and
swallowed clicks on the panel's composer; only the card takes input now.
Claude-Session: https://claude.ai/code/session_01VjoXN3xdNZrHZeYA6qMi3g
Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
RIP-3 cutover. The free-form /chat panel (general.help) now answers through a
page-scoped single-call console (AskConsole → POST /api/agent/ask) instead of
the streaming Anthropic runtime, so the in-app assistant runs on ANY configured
backend, including a local OpenAI-compatible model (Qwen behind
llama.cpp/Ollama/vLLM). No tool loop, no NDJSON stream, no Anthropic wire format.
Threads still persist: the ask route gains an opt-in persist branch that writes
both turns to agent_conversations/agent_messages as canonical Anthropic text
blocks, so the /chat sidebar and "resume a thread" keep working across old
streaming threads and new single-call ones. Page-scoped one-off asks (a report
page) omit persist and stay stateless.
Scope: only general.help is wired to the console. The tool-loop intents
(transaction.categorization, invoice.draft, supplier_invoice.review) and the
docked AgentSheet still use AgentChat + run-turn.ts because they stage
operations and need the tool loop, so run-turn.ts is intentionally NOT deleted
here (the plan gates its deletion on "once nothing calls them"; RIP-4 migrates
the rest).
- lib/agent/ask/persist.ts: resolveChatConversation (create/resume, ownership),
persistUserTurn, persistAssistantTurn (append + roll last_message_* forward)
- app/api/agent/ask/route.ts: persist branch (resolve → user turn → answer →
assistant turn), returns conversation_id; 404 on a foreign conversation
- components/agent/AskConsole.tsx: the console UI (approved sign-off design):
user bubble + bare-prose answer, thinking indicator, empty/503/paywall states
- ChatConversationView / ChatNewStarter: branch general.help → AskConsole,
every other intent keeps AgentChat unchanged
Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
