overlord-cli 5.15.1 → 5.16.0

package/README.md

@@ -62,9 +62,9 @@ ovld prompt "Draft a fix for the onboarding flow"
 ovld version
 ovld update
 ovld protocol discover-project
-ovld protocol attach --ticket-id <ticket-id>
+ovld protocol attach --ticket-id <ticket_id>
 ovld protocol search-tickets --query "auth refactor" --status next-up,execute
-ovld protocol update --session-key <session-key> --ticket-id <ticket-id> --summary "Working on it" --phase execute
+ovld protocol update --session-key <session-key> --ticket-id <ticket_id> --summary "Working on it" --phase execute
 ovld setup
 ovld setup codex
 ovld setup claude

package/bin/_cli/launcher.mjs

@@ -169,12 +169,12 @@ function buildTmuxWrappedCommand(innerCommand, tmuxCommand) {
 
 function printLauncherHelp() {
   console.log(`Usage:
-  ovld launch <agent> --ticket-id <id> [options]
-  ovld connect <agent> --ticket-id <id> [options]   # alias for ovld launch
-  ovld restart <agent> --ticket-id <id> [options]
+  ovld launch <agent> --ticket-id <ticket_id> [options]
+  ovld connect <agent> --ticket-id <ticket_id> [options]   # alias for ovld launch
+  ovld restart <agent> --ticket-id <ticket_id> [options]
 
 Options:
-  --ticket-id <id>                  Ticket to launch or resume
+  --ticket-id <ticket_id>           Ticket to launch or resume (e.g. 1:899). Also accepts UUID.
   --working-directory <path>        Change to a local working directory before launch
   --launch-mode <run|ask>           Ask mode adjusts the fetched prompt context
   --model <identifier>              Preferred model identifier
@@ -360,11 +360,11 @@ async function runAgent(agent, mode = 'run', options = {}) {
     const isResume = mode === 'resume';
     const noSessionHint =
       agent === 'claude'
-        ? `No prior Claude session was found. Start one with \`ovld launch claude --ticket-id <ticket-id>\` first.`
+        ? `No prior Claude session was found. Start one with \`ovld launch claude --ticket-id <ticket_id>\` first.`
         : agent === 'codex'
-          ? `No prior Codex session was found. Start one with \`ovld launch codex --ticket-id <ticket-id>\` first.`
+          ? `No prior Codex session was found. Start one with \`ovld launch codex --ticket-id <ticket_id>\` first.`
           : agent === 'opencode'
-            ? `No prior OpenCode session was found. Start one with \`ovld launch opencode --ticket-id <ticket-id>\` first.`
+            ? `No prior OpenCode session was found. Start one with \`ovld launch opencode --ticket-id <ticket_id>\` first.`
             : '';
     const message = error instanceof Error ? error.message : String(error);
 

package/bin/_cli/protocol.mjs

@@ -1183,7 +1183,7 @@ async function protocolPrompt(args) {
   );
 
   const sessionKey = data.session?.sessionKey;
-  const ticketId = data.ticket?.id;
+  const ticketId = data.ticket?.ticket_id ?? data.ticket?.id;
   console.log(JSON.stringify(data, null, 2));
 
   if (sessionKey) {
@@ -1362,7 +1362,7 @@ export async function runProtocolCommand(subcommand, args) {
 
 Use this for ticket lifecycle work from an agent runtime: create a standalone
 draft with \`ovld protocol create\`, create-and-attach with \`ovld protocol prompt\`,
-or attach to an existing ticket with \`ovld protocol attach --ticket-id <id>\`.
+or attach to an existing ticket with \`ovld protocol attach --ticket-id <ticket_id>\`.
 
 Project discovery:
   When prompting or creating tickets, the CLI automatically resolves the correct
@@ -1399,14 +1399,14 @@ Subcommands:
   attachment-upload-file      Prepare, upload, and finalize a local file in one command
 
 Environment fallback:
-  --session-key <- SESSION_KEY
-  --ticket-id   <- TICKET_ID
+  --session-key  <- SESSION_KEY
+  --ticket-id    <- TICKET_ID  (human-readable ticket_id, e.g. 1:899)
   auth/host     <- OVERLORD_URL, optional OVERLORD_ACCESS_TOKEN + OVERLORD_ORGANIZATION_ID, or shared OAuth credentials from ovld auth/Desktop login
   --timeout     <- OVERLORD_TIMEOUT
 
 Common flags:
   --timeout <ms>              Request timeout in milliseconds (default: ${DEFAULT_TIMEOUT_MS})
-  --ticket-id <id>            Ticket id when the subcommand operates on an existing ticket
+  --ticket-id <ticket_id>     Ticket identifier (e.g. 1:899) when the subcommand operates on an existing ticket
   --session-key <key>         Session key returned by attach/connect/prompt
   --agent <identifier>        Agent identifier sent to Overlord (default: AGENT_IDENTIFIER or claude-code)
   --model <identifier>        Model identifier to snapshot on executing objectives
@@ -1434,7 +1434,7 @@ attach:
   Purpose:
     Create the working session for an agent on an existing ticket. This is the normal first call.
   Required:
-    --ticket-id <id>
+    --ticket-id <ticket_id>   Human-readable identifier (e.g. 1:899). Also accepts UUID.
   Optional:
     --agent <identifier>
     --model <identifier>
@@ -1450,7 +1450,7 @@ connect:
   Purpose:
     Create a lightweight session when you only need a session key and not the full ticket payload
   Required:
-    --ticket-id <id>
+    --ticket-id <ticket_id>   Human-readable identifier (e.g. 1:899). Also accepts UUID.
   Optional:
     --agent <identifier>
     --model <identifier>

package/bin/_cli/setup.mjs

@@ -14,7 +14,7 @@ import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { checkForCliUpdate, getCurrentCliVersion, printCliUpdateNotice } from './cli-update.mjs';
 
-const BUNDLE_VERSION = '1.9.0';
+const BUNDLE_VERSION = '1.11.0';
 const MD_MARKER_START = '<!-- overlord:managed:start -->';
 const MD_MARKER_END = '<!-- overlord:managed:end -->';
 const MANIFEST_DIR = path.join(os.homedir(), '.ovld');
@@ -371,22 +371,22 @@ function slashCommandFiles(agent) {
       {
         path: path.join(base, 'connect.md'),
         content: `---
-description: Connect this session to another Overlord ticket by ticket ID
-argument-hint: <ticket-id>
+description: Connect this session to another Overlord ticket by ticket identifier
+argument-hint: <ticket_id>
 disable-model-invocation: true
 ---
 
-Run \`ovld protocol connect --ticket-id <ticketId>\` using \`$ARGUMENTS\` as the ticket ID.`
+Run \`ovld protocol connect --ticket-id <ticket_id>\` using \`$ARGUMENTS\` as the ticket ID.`
       },
       {
         path: path.join(base, 'load.md'),
         content: `---
 description: Load Overlord ticket context without creating a new session
-argument-hint: <ticket-id>
+argument-hint: <ticket_id>
 disable-model-invocation: true
 ---
 
-Run \`ovld protocol load-context --ticket-id <ticketId>\` using \`$ARGUMENTS\` as the ticket ID.`
+Run \`ovld protocol load-context --ticket-id <ticket_id>\` using \`$ARGUMENTS\` as the ticket ID.`
       },
       {
         path: path.join(base, 'create.md'),

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "overlord-cli",
-  "version": "5.15.1",
+  "version": "5.16.0",
   "description": "Overlord CLI — launch AI agents on tickets from anywhere",
+  "homepage": "https://www.ovld.ai/docs/",
   "type": "module",
   "bin": {
     "overlord": "bin/ovld.mjs",
@@ -28,7 +29,8 @@
   ],
   "license": "Proprietary",
   "repository": {
+    "private": true,
     "type": "git",
-    "url": "git+https://github.com/cooperativ-labs/overlord.git"
+    "url": "git+https://github.com/cooperativ-labs/overlord/packages/overlord-cli.git"
   }
 }

package/plugins/claude/commands/connect.md

@@ -1,6 +1,6 @@
 ---
 description: Connect this session to another Overlord ticket by ticket ID
-argument-hint: <ticket-id>
+argument-hint: <ticket_id>
 disable-model-invocation: true
 ---
 

package/plugins/claude/commands/load.md

@@ -1,6 +1,6 @@
 ---
 description: Load Overlord ticket context without creating a new session
-argument-hint: <ticket-id>
+argument-hint: <ticket_id>
 disable-model-invocation: true
 ---
 

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

@@ -11,7 +11,7 @@ Use this skill whenever Claude Code needs to work with Overlord, whether the ses
 
 Use this mode when the prompt already contains a ticket ID or explicitly says the session was launched by Overlord.
 
-1. Attach first with `ovld protocol attach --ticket-id <ticket-id>`.
+1. Attach first with `ovld protocol attach --ticket-id <ticket_id>`.
 2. Keep the returned `session.sessionKey` for all follow-up calls.
 3. Treat the Overlord ticket prompt as authoritative for the objective, constraints, and delivery target.
 4. Post updates while working with `ovld protocol update --phase execute`.
@@ -76,8 +76,8 @@ Use this mode when the conversation starts normally and the user asks Claude to
    - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to the caller's configured Overlord `project_user.local_working_directory`, then creates a standalone draft.
 2. Default to `create` for new tickets. Only use `/overlord:spawn` or `ovld protocol spawn --agent claude-code --objective "..."` when the user explicitly asks to create and execute immediately.
    `spawn` creates the ticket in `execute` status and attaches immediately.
-3. If the user already has a ticket ID and only wants to inspect it, use `/overlord:load` or run `ovld protocol load-context --ticket-id <ticket-id>`.
-4. If the user wants to route the current session onto an existing ticket by ID, use `/overlord:connect` or run `ovld protocol connect --ticket-id <ticket-id>`.
+3. If the user already has a ticket ID and only wants to inspect it, use `/overlord:load` or run `ovld protocol load-context --ticket-id <ticket_id>`.
+4. If the user wants to route the current session onto an existing ticket by ID, use `/overlord:connect` or run `ovld protocol connect --ticket-id <ticket_id>`.
 5. If the user wants to find a ticket but does not know the ID, use `ovld attach` for interactive ticket search and agent launch, or ask the user for the ticket ID if staying strictly inside chat is the better fit.
 6. If you need other lifecycle commands or flags, run `ovld protocol help` and use the real subcommand list instead of guessing.
 7. Once you attach to a ticket, switch back to Mode 1 and follow the full ticket lifecycle.

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

@@ -9,7 +9,7 @@ Use this skill whenever Cursor needs to work with Overlord, whether the session
 
 ## Mode 1: Launched From Overlord Desktop Or CLI
 
-1. Attach first with `ovld protocol attach --ticket-id <ticket-id>`.
+1. Attach first with `ovld protocol attach --ticket-id <ticket_id>`.
 2. Keep the returned `session.sessionKey` for all follow-up calls.
 3. Treat the Overlord ticket prompt as authoritative for the objective, constraints, and delivery target.
 4. Post updates while working with `ovld protocol update --phase execute`.
@@ -21,8 +21,8 @@ Use this skill whenever Cursor needs to work with Overlord, whether the session
 
 1. If the user wants to create tickets (and does not ask to start execution), use `/create` or run `ovld protocol create --agent cursor --objective "..."`.
 2. Default to `create` for new tickets. Only use `/spawn` or `ovld protocol spawn --agent cursor --objective "..."` when the user explicitly asks to create and execute immediately.
-3. If the user already has a ticket ID and only wants to inspect it, use `/load` or run `ovld protocol load-context --ticket-id <ticket-id>`.
-4. If the user wants to route the current session onto an existing ticket by ID, use `/connect` or run `ovld protocol connect --ticket-id <ticket-id>`.
+3. If the user already has a ticket ID and only wants to inspect it, use `/load` or run `ovld protocol load-context --ticket-id <ticket_id>`.
+4. If the user wants to route the current session onto an existing ticket by ID, use `/connect` or run `ovld protocol connect --ticket-id <ticket_id>`.
 5. If the user wants to search for tickets by keyword or status, use the `search_tickets` MCP tool.
 6. If you need other lifecycle commands or flags, run `ovld protocol help` and use the real subcommand list instead of guessing.
 7. Once you attach to a ticket, switch back to Mode 1 and follow the full ticket lifecycle.

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

@@ -9,10 +9,10 @@ Use this skill when Codex needs to work with Overlord, whether the session was l
 
 ## Mode 1: Launched From Overlord Desktop Or CLI
 
-1. Attach first with `ovld protocol attach --ticket-id <ticket-id>`.
+1. Attach first with `ovld protocol attach --ticket-id <ticket_id>`.
 2. Store the returned `SESSION_KEY` or `session.sessionKey`.
 3. Treat the Overlord ticket prompt as authoritative for the specific objective and ticket-level constraints.
-4. While working, publish meaningful progress with `ovld protocol update --session-key <sessionKey> --ticket-id <ticket-id> --phase execute --summary "..."`.
+4. While working, publish meaningful progress with `ovld protocol update --session-key <sessionKey> --ticket-id <ticket_id> --phase execute --summary "..."`.
 5. If a later user message arrives during the ticket session, publish it immediately with `--event-type user_follow_up` before doing anything else.
 6. If blocked on a human-only action, ask a precise blocking question with `ovld protocol ask` and stop.
 7. Deliver last with `ovld protocol deliver`, including meaningful `changeRationales` for every behavioral git-tracked change.
@@ -69,8 +69,8 @@ For larger delivery payloads, prefer `--payload-file -` and stream the full JSON
 
 1. If the user wants to create tickets (and does not ask to start execution), run `ovld protocol create --agent codex --objective "..."`.
 2. Default to `create` for new tickets. Only use `ovld protocol spawn --agent codex --objective "..."` when the user explicitly asks to create and execute immediately.
-3. If the user wants to inspect an existing ticket without starting work, use `ovld protocol load-context --ticket-id <ticket-id>`.
-4. If the user wants to work an existing ticket, attach with `ovld protocol attach --ticket-id <ticket-id>` and then switch to Mode 1.
+3. If the user wants to inspect an existing ticket without starting work, use `ovld protocol load-context --ticket-id <ticket_id>`.
+4. If the user wants to work an existing ticket, attach with `ovld protocol attach --ticket-id <ticket_id>` and then switch to Mode 1.
 5. If the user wants to find existing tickets by keyword or workflow state, use the `search_tickets` tool.
 6. If you need to understand project routing before spawning, use `ovld protocol discover-project`.
 7. If you need other lifecycle commands or flags, run `ovld protocol help` and use the real subcommand list instead of guessing.