Today the webhook trigger is request/response: POST an input, get the full run result back when the run finishes. Add a streaming variant of the trigger endpoint so callers can receive output as the run progresses (e.g. SSE or chunked responses), which longer runs and interactive UIs need.
Open questions:
- Protocol: SSE vs chunked JSON lines vs WebSocket
- What streams: tokens, tool events, or both
- How auth and
conversation_id carry over from the existing webhook trigger
🤖 Generated with Claude Code
Today the webhook trigger is request/response: POST an input, get the full run result back when the run finishes. Add a streaming variant of the trigger endpoint so callers can receive output as the run progresses (e.g. SSE or chunked responses), which longer runs and interactive UIs need.
Open questions:
conversation_idcarry over from the existing webhook trigger🤖 Generated with Claude Code