[Bug]: Provider streaming work (#2868, #2873, #2875) stranded on deleted dev branch — never reached master

[joehoyle]

Summary

Provider streaming for channel draft updates was implemented in March 2026 via PRs #2868, #2873, and #2875 (by @theonlyhennygod). All three were merged to an internal dev branch. The dev branch was subsequently deleted without ever being merged to master. The streaming code has never reached master or any release.

Issues #2721 and #2869 are closed as "completed" despite the code never landing.

Affected component

agent, provider, channel

Current behavior (master / v0.5.4)

run_tool_call_loop in src/agent/loop_.rs calls provider.chat() exclusively (non-streaming). Channels that support draft updates only receive:

• Progress messages ("🤔 Thinking...", "💬 Got N tool call(s)")
• Post-hoc chunked final text (split on whitespace after the full response arrives)

No real token-by-token streaming reaches channels.

What was implemented (and lost)

PR	Title	Merge commit	Base branch
#2868	fix(channel): consume provider streaming in tool loop drafts	52b9e6a	dev
#2873	feat(router): add streaming passthrough for routed providers	27c9f8a	dev
#2875	feat(streaming): add native tool-event streaming parity	88aef93	dev

The orphaned commits are still fetchable:

git fetch origin 52b9e6a2210df08dbccf08ff81907d6d93cf9254
git fetch origin 27c9f8a9fd9e3de147eeb58b2d3c309cc5cfc5de
git fetch origin 88aef9349c5285665d2cfb5872907299bb3b0c4e

Cherry-picking onto v0.5.4 produces 3 conflicts in src/agent/loop_.rs — the chat result handling and display text resolution have diverged.

Request

Please re-land the provider streaming work on master, either by resolving the cherry-pick conflicts or re-implementing based on the original PR designs.

Related

• [Bug]: channel draft streaming is post-hoc chunking; run_tool_call_loop does not consume provider streaming #2721 (original bug report — closed as completed)
• feat(streaming): full parity for routed/native-tool draft streaming #2869 (streaming parity tracker — closed as completed)
• fix(agent): relay tool-call text via on_delta #3266 (open PR — relay tool-call text via on_delta)

[NickRI]

Just want to add to the list.

• feat(http_request): add env-backed credential profiles and onboarding policy presets #2148
• fix(http_request): stabilize credential_profile env resolution #2570

[DenysVuika]

Same for this:

• feat(integrations): support lmstudio custom connector endpoint #2811

[joehoyle]

@theonlyhennygod could you clarify what the expectation was on all the PRs merged to main and dev?

[theonlyhennygod]

Hi @joehoyle — thank you for the detailed write-up and for tracking down the orphaned commits.

We want to confirm that we are no longer using main (or the old dev branch) — the project now uses master as the primary branch. Both main and dev have been retired.

We sincerely apologize that the provider streaming work from PRs #2868, #2873, and #2875 was lost in the branch transitions. This should not have happened, and we understand the frustration of having merged, working code never reach the release branch.

We see that PR #4175 (feat/reland-provider-streaming) has been opened to re-land this work against master. We'll review and prioritize getting that merged. If there are outstanding conflicts or issues with that PR, please let us know.

Thanks for your patience and for contributing this work in the first place.