@sjawhar/opencode-legion-envoy 1.31.0 → 1.31.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/dispatch/SKILL.md +4 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/opencode-legion-envoy",
3
- "version": "1.31.0",
3
+ "version": "1.31.1",
4
4
  "type": "module",
5
5
  "main": "dist/src/server.js",
6
6
  "exports": {
package/skills/dispatch/SKILL.md CHANGED
@@ -485,7 +485,10 @@ dispatch_message({
485
485
 
486
486
  `in_reply_to` correlates the answer under the asker's message in its Conversation card. A BTW
487
487
  delivery can post its answer automatically; use this call when the frame asks the primary agent to
488
- reply. `dispatch_message` itself never carries `target` or `delivery`: agent-to-agent traffic goes
488
+ reply. A human may reply to your message in turn — the follow-up arrives as a targeted frame whose
489
+ `in_reply_to` names your message and whose `reply_body` quotes it; answer it the same way,
490
+ `dispatch_message({ issue, in_reply_to: "<their reply id>", body })`, so the exchange reads as one
491
+ thread. `dispatch_message` itself never carries `target` or `delivery`: agent-to-agent traffic goes
489
492
  through Envoy or the hub. A bearer that targets over HTTP names its own session in `actor`
490
493
  (`{kind: "session", id}`), and the card shows that session as the author. `GET /api/v1/agents`
491
494
  (any authenticated caller) lists live sessions with their capabilities (`aside`, `btw`, `steer`);