Engine room / A working outcome

The window closes.
The answer arrives.

I built a stored-result path into Claude Engine so a broken client stream can collect the completed turn.

An actual local execution, replayed here.

Recorded execution / interactive replay

One turn. Two views.

Replay the actual 14 October run. Controls move the recording; they make no live request.

The fictional task

Prepare the opening checklist for the Lantern Makers Club.

No tools · No private data

Start the replay, or jump to the moment the connection closed.

Browser client0 charactersReady

Engine & storage0 charactersReady

01 / Browser clientReady

The answer will begin here.

02 / Engine & RedisReady

Same engine process

Waiting for the task

0 answer characters

Stored result

Awaiting completion

—

Actual Claude subscription inference
Original route & result storage code
Isolated local Redis · delivery worker off

Recorded time0.00s11.50s to retrieval

23characters before disconnect

2,632characters recovered

202 200running, then completed

Same answertwo successful reads

Inspect the execution receipt Source, timestamps & boundaries

What ran

Claude Engine’s actual HTTP routes, invocation, client pool and bundled SDK CLI, with real Redis. The browser aborted its fetch stream. The engine detected the failed write and stored the final answer after the same turn completed.

Source revision: bf89abc1646bd12133a0f22bc2d51f3286813250
Captured: 14 October 2026 · 21:29 UTC
Runtime: Sonnet 5.5 · SDK 0.2.164 · Redis 7.0.15
Final answer SHA-256: a37db1de68db9f5d1375332b2e159c385d7c9ca6f05911fe4896ef42a6cb34d2

Download the redacted receipt

What the harness changed

Service setup was restricted to the local experiment. MCP connections, workflow shipping, background restore and notification delivery were disabled. The original outbox enqueue wrote its receipt locally, with no delivery worker.

A temporary configuration directory contained only subscription auth and this fictional session. The engine’s session index was redirected into it. The owned auth copy was removed after capture. Paid API keys were excluded from the environment.

The tested boundary

A client connection closed while the engine kept running. This run did not test a process restart, conversation migration, tool approvals or production client reconciliation. The exhibit replays recorded evidence; it does not make a live model request.

Watch the original execution

The connection
really closed.

A separate browser, the committed engine source and an isolated Redis instance. The screen freezes at 23 characters, while the engine finishes all 2,632. The result endpoint first returns 202, then returns the completed answer twice.

Controlled local capture · fictional content · 14 October 2026. No production service, notification recipient or unrelated session was involved.

A genuine continuous browser recording of the controlled run. The upper exhibit is a static replay of its recorded events. The engine process stays alive throughout.

Why the answer survives

Finishing the work is
only half the job.

The engine keeps collecting the turn after its client disconnects. Once the answer is complete, it stores the final text and ordered timeline in Redis. A result endpoint makes that completion available for later retrieval; idempotent reads let more than one client collect it.

Read the connected agents story

The window closes.The answer arrives.