feat(whatsapp): upsert busy messages via steer#17155
Open
EvolvingSoftwareAgent wants to merge 5 commits into
Open
feat(whatsapp): upsert busy messages via steer#17155EvolvingSoftwareAgent wants to merge 5 commits into
EvolvingSoftwareAgent wants to merge 5 commits into
Conversation
8c416da to
ee46abc
Compare
64a0ef4 to
d8adf46
Compare
d8adf46 to
ae41ece
Compare
added 5 commits
June 2, 2026 19:02
ae41ece to
fa5b71c
Compare
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
Follow-up to #12116. This updates WhatsApp's busy-message path so messages sent while a WhatsApp-backed run is active can be steered into the running agent, while preserving the soft-session context introduced by #16953.
/sessionssoft-thread routing so busy follow-ups land in the correct Hermes session.upsert_steer,reply_aware_steer, andexplicit_steerpolicies.running_agent.steer(...)with quoted-reply context preserved./steer passed to LLMprogress line at the actual delivery point.Why
#12116 added the core mid-run
/steer <prompt>primitive. WhatsApp needs the next layer: when a user replies or sends follow-up text while a session is busy, the gateway should be able to merge that context into the active run safely instead of treating it as a blunt interrupt or losing the reply/session association.The runner owns the upsert handler rather than the adapter to avoid adapter-recursive dispatch. If a real running agent exists, the handler calls
agent.steer(...); otherwise it returnsFalseso the normal message insertion/queue path can proceed.Current version
origin/main.d8adf4620eefee6626e80aa828fca0a1cc5312f6./sessionsUX plus the WhatsApp bridge diagnostics/slash-guidance fix from the local version.Test plan
git diff --check origin/main...HEADscripts/run_tests.sh tests/gateway/test_internal_event_bypass_pairing.py tests/gateway/test_platform_base.py tests/gateway/test_run_progress_topics.py tests/gateway/test_whatsapp_busy_steer.py tests/gateway/test_whatsapp_connect.py tests/gateway/test_whatsapp_sessions.py tests/gateway/test_whatsapp_group_gating.py tests/run_agent/test_steer.py -q— 246 passed, 1 warningFull suite not run locally.
Related
/steer <prompt>mid-run injection).Refresh status
main.ae41ecefa.mergeable: true;mergeable_state: unstablebecause GitHub checks are pending/absent, not because of conflicts.