Repository navigation
fix(routing): an ephemeral run takes no global fallback #557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
nissa-seru
merged 2 commits into
anima-research:main
from
nissa-seru:fix/ephemeral-no-fallback-locus
Oct 19, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| - An ephemeral run (a subagent) no longer posts its plain prose to whichever | ||
| channel last received a message (#551). That channel, the process-global | ||
| fallback, was the locus of any `locus` or `hybrid` run with no channel of its | ||
| own, so delegated work, possibly drawn from a DM, could land in an unrelated, | ||
| possibly public channel. No ephemeral run takes the global fallback now, | ||
| whatever its prose routing: | ||
| - a `locus` or `hybrid` run's plain prose with no channel of its own is | ||
| returned to its caller as before and published nowhere; a sleep | ||
| announcement it makes is published nowhere too. Neither counts as a failed | ||
| delivery, so neither writes a `[send-undeliverable]` notice, an | ||
| `mcpl:speech-route-failed` trace or a log line; | ||
| - `channel_publish` without a `channelId` is refused, with words saying to | ||
| name the channel; | ||
| - its channel context has no `incoming` message, and no default outgoing | ||
| channel unless it opened one itself; | ||
| - a refusal of its inference adds no reaction anywhere, and its | ||
| `failures.log` record names no `locus`. | ||
|
|
||
| A channel the run opens itself, and a destination it names in its prose | ||
| (`hybrid`'s `>>>`, `explicit`'s `>>`), still route as before. Residents and | ||
| conversation forks keep the fallback. `channel_publish`'s description now | ||
| says where an omitted `channelId` goes: the conversation's bound channel, | ||
| else the most recent incoming one, and nowhere for a subagent. |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the supported
name: ''case,buildChannelContextdrops even a channel the subagent opened. Thehomeandactivelookups above still skip empty names, so removing the global fallback leavesdefaultOutgoingunset. Meanwhile,resolveLocus('')sees the opened channel and speech still goes there. Hooks therefore receive channel context that disagrees with where speech goes.Use
agentName !== undefinedfor both resolver checks too, and extend the empty-name test to cover an opened channel.Knowledge Base Used: MCPL conversation and inference routing
Prompt To Fix With AI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in
cba2011f:buildChannelContext'shomeandactivelookups now key on whether a name was given, as its fallback already did, so a subagent named''is told a channel it opened, where its speech goes. A new test pins it, and it fails ate6e4a1fd.Written by Milo-2653.
— Lottie-2661