Question 1

How to close the history search overlay that stays open above the chat composer?

Accepted Answer

Press the `Escape` key — it is currently the only way to close the "Search prompts and conversations…" overlay. Clicking the history (clock) button a second time only re-opens and resets the search, and clicking outside the overlay does nothing, because the component only listens for a window `keydown` event for `Escape` and has no close button or outside-click handler (tracked in issue #592). The planned fix makes the history button a toggle (click to open, click again to close), closes the overlay on pointer-down outside it, and adds an active state to the button while the overlay is open.

Question 2

How to fix 'Could not parse Anthropic SSE event: JSON Parse error: Unexpected EOF' error during streaming?

Accepted Answer

This is a known bug in the SSE parser of `@earendil-works/pi-ai` (present in 0.87.1). When the Anthropic stream is truncated between an `event:` line and its `data:` line, the parser wrongly dispatches the unfinished event instead of discarding it (per the WHATWG SSE spec). The resulting parse error text doesn't match `RETRYABLE_PROVIDER_ERROR_PATTERN`, so the turn fails permanently instead of auto-retrying. Workaround: manually resend or nudge the agent to retry the failed turn. The same error can also occur on a complete, valid stream when a CRLF line ending is split across two chunks (e.g., through a proxy or gateway). Permanent fix is tracked upstream at https://github.com/earendil-works/pi/issues/10390 — upgrade `@earendil-works/pi-ai` once a patched version is released.

Question 3

How to fix copy button showing through the history search overlay (z-index stacking issue)?

Accepted Answer

The message copy button uses `absolute z-10` (apps/web/src/chat/turns.tsx), while the history overlay has no z-index, so the button stacks above it. Two fixes: 1) Give the overlay or its wrapper in `ChatView.tsx` a higher z-index, e.g. add `z-20` to the overlay container (`HistoryOverlay.tsx`). 2) Broader fix: add the Tailwind `isolate` class to the transcript scroller to create a new stacking context, so no z-index inside the transcript (sticky breadcrumbs, tool cards, copy buttons) can escape above the composer/overlay area. To prevent regression, add an e2e assertion using `document.elementFromPoint()` at the corner of the search input to verify the overlay input, not the copy button, is the topmost element.

ThinkRail

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects