Dashboardopencode-loreResponses ingress streaming and bounded…

Responses ingress streaming and bounded parsing boundary

Category: architecture
Confidence: 1.00
ID: 01a0a466-cb9b-7003-902f-35426664c8ff
Project ID: 6f4be9ff-ed84-4cca-a9e7-732a0b0b8677
Cross-project: No
Recalled in other projects: 1
Source session: 1dOKx83Yn1cacYtI1
Created: 2026-09-08 13:12:46
Updated: 2026-09-15 09:29:55

Cross-Project Recalls

ProjectHitsLast recalled
opencode 1 8d ago

Content

Chose incremental ingress parsing only for /v1/responses and /v1/codex/responses over universal streaming because only their shared item normalizer can consume input incrementally. Below 256 KiB, preserve exact JSON.parse; above it, replay once and stream $.input.* through createInputItemsBuilder(). This bounds Lore gateway parsing amplification, not upstream allocation: if OpenCode first constructs and serializes the full request body, downstream streaming cannot recover that memory. Audit OpenCode’s construction and serialization boundary before porting the builder.

Move to: