feat(channels): add QQ QR binding and group context - #160
Merged
Conversation
added 5 commits
August 4, 2026 20:02
Pandakingxbc
marked this pull request as ready for review
August 5, 2026 13:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
harness-gateway 0.9.1package and lock it from public PyPIWhy
QQ group conversations need enough recent context for the agent to understand referenced files and prior messages, while keeping the current message clearly identified as the message to answer. The visual controls avoid requiring operators to edit raw JSON, and QR onboarding removes the need to manually copy QQ bot credentials.
Group policy behavior
Auto: use the visibility authorized by QQMentions only: respond only to messages that mention the bot, with no historyMention + recent: include the configured recent-message window when the bot is mentionedAll messages: allow the bot to observe the full delivered group stream; operators can additionally choose whether every message activates the agentalwaysactivation is only retained withallvisibility)Dependency
The implementation uses the group-context and QQ QR-login APIs published in
harness-gateway 0.9.1. Bothpyproject.tomlanduv.lockresolve public releases; no sibling editable source is committed. The merged lock also resolvesorcakit-harness-agent 0.9.19from public PyPI.Verification
The repository gate completed successfully after merging the latest
develop:A fresh Python 3.12 environment was also synchronized with
uv sync --locked --no-sourcesat the dependency commit and verified against only the committed public lock:GitHub Actions run 31006534837 passed all required jobs:
The remaining Vite output consists of existing chunk-size and mixed dynamic/static import warnings; the build exits successfully. GitHub also emitted non-blocking action cache-service and Node.js runtime deprecation annotations.