@deepseek-ai/dsh-client-ui-qqbot

QQ bot connection toggle in the composer tool row. The browser half occupies the always-visible conversation.input.left seat (a small control inside the composer card's tool row, rendered for blank sessions too); each session gets a chip that executes /qqbot on (bind this session to the QQ gateway) or /qqbot off (disconnect), with the single bound session rendered as the active state.

Behavior

• The bound-session id lives in a shared bare observable registered through the inject face's hooks compartment, so every session reads the same value; switching sessions shows the truth rather than optimistic click state.
• The host command is owned by @deepseek-ai/dsh-qqbot; this package registers no host behavior — its node half is an intentional no-op.
• Admission failures (unknown command, transport error) surface as a title on the chip; the toggle stays usable.

Model Experience

Indirectly, through the /qqbot command; dsh-qqbot owns the command, the bound-session routing, and the channel prompt.

KV Cache effect

Prefix-stable — the toggle registers no prompt, schema, or result; the bound session's system prompt changes only through dsh-qqbot's channel section.

Known Limitations and Deferred Work

• Bound state is the last admitted command, not a live host read — the chip reflects the most recent successful /qqbot on / off; a host-side unbind that no client round-trip reported (for example, the bound session's disposal) is not reflected until the next toggle, which then rebinds correctly.