Repository navigation
HTTP transport: move to streaming (SSE / Streamable HTTP) for server-initiated notifications #227
Description
Sub-issue of #222 (see docs/progressive-tool-scoping-design.md §6.4).
#223's additive HTTP transport is a synchronous tiny_http POST-request/JSON-response model — it can't push a notifications/tools/list_changed (or any other server-initiated notification) between requests. Replacing or augmenting it with SSE or MCP's Streamable HTTP is needed for the scope-increase flow (#226) to push notifications over HTTP the way it can over stdio's persistent pipe.
Can ship independently of #226 — HTTP callers can poll tools/list after request_increase without this; only the push notification needs it.
Activity
feat(pm-hooks): ProjectEventBus general event hook system + register_…
elasticdotventures commentedon Oct 11, 2026
PR #264 is open and MERGEABLE — awaiting operator review+merge.
elasticdotventures commentedon Oct 11, 2026
Resolved in PR #264 (task/227-sse-streamable-http) — axum/SSE Streamable HTTP transport, PM task hooks (TaskCreate/TaskDone/TaskUpdate fire ProjectEvent on bus), tool_called event on every dispatch. MERGEABLE.
feat(http-transport): replace tiny_http with axum/SSE Streamable HTTP (…