David
Blumenau
Menu
Feature atlas
EngineRecover the answer after a disconnect

Close the window. Keep the result.

The problem

A browser or proxy connection can disappear while a long-running tool turn continues on the engine.

An explanatory exhibit

Two lifetimes, one completed turn

Local explanatory exhibit · invented records · no live service or agent call

Foreground / client lane

  1. Request starts
  2. Connection disappears
  3. Reconnect retrieve result

Background / engine lane

  1. Turn starts
  2. Tool completes
  3. Completion stored

Illustrated browser/SSE disconnect. The engine stays running; permission behavior depends on its configured disconnect policy.

Inspect the consequence

Foreground disconnects

Browser stream: disconnected

This example separates the client connection from the ongoing turn.

Client reconnects

Stored answer + ordered activity

Recovery retrieves a completion record. It does not establish engine process-restart survival.

What this makes possible

Engine-side result storage and PanelForge recovery let a client reconnect and retrieve an ordered turn timeline and completed response after a foreground stream breaks.

Source information sheet

Evidence, implementation & history Implementation inspected

What I checked

Source and release record inspected; no current product execution is claimed for this illustration. Scope: browser/SSE disconnect while the Claude Engine turn continues. This does not promise process-restart survival or equivalent behavior in every engine.

Release anchor: claude-engine v6.13.0; panel-forge web-v8.16.0.

Research cut: 14 October 2026. Source areas below are from claude-engine + panel-forge. Private conversation references are retained in the research ledger and are not published here.

Implementation decisions

Engine-side result storage and PanelForge recovery let a client reconnect and retrieve an ordered turn timeline and completed response after a foreground stream breaks.

Keep the foreground event stream separate from a retrievable completion record; restore from a cursor and reconcile ordered activity.

A path through the feature

  1. The consequence

    Keep the foreground event stream separate from a retrievable completion record; restore from a cursor and reconcile ordered activity.

Source areas

  • claude-engine/claude_engine/routes/stream.py
  • claude-engine/claude_engine/turn_timeline.py
  • panel-forge/resources/js/composables/useChatStreamRecovery.ts
  • panel-forge/app/Http/Controllers/Api/ClaudeEngineStreamController.php

The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.

Recorded history

Dates describe the researched record, rather than today’s deployment.

  1. claude-engine v6.13.0; panel-forge web-v8.16.0