overlord-cli 0.2606050806.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/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']
@@ -3175,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-or-name>   Explicit project (UUID or name) 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
@@ -3190,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.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord-cli",
-  "version": "0.2606050806.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/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.

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.

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

@@ -271,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: {

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.