Frontmatter
| id | 9760 |
| title | Resolve Undici HeadersTimeout in Session Summarization |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Apr 7, 2026, 6:19 PM |
| updatedAt | Apr 7, 2026, 6:20 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9760 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 7, 2026, 6:20 PM |
Resolve Undici HeadersTimeout in Session Summarization
Closedbugai
tobiu assigned to @tobiu on Apr 7, 2026, 6:19 PM

tobiu
Apr 7, 2026, 6:19 PM
Successfully replaced native node fetch bridging over to raw Node http interface. This allows us to strictly enforce the requested 1-hour generation timeout across Ollama without tripping over the undocumented undici headers timeout mechanism. Sandman queue processing will auto-retry and reliably synthesize remaining sessions on next daemon boot.
tobiu closed this issue on Apr 7, 2026, 6:20 PM
Node's native
fetch(via undici) enforces an undocumented 300,000ms (5-minute) timeout for the HTTPheadersTimeout. WhenSessionServicepushes massive 300k+ character prompts to a local Ollama instance duringautoSummarize, it spans beyond the 5-minute threshold before generating the first token, causingUND_ERR_HEADERS_TIMEOUTand skipping session consolidation.This ticket aims to refactor the local REST wrapper to bypass
fetchentirely and utilize Native Node.jshttp/httpspackages to gracefully enforce the requested 1-hour timeout threshold without arbitrary network drops.