What would you like to be added?
Track followup work for the exported followup suggestion API in @qwen-code/webui.
The current PR fixes the core / CLI paths, but the exported WebUI surface still needs follow-up alignment before consumers start wiring this feature in.
Why is this needed?
@qwen-code/webui already exposes followup-related APIs and integration points, including:
useFollowupSuggestionsfollowupStateonAcceptFollowuponDismissFollowup
However, in the current repository state, this followup flow does not appear to be fully wired into an active consumer path yet (for example, VS Code companion is using InputForm, but not the followup suggestion flow).
Because of that, this is better tracked as follow-up work rather than blocking the current PR.
The exported WebUI API has started to expose Enter-path behavior that assumes skipOnAccept-style handling, but the underlying WebUI controller behavior is not fully aligned yet.
That means future consumers wiring useFollowupSuggestions() together with InputForm could hit inconsistent behavior unless the controller contract and implementation are finalized together.
Additional context
Suggested follow-up work:
- Align the exported WebUI followup API contract with the controller implementation
- Decide the intended Enter-accept behavior for WebUI consumers
- Wire the followup flow into the actual consumer(s) when ready
- Add regression tests covering Enter accept / submit / clear behavior
- Verify behavior in VS Code companion once the feature is actually connected
This is not considered a blocker for PR #2872 because there is no confirmed active consumer path in this repository relying on the unfinished WebUI followup flow yet.
What would you like to be added?
Track followup work for the exported followup suggestion API in
@qwen-code/webui.The current PR fixes the core / CLI paths, but the exported WebUI surface still needs follow-up alignment before consumers start wiring this feature in.
Why is this needed?
@qwen-code/webuialready exposes followup-related APIs and integration points, including:useFollowupSuggestionsfollowupStateonAcceptFollowuponDismissFollowupHowever, in the current repository state, this followup flow does not appear to be fully wired into an active consumer path yet (for example, VS Code companion is using
InputForm, but not the followup suggestion flow).Because of that, this is better tracked as follow-up work rather than blocking the current PR.
The exported WebUI API has started to expose Enter-path behavior that assumes
skipOnAccept-style handling, but the underlying WebUI controller behavior is not fully aligned yet.That means future consumers wiring
useFollowupSuggestions()together withInputFormcould hit inconsistent behavior unless the controller contract and implementation are finalized together.Additional context
Suggested follow-up work:
This is not considered a blocker for PR #2872 because there is no confirmed active consumer path in this repository relying on the unfinished WebUI followup flow yet.