Outstanding: Remove the 500-message REST history cap #28

New issue

Open

opened 2026-08-22 04:18:26 +00:00 by kayg · 0 comments

kayg commented

2026-08-22 04:18:26 +00:00

Owner

Current state

Outstanding backend/data limitation. The REST history endpoint returns at most 500 messages per session and has no pagination. Long conversations therefore have older messages that are absent from the local cache, so local search cannot find them.

Acceptance criteria

Add a pagination or equivalent complete-history retrieval contract to the Hermes REST integration.
Retrieve all pages deterministically without dropping or duplicating messages.
Preserve stable ordering and stable message identity across page boundaries.
Ensure the local cache and search index include messages older than the first 500.
Define and surface a precise error/partial-history state if a backend cannot provide more pages; do not silently claim the transcript is complete.

## Current state Outstanding backend/data limitation. The REST history endpoint returns at most 500 messages per session and has no pagination. Long conversations therefore have older messages that are absent from the local cache, so local search cannot find them. ## Acceptance criteria - Add a pagination or equivalent complete-history retrieval contract to the Hermes REST integration. - Retrieve all pages deterministically without dropping or duplicating messages. - Preserve stable ordering and stable message identity across page boundaries. - Ensure the local cache and search index include messages older than the first 500. - Define and surface a precise error/partial-history state if a backend cannot provide more pages; do not silently claim the transcript is complete.

kayg added the

outstanding

label

2026-08-22 04:18:30 +00:00

kayg referenced this issue

2026-08-22 12:55:20 +00:00

Decide whether local search indexes compaction-preserved rows #34

kayg referenced this issue

2026-08-22 18:27:02 +00:00

Tomorrow: sidebar, search, and Settings UI plan #42