@sjawhar/opencode-legion-envoy 2.0.5 → 2.2.0

package/dist/src/server.js

@@ -13902,6 +13902,13 @@ var commentValidation = {
   },
   message: `${commentOwner.message} turn requires reply_to_ask.`
 };
+var messageValidation = {
+  check: (value) => {
+    const input = value;
+    return typeof input.issue === "string" || typeof input.in_reply_to === "string";
+  },
+  message: "issue is required unless in_reply_to names a message delivered to this session, which is the one message with no issue."
+};
 var ISSUE_COMPONENTS_MODES = ["inherit", "explicit", "none"];
 function componentsArgument(z2) {
   return z2.object({
@@ -14119,12 +14126,13 @@ var dispatchToolSpecs = [
   {
     name: "dispatch_message",
     example: { issue: "DSP-1", body: "Implementation started." },
-    description: "Post a note humans must read now: a reply to a human's message, a deliverable that landed, or a blocker only " + "they can clear. Never progress or status updates - Dispatch is a high-signal record, not a log. Not a decision " + `(dispatch_ask) or document feedback (dispatch_comment). Body is at most 2,000 characters. ${ISSUE_REFERENCE}`,
+    description: "Post a note humans must read now: a reply to a human's message, a deliverable that landed, or a blocker only " + "they can clear. Never progress or status updates - Dispatch is a high-signal record, not a log. Not a decision " + "(dispatch_ask) or document feedback (dispatch_comment). To answer a human's direct message to this session - " + "one sent from the Agents page, which names no issue - pass that message's bare id as in_reply_to and no issue; " + "the reply lands in that conversation, and a second call with the same in_reply_to posts nothing because " + "Dispatch keeps the one reply per message. Every other message names its issue. " + `Body is at most 2,000 characters. ${ISSUE_REFERENCE}`,
     arguments: (z2) => ({
-      issue: z2.string().describe(ISSUE_REFERENCE),
+      issue: z2.string().describe(`${ISSUE_REFERENCE} Omit it only when in_reply_to answers a human's direct message to this session.`).optional(),
       body: z2.string({ max: 2000 }).describe("Update text, at most 2,000 characters."),
-      in_reply_to: z2.string().describe("Optional message id or dispatch://KEY/message/<id> reference to reply to, threading " + "this message under it so the reply stays with the original in the Conversation.").optional()
-    })
+      in_reply_to: z2.string().describe("Optional message id or dispatch://KEY/message/<id> reference to reply to, threading " + "this message under it so the reply stays with the original in the Conversation. " + "A bare id with no issue answers a human's direct message to this session; a " + "dispatch://KEY/message/<id> names the issue its message lives on, so that form is a " + "reply on that issue.").optional()
+    }),
+    validation: messageValidation
   },
   {
     name: "dispatch_doc_edit",
@@ -15171,6 +15179,9 @@ class DispatchClient {
   async message(issue2, input) {
     return this.#json("POST", ["api", "v1", "issues", await this.#resolveIssue(issue2), "messages"], input);
   }
+  async messageReply(id, input) {
+    return this.#json("POST", ["api", "v1", "messages", id, "reply"], input);
+  }
   async getMessage(issue2, id) {
     return this.#json("GET", [
       "api",
@@ -16019,6 +16030,10 @@ async function resolveOwnerArguments(tool, input, cwd, env, exec, serverUrl, pro
       owner: issue3 === undefined ? null : { kind: "issue", issue: issue3 }
     };
   }
+  const replyTarget = args.in_reply_to;
+  if (tool === "dispatch_message" && typeof replyTarget === "string" && !replyTarget.startsWith("dispatch://")) {
+    return { args, ref, owner: null };
+  }
   const legionIssue = env.LEGION_ISSUE;
   if (!legionIssue) {
     problems.push(ownerRequiredProblem);
@@ -16443,7 +16458,7 @@ async function executeDispatchTool(input) {
   const schema = toolSchema(input.tool);
   const parsed = schema.safeParse(ownerArguments.args, { reportInput: true });
   if (!parsed.success) {
-    const issues = parsed.error.issues.filter((issue3) => !ownerMissing || !(issue3.code === "invalid_type" && issue3.path.length === 1 && issue3.path[0] === "issue" && issue3.input === undefined || issue3.code === "custom" && issue3.path.length === 0 && issue3.message.startsWith("Exactly one of issue and project is required")));
+    const issues = parsed.error.issues.filter((issue3) => !ownerMissing || !(issue3.code === "invalid_type" && issue3.path.length === 1 && issue3.path[0] === "issue" && issue3.input === undefined || issue3.code === "custom" && issue3.path.length === 0 && (issue3.message.startsWith("Exactly one of issue and project is required") || issue3.message.startsWith("issue is required unless in_reply_to"))));
     problems.push(...formatZodIssues(issues, schema));
   }
   problems.push(...argumentProblems(input.tool, ownerArguments.args));
@@ -16873,9 +16888,23 @@ ${followsAsk(askOwner)}`,
     }
     case "dispatch_message": {
       const inReplyTo = messageInReplyTo(args);
+      const body = stringArg(args, "body");
+      if (owner === null && inReplyTo !== undefined) {
+        const reply = await client.messageReply(inReplyTo, { body, attempt: 1, actor });
+        if (reply.body !== body) {
+          return {
+            text: `Message ${inReplyTo} was already answered by message ${reply.id}; Dispatch kept ` + "that reply and posted nothing. Wait for their next message rather than answering " + "this one again.",
+            details: { message: reply.id, in_reply_to: inReplyTo, posted: false }
+          };
+        }
+        return {
+          text: `Replied to message ${inReplyTo} with message ${reply.id}`,
+          details: { message: reply.id, in_reply_to: inReplyTo, posted: true }
+        };
+      }
       const issueKey = issue2();
       const message = await client.message(issueKey, {
-        body: stringArg(args, "body"),
+        body,
         ...inReplyTo === undefined ? {} : { in_reply_to: inReplyTo },
         actor
       });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/opencode-legion-envoy",
-  "version": "2.0.5",
+  "version": "2.2.0",
   "type": "module",
   "main": "dist/src/server.js",
   "exports": {

package/skills/dispatch/SKILL.md

@@ -807,6 +807,31 @@ through Envoy or the hub. A bearer that targets over HTTP names its own session
 target only a session that advertises the mode you want. Sending to a session with no issue
 (`POST /api/v1/agents/{session_id}/messages`) stays human-only.
 
+### Answering a direct message
+
+A human can also message you directly from the **Agents** page, with no issue at all. That frame
+names no issue and its `reply_with` hint carries none either; answer it with the message's bare
+id in `in_reply_to`, alone:
+
+```ts
+dispatch_message({
+  in_reply_to: "<the direct message's id>",
+  body: "The requested answer.",
+})
+```
+
+Leave `issue` out — there is no issue to post into, and naming one would file your answer on
+unrelated work. Dispatch threads the reply under their message in the same conversation, and the
+human sees it on your agent card. Every other message still names its issue, so keep the `issue`
+the frame gave you whenever it gave you one; a `dispatch://KEY/message/<id>` reference names the
+issue its message lives on, so that form is a reply on that issue, not a direct message.
+
+One reply per message they send. A second call with the same `in_reply_to` posts nothing:
+Dispatch answers it with the reply already stored, and the tool result says the message was
+already answered rather than reporting a send. That happens most often when your host answered
+the **BTW** automatically before you got here — read the result before writing again, and wait
+for their next message instead.
+
 ## Following
 
 An ask has followers: every session that wrote to it — the session that opened it and every session that replied with