docs(specs): document tool.execute.after subagent behavior and propose bus delivery - #41305
docs(specs): document tool.execute.after subagent behavior and propose bus delivery#41305semanticRig wants to merge 1 commit into
Conversation
…ivery the hook already fires for subagents but the contract is undocumented and the payload shape is not versioned. this spec documents what exists, proposes a typed contract, and extends session-delivery with a bus variant so cross-session messaging can build on a stable interface. the reference implementation at semanticRig/cross-session-agent-messaging proves the mechanism works. the maildir transport stays external. the core change is making the hook contract explicit. see anomalyco#41304
github-actions
Bot
added
needs:title
needs:compliance
|
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: I found 2 potentially related PRs: 1. feat(opencode): session-to-session messaging — communicate between two running sessions This PR directly addresses cross-session messaging, which is closely related to the subagent messaging behavior being documented in PR #41305. 2. feat(opencode): coordinator-messaging — sibling/coordinator subagent communication This PR focuses on coordinator and sibling subagent communication, which overlaps with the subagent session messaging proposed in PR #41305. Both of these PRs appear to be addressing similar use cases around subagent and cross-session communication, though PR #41305 is primarily a documentation/spec PR that documents and versions existing behavior while proposing a new |
semanticRig
changed the title
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
github-actions
Bot
removed
the
needs:compliance
2 participants
Issue for this PR
See #41304
Type of change
What does this PR do?
One spec file at specs/subagent-messaging.md.
Documents that tool.execute.after fires for subagent sessions, proposes a typed hook contract, and suggests adding
busto the SessionDelivery types alongsidesteerandqueue.No code changes. The hook behavior already exists. The maildir transport (reference impl at semanticRig/cross-session-agent-messaging) stays external.
Related to the session messaging PRs #38944 and #38943.
How did you verify?
Tested on OpenCode 1.18.15 with a probe plugin confirming tool.execute.after fires for subagents. Reference implementation handles 10 parallel subagents. Spec change is docs-only, matches specs/project.md format.
Checklist