overlord-cli 0.2606050717.0 → 0.2606050938.0

package/README.md

@@ -134,7 +134,7 @@ Agents can find docs here: https://www.ovld.ai/docs/for-agents
 - `revert` - restore the local working tree to an objective checkpoint after fetching its checkpoint row
 - `search-tickets` - find tickets by keyword, status, project, creator, or update date
 - `add-objectives` - append ordered objectives to an existing ticket (`--objectives-json` / `--objectives-file`)
-- `create` - create a draft ticket without attaching (standalone or follow-up)
+- `create` - create a draft ticket without attaching (standalone or follow-up; `--project-id` can override the inherited project during follow-up creation)
 - `prompt` - create a ticket and attach to it immediately (`spawn` is a backward-compatible alias)
 - `record-work` - record already-completed chat work as a ticket in review with a completed objective and trigger feed-post generation
 - `update` - post progress, discussion/decision events, optional change rationales, and explicit `--begin-follow-up-work` transitions

package/bin/_cli/new-ticket.mjs

@@ -48,10 +48,10 @@ function parseFlags(args) {
 
 function buildUsage(commandName) {
   if (commandName === 'prompt') {
-    return 'Usage: ovld prompt --objectives-json \'[{"objective":"..."}]\' [--objectives-file <path>] [--title "..."] [--acceptance-criteria "..."] [--available-tools "..."] [--for-human] [--priority low|medium|high|urgent] [--project-id <id>] [--agent <agent>] [--model <identifier>] [--delegate <agent>]';
+    return 'Usage: ovld prompt --objectives-json \'[{"objective":"..."}]\' [--objectives-file <path>] [--title "..."] [--acceptance-criteria "..."] [--available-tools "..."] [--for-human] [--priority low|medium|high|urgent] [--project-id <id-or-name>] [--agent <agent>] [--model <identifier>] [--delegate <agent>]';
   }
 
-  return 'Usage: ovld create --objectives-json \'[{"objective":"..."}]\' [--objectives-file <path>] [--title "..."] [--acceptance-criteria "..."] [--available-tools "..."] [--for-human] [--priority low|medium|high|urgent] [--project-id <id>] [--agent <agent>] [--model <identifier>] [--delegate <agent>]';
+  return 'Usage: ovld create --objectives-json \'[{"objective":"..."}]\' [--objectives-file <path>] [--title "..."] [--acceptance-criteria "..."] [--available-tools "..."] [--for-human] [--priority low|medium|high|urgent] [--project-id <id-or-name>] [--agent <agent>] [--model <identifier>] [--delegate <agent>]';
 }
 
 function resolveForHumanFlag(flags) {
@@ -305,15 +305,17 @@ async function createTicket(platformUrl, bearerToken, localSecret, organizationI
   return data.ticket;
 }
 
-function resolveProject(projects, projectId) {
-  if (!projectId) return null;
+export function resolveProject(projects, projectIdOrName) {
+  if (!projectIdOrName) return null;
 
-  const project = projects.find(candidate => candidate.id === projectId);
-  if (!project) {
-    throw new Error(`Unknown project ID: ${projectId}`);
-  }
+  const byId = projects.find(candidate => candidate.id === projectIdOrName);
+  if (byId) return byId;
+
+  const lowerName = projectIdOrName.toLowerCase();
+  const byName = projects.find(candidate => candidate.name?.toLowerCase() === lowerName);
+  if (byName) return byName;
 
-  return project;
+  throw new Error(`Unknown project: ${projectIdOrName}`);
 }
 
 function resolveAgent(agent) {
@@ -424,7 +426,8 @@ Creates a ticket after interactive numbered project selection.
 
 Examples:
   ovld create --objectives-json '[{"objective":"Implement login page"}]'
-  ovld create --objectives-json '[{"objective":"Fix sync bug"}]' --project-id <project-id>
+  ovld create --objectives-json '[{"objective":"Fix sync bug"}]' --project-id <id-or-name>
+  ovld create --objectives-json '[{"objective":"Fix sync bug"}]' --project-id "My Project"
 `);
     return;
   }

package/bin/_cli/protocol.mjs

@@ -2551,6 +2551,7 @@ async function protocolCreateTicket(args) {
       sessionKey,
       ticketId,
       ...objectiveInput,
+      ...(flags['project-id'] ? { projectId: String(flags['project-id']) } : {}),
       ...(flags.title ? { title: String(flags.title) } : {}),
       ...(flags.priority ? { priority: String(flags.priority) } : {}),
       ...(flags['acceptance-criteria']
@@ -2836,10 +2837,12 @@ Project discovery:
   You can also discover the project explicitly:
 
     ovld protocol discover-project
-    ovld protocol discover-project --project-id <project-uuid>
+    ovld protocol discover-project --project-id <id-or-name>
+    ovld protocol discover-project --project-id "My Project"
     ovld protocol discover-project --working-directory /path/to/repo
 
   Use --project-id to override automatic resolution on discover, prompt, or ticket creation.
+  Accepts a UUID or a project name (names are unique per organization).
   Use --personal to create a private ticket without assigning any project.
 
 Subcommands:
@@ -2912,7 +2915,7 @@ discover-project:
     Resolve the Overlord project that corresponds to the current (or given) working directory.
     Uses the caller's configured "Local working directory" for matching.
   Optional:
-    --project-id <uuid>       Resolve this project directly; skips working-directory matching
+    --project-id <id-or-name> Resolve this project directly; skips working-directory matching
     --working-directory <path>  Directory to match (default: current working directory)
     --device-fingerprint <fp>   Prefer resource directories for this registered device
     --device-hostname <name>    Register/update device metadata when fingerprint is provided
@@ -2982,7 +2985,7 @@ search-tickets:
     --status <csv>             Comma-separated statuses, e.g. "draft,next-up,execute"
     --include-completed <bool> Include completed tickets (default: false)
     --limit <n>                Max results 1..50 (default: 8)
-    --project-id <uuid>        Restrict to a single project
+    --project-id <id-or-name>  Restrict to a single project
     --created-by <uuid>        Restrict to tickets created by this user
     --updated-after <iso>      Updated_at >= ISO timestamp
     --updated-before <iso>     Updated_at <= ISO timestamp
@@ -3134,7 +3137,7 @@ prompt:
   Optional:
     --title <text>
     --priority <level>        low | medium | high | urgent
-    --project-id <id>         Explicit project; skips working-directory resolution
+    --project-id <id-or-name> Explicit project (UUID or name); skips working-directory resolution
     --personal                Create the ticket without assigning a project
     --working-directory <path> Override cwd for project resolution (default: cwd)
     --acceptance-criteria <text>
@@ -3173,7 +3176,7 @@ create:
     --session-key <key>
     --ticket-id <ticket_id>
     --working-directory <path>  Resolve project by your configured local working directory (default: cwd)
-    --project-id <id>           Explicit project for standalone draft creation
+    --project-id <id-or-name>   Explicit project (UUID or name); overrides follow-up inheritance or standalone cwd resolution
     --personal                  Create a private standalone draft without a project
     --title <text>
     --priority <level>        low | medium | high | urgent
@@ -3188,7 +3191,7 @@ create:
     New draft ticket JSON (follow-up draft when session flags are provided)
   Notes:
     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.
+    Follow-up create requires both --session-key and --ticket-id and inherits the current ticket project unless --project-id is passed.
     Use create for future work. If the work is already complete and only needs to be recorded,
     use \`record-work\` instead.
 
@@ -3219,7 +3222,7 @@ record-work:
   Optional:
     --title <text>            Auto-derived from objective if omitted
     --priority <level>        low | medium | high | urgent
-    --project-id <id>         Skip cwd resolution and use this project explicitly
+    --project-id <id-or-name> Skip cwd resolution and use this project explicitly (UUID or name)
     --working-directory <path> Override cwd for project resolution
     --personal                Create a private ticket when no project should be associated
     --artifacts-json <json>
@@ -3421,8 +3424,10 @@ Examples:
   ovld protocol auth-status
   ovld protocol discover-project
   ovld protocol discover-project --project-id <project-uuid>
+  ovld protocol discover-project --project-id "My Project"              # resolve by name
   ovld protocol discover-project --working-directory /path/to/repo
   ovld protocol prompt --agent codex --objective "Implement feature X"   # auto-resolves project from cwd
+  ovld protocol prompt --project-id "My Project" --objective "Fix bug"   # resolve project by name
   ovld protocol attach --ticket-id 1:899
   ovld protocol attach --ticket-id 1:899 --external-session-id null
   ovld protocol connect --ticket-id 1:899

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord-cli",
-  "version": "0.2606050717.0",
+  "version": "0.2606050938.0",
   "description": "Overlord CLI — launch AI agents on tickets from anywhere",
   "homepage": "https://www.ovld.ai/docs/",
   "type": "module",

package/plugins/claude/commands/record-work.md

@@ -24,6 +24,6 @@ After the command succeeds, report the new `TICKET_ID`.
 Rules:
 - Do NOT use this for in-progress work. Use `/prompt` for that.
 - The CLI validates that every changed git-tracked file is represented in `changeRationales` unless `--skip-file-change-check` is passed.
-- If project resolution fails, re-run with `--project-id <id>` or `--personal`.
+- If project resolution fails, re-run with `--project-id <id-or-name>` or `--personal`.
 
 

package/plugins/claude/skills/overlord-ticket/reference/cli.md

@@ -114,6 +114,7 @@ When creating tickets from within a repository:
 - Prefer `create` by default for draft ticket creation.
 - Use `prompt` only when the user explicitly asks to start execution immediately.
 - Both commands can resolve the project from the current working directory; use `--working-directory` to override or `--project-id` to be explicit.
+- Follow-up `create` calls under an active session inherit the current ticket's project by default, but `--project-id` can override that when the follow-up belongs in a different project.
 - Create multiple tickets when each prompt represents a different feature or goal.
 - Add objectives to the same ticket when each prompt is a sequential step toward the same feature or goal; use `ovld protocol add-objectives --ticket-id <ticket_id> --objectives-json '[{"objective":"..."}]'`.
 - `create`, `prompt`, and `record-work` require `--objectives-json` or `--objectives-file` with an ordered array of `{ "objective": "...", "title": "...", "autoAdvance": true }` objects. A single objective is just an array with one item.
@@ -134,11 +135,12 @@ To inspect project resolution explicitly:
 
 ```bash
 ovld protocol discover-project
-ovld protocol discover-project --project-id <project_uuid>
+ovld protocol discover-project --project-id <id-or-name>
+ovld protocol discover-project --project-id "My Project"
 ovld protocol discover-project --working-directory /path/to/repo
 ```
 
-Use `--project-id` when the project id is already known. Use `--working-directory` to override cwd path matching. If the runtime has an `OVERLORD_DEVICE_FINGERPRINT`, pass `--device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"` so resource-directory matching prefers the current device.
+Use `--project-id` when the project ID or name is already known (names are unique per organization, matched case-insensitively). Use `--working-directory` to override cwd path matching. If the runtime has an `OVERLORD_DEVICE_FINGERPRINT`, pass `--device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"` so resource-directory matching prefers the current device.
 
 ## Creating Projects
 

package/plugins/cursor/skills/overlord-ticket/reference/cli.md

@@ -114,6 +114,7 @@ When creating tickets from within a repository:
 - Prefer `create` by default for draft ticket creation.
 - Use `prompt` only when the user explicitly asks to start execution immediately.
 - Both commands can resolve the project from the current working directory; use `--working-directory` to override or `--project-id` to be explicit.
+- Follow-up `create` calls under an active session inherit the current ticket's project by default, but `--project-id` can override that when the follow-up belongs in a different project.
 - Create multiple tickets when each prompt represents a different feature or goal.
 - Add objectives to the same ticket when each prompt is a sequential step toward the same feature or goal; use `ovld protocol add-objectives --ticket-id <ticket_id> --objectives-json '[{"objective":"..."}]'`.
 - `create`, `prompt`, and `record-work` require `--objectives-json` or `--objectives-file` with an ordered array of `{ "objective": "...", "title": "...", "autoAdvance": true }` objects. A single objective is just an array with one item.
@@ -134,11 +135,12 @@ To inspect project resolution explicitly:
 
 ```bash
 ovld protocol discover-project
-ovld protocol discover-project --project-id <project_uuid>
+ovld protocol discover-project --project-id <id-or-name>
+ovld protocol discover-project --project-id "My Project"
 ovld protocol discover-project --working-directory /path/to/repo
 ```
 
-Use `--project-id` when the project id is already known. Use `--working-directory` to override cwd path matching. If the runtime has an `OVERLORD_DEVICE_FINGERPRINT`, pass `--device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"` so resource-directory matching prefers the current device.
+Use `--project-id` when the project ID or name is already known (names are unique per organization, matched case-insensitively). Use `--working-directory` to override cwd path matching. If the runtime has an `OVERLORD_DEVICE_FINGERPRINT`, pass `--device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"` so resource-directory matching prefers the current device.
 
 ## Creating Projects
 

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

@@ -64,7 +64,8 @@ const tools = [
       properties: {
         project_id: {
           type: 'string',
-          description: 'Project UUID to resolve directly. Skips working-directory matching.'
+          description:
+            'Project UUID or name to resolve directly. Skips working-directory matching. Names are unique per organization and matched case-insensitively.'
         },
         working_directory: {
           type: 'string',
@@ -270,7 +271,8 @@ const tools = [
   },
   {
     name: 'create_ticket',
-    description: 'Create a draft ticket without attaching (ovld protocol create).',
+    description:
+      'Create a draft ticket without attaching (ovld protocol create). When session_key/ticket_id are provided, this creates a follow-up draft and project_id can override the current ticket project.',
     inputSchema: {
       type: 'object',
       properties: {
@@ -1170,6 +1172,11 @@ const searchTicketsTool = {
       limit: {
         type: 'number',
         description: 'Maximum number of results to return (1–50, default 8).'
+      },
+      project_id: {
+        type: 'string',
+        description:
+          'Optional project UUID or name to restrict results. Names are matched case-insensitively.'
       }
     }
   },
@@ -1177,7 +1184,8 @@ const searchTicketsTool = {
     query: args.query,
     statuses: Array.isArray(args.statuses) ? args.statuses.join(',') : args.statuses,
     'include-completed': args.include_completed,
-    limit: args.limit
+    limit: args.limit,
+    'project-id': args.project_id
   }),
   subcommand: 'search-tickets'
 };

package/plugins/overlord/skills/overlord-ticket/reference/cli.md

@@ -114,6 +114,7 @@ When creating tickets from within a repository:
 - Prefer `create` by default for draft ticket creation.
 - Use `prompt` only when the user explicitly asks to start execution immediately.
 - Both commands can resolve the project from the current working directory; use `--working-directory` to override or `--project-id` to be explicit.
+- Follow-up `create` calls under an active session inherit the current ticket's project by default, but `--project-id` can override that when the follow-up belongs in a different project.
 - Create multiple tickets when each prompt represents a different feature or goal.
 - Add objectives to the same ticket when each prompt is a sequential step toward the same feature or goal; use `ovld protocol add-objectives --ticket-id <ticket_id> --objectives-json '[{"objective":"..."}]'`.
 - `create`, `prompt`, and `record-work` require `--objectives-json` or `--objectives-file` with an ordered array of `{ "objective": "...", "title": "...", "autoAdvance": true }` objects. A single objective is just an array with one item.
@@ -134,11 +135,12 @@ To inspect project resolution explicitly:
 
 ```bash
 ovld protocol discover-project
-ovld protocol discover-project --project-id <project_uuid>
+ovld protocol discover-project --project-id <id-or-name>
+ovld protocol discover-project --project-id "My Project"
 ovld protocol discover-project --working-directory /path/to/repo
 ```
 
-Use `--project-id` when the project id is already known. Use `--working-directory` to override cwd path matching. If the runtime has an `OVERLORD_DEVICE_FINGERPRINT`, pass `--device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"` so resource-directory matching prefers the current device.
+Use `--project-id` when the project ID or name is already known (names are unique per organization, matched case-insensitively). Use `--working-directory` to override cwd path matching. If the runtime has an `OVERLORD_DEVICE_FINGERPRINT`, pass `--device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"` so resource-directory matching prefers the current device.
 
 ## Creating Projects