ActionController::Live support #155

Activity

1. erickreutz

   added

   enhancementNew feature or requestNew feature or request

   on Oct 7, 2025
2. kevinjcoleman commented on Nov 10, 2025

   

   kevinjcoleman

   on Nov 10, 2025

   More actions

   Definitely interested in this @erickreutz did you ever dig in here?
3. koic commented on Apr 11, 2026

   

   koic

   on Apr 11, 2026

   Member

   More actions

   Thanks for the suggestion. Looking at the current architecture, I don't see a clear benefit to adding an ActionController::Live example:

   1. Controller pattern (new transport per request): Sessions cannot be shared across requests (Mcp-Session-Id is lost because @sessions is cleared when a new StreamableHTTPTransport is instantiated). Progress and Sampling all depend on session persistence, so ActionController::Live streaming doesn't help in this case.
   2. Mount pattern / shared transport (Make StreamableHTTPTransport a Rack application #263): StreamableHTTPTransport already sets Content-Type: text/event-stream and writes to the stream via Rack 3 Streaming Body. The SDK stores the stream in @sessions[session_id][:post_request_streams][request_id] so tools can write progress notifications and sampling requests during execution. ActionController::Live would be edundant here.
   3. Premise: The SDK already returns text/event-stream for session-based requests, so there's no gap that ActionController::Live would fill.

   If there's a specific use case I'm missing, please let me know. Otherwise, I'll close this issue. Thank you.
4. koic

   closed this as completedon Apr 11, 2026