overlord-cli 5.13.0 → 5.15.0

package/bin/_cli/protocol.mjs

@@ -834,6 +834,33 @@ async function protocolDeliver(args) {
 // objective attachments
 // ---------------------------------------------------------------------------
 
+async function protocolAttachmentList(args) {
+  const flags = parseFlags(args);
+  const { sessionKey, ticketId } = resolveSessionFlags(flags);
+  if (!sessionKey) throw new Error('--session-key is required (or set SESSION_KEY)');
+  if (!ticketId) throw new Error('--ticket-id is required (or set TICKET_ID)');
+
+  const { platformUrl, bearerToken, localSecret, organizationId } = await resolveAuth();
+  const timeoutMs = resolveTimeout(flags);
+
+  const body = {
+    sessionKey,
+    ticketId,
+    ...(flags['objective-id'] ? { objectiveId: String(flags['objective-id']) } : {})
+  };
+
+  const data = await apiPost(
+    platformUrl,
+    bearerToken,
+    localSecret,
+    organizationId,
+    '/api/protocol/attachments/list',
+    body,
+    timeoutMs
+  );
+  console.log(JSON.stringify(data, null, 2));
+}
+
 async function protocolAttachmentPrepareUpload(args) {
   const flags = parseFlags(args);
   const { sessionKey, ticketId } = resolveSessionFlags(flags);
@@ -1365,6 +1392,7 @@ Subcommands:
   read-context              Read shared persistent context for this ticket
   write-context             Write shared persistent context for future sessions
   deliver                     Finish work, send artifacts, and move the ticket to review
+  attachment-list             List objective attachments visible to the current session
   attachment-prepare-upload   Get a signed upload URL for an objective attachment
   attachment-finalize-upload  Finalize an uploaded attachment row after storage upload
   attachment-download-url     Get a signed download URL for an existing attachment
@@ -1597,6 +1625,15 @@ create:
     Standalone create auto-discovers the project from the current working directory unless --personal is set.
     Follow-up create requires both --session-key and --ticket-id.
 
+attachment-list:
+  Required:
+    --session-key <key>
+    --ticket-id <id>
+  Optional:
+    --objective-id <id>       Filter to a single objective
+  Returns:
+    JSON array of { id, label, content_type, file_size, objective_id, storage_path, created_at }
+
 attachment-prepare-upload:
   Required:
     --session-key <key>
@@ -1661,6 +1698,7 @@ Examples:
   ovld protocol ask --session-key <key> --ticket-id <id> --question-file ./question.txt
   ovld protocol read-context --session-key <key> --ticket-id <id> --query arch --limit 5
   ovld protocol write-context --session-key <key> --ticket-id <id> --key "arch" --value '"monorepo"' --tags repo,agent
+  ovld protocol attachment-list --session-key <key> --ticket-id <id>
   ovld protocol attachment-prepare-upload --session-key <key> --ticket-id <id> --objective-id <objective-id> --file-name spec.pdf --content-type application/pdf
   ovld protocol attachment-upload-file --session-key <key> --ticket-id <id> --objective-id <objective-id> --file ./spec.pdf
   ovld protocol attachment-download-url --session-key <key> --ticket-id <id> --attachment-id <attachment-id>
@@ -1706,6 +1744,10 @@ Examples:
     await protocolPrompt(args);
     return;
   }
+  if (subcommand === 'attachment-list') {
+    await protocolAttachmentList(args);
+    return;
+  }
   if (subcommand === 'attachment-prepare-upload') {
     await protocolAttachmentPrepareUpload(args);
     return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord-cli",
-  "version": "5.13.0",
+  "version": "5.15.0",
   "description": "Overlord CLI — launch AI agents on tickets from anywhere",
   "type": "module",
   "bin": {

package/plugins/claude/skills/overlord-ticket/SKILL.md

@@ -141,10 +141,13 @@ When in doubt, ask yourself: *can this be done entirely inside a terminal or bro
 ```bash
 ovld protocol read-context --session-key <sessionKey> --ticket-id $TICKET_ID
 ovld protocol write-context --session-key <sessionKey> --ticket-id $TICKET_ID --key "key" --value '"json-value"'
+ovld protocol attachment-list --session-key <sessionKey> --ticket-id $TICKET_ID
 ovld protocol attachment-upload-file --session-key <sessionKey> --ticket-id $TICKET_ID --objective-id <objective-id> --file ./spec.pdf --content-type application/pdf
 ovld protocol attachment-download-url --session-key <sessionKey> --ticket-id $TICKET_ID --attachment-id <attachment-id>
 ```
 
+The `attach` and `load-context` responses already include `attachments` and `objectives` arrays — use those for `<attachment-id>` and `<objective-id>` values. Run `attachment-list` mid-session if new files have been uploaded since attach.
+
 ## Rules
 
 - Always attach first and always deliver last once you are on a ticket.

package/plugins/overlord/README.md

@@ -25,7 +25,7 @@ personal marketplace entry at `~/.agents/plugins/marketplace.json`.
 - Ticket session flow: `attach_ticket`, `connect_ticket`, `load_ticket_context`, `spawn_ticket`
 - Progress and review flow: `post_update`, `record_change_rationales`, `ask_blocking_question`, `deliver_ticket`
 - Shared context: `read_shared_context`, `write_shared_context`
-- Objective attachments: `prepare_attachment_upload`, `finalize_attachment_upload`, `get_attachment_download_url`, `upload_attachment_file`
+- Objective attachments: `list_attachments`, `prepare_attachment_upload`, `finalize_attachment_upload`, `get_attachment_download_url`, `upload_attachment_file`
 
 The MCP server shells into the installed `ovld` binary so the plugin stays aligned with the shipped CLI behavior instead of depending on this repository checkout.
 

package/plugins/overlord/scripts/overlord-mcp.mjs

@@ -295,6 +295,26 @@ const tools = [
     }),
     subcommand: 'deliver'
   },
+  {
+    name: 'list_attachments',
+    description:
+      'List objective attachments visible to the current ticket session. Returns attachment IDs needed by get_attachment_download_url, plus their objective_id, label, content_type, file_size, and storage_path.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        session_key: { type: 'string' },
+        ticket_id: { type: 'string' },
+        objective_id: { type: 'string' }
+      },
+      required: ['session_key', 'ticket_id']
+    },
+    toCliFlags: args => ({
+      'session-key': args.session_key,
+      'ticket-id': args.ticket_id,
+      'objective-id': args.objective_id
+    }),
+    subcommand: 'attachment-list'
+  },
   {
     name: 'prepare_attachment_upload',
     description: 'Prepare an objective attachment upload and return a signed upload URL.',

package/plugins/overlord/skills/overlord-ticket/SKILL.md

@@ -102,10 +102,13 @@ Record only meaningful behavioral changes. Skip formatting-only noise. Prefer 1-
 ```bash
 ovld protocol read-context --session-key <sessionKey> --ticket-id $TICKET_ID
 ovld protocol write-context --session-key <sessionKey> --ticket-id $TICKET_ID --key "key" --value '"json-value"'
+ovld protocol attachment-list --session-key <sessionKey> --ticket-id $TICKET_ID
 ovld protocol attachment-upload-file --session-key <sessionKey> --ticket-id $TICKET_ID --objective-id <objective-id> --file ./spec.pdf --content-type application/pdf
 ovld protocol attachment-download-url --session-key <sessionKey> --ticket-id $TICKET_ID --attachment-id <attachment-id>
 ```
 
+The `attach` and `load-context` responses already include `attachments` and `objectives` arrays — use those for `<attachment-id>` and `<objective-id>` values. Run `attachment-list` mid-session if new files have been uploaded since attach.
+
 ## Project Discovery And Ticket Creation
 
 When creating tickets from within a repository: