Repository navigation
Skip vibration when a subagent stops - #7
Merged
Merged
Conversation
devxoul
force-pushed
the
skip-subagent-stop
branch
from
October 26, 2026 15:01
15872fb to
104f02a
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
In omo (senpi), the pi extension vibrated whenever a subagent finished, as well as when the main agent stopped. omo runs category subagents as RPC sessions, and those report a UI, so the
ctx.hasUIguard let them through.Changes
isSubagentSessionrecognizes omo subagents the same way omo does: shared-host children are opened withsessionKind: "worker", standalone RPC children carryOMO_SENPI_TASK_RPC_CHILD=1, and team members carrySENPI_TASK_MEMBERagent_endhandler skips vibration for those sessions