overlord-cli 0.2605312007.0 → 0.2606010644.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2243,7 +2243,7 @@ async function protocolPrompt(args) {
2243
2243
 
2244
2244
  // When --project-id is not provided, auto-send cwd as workingDirectory so
2245
2245
  // the server can resolve the project from the caller's project_user
2246
- // local_working_directory setting.
2246
+ // project resource directory setting.
2247
2247
  const personal = Boolean(flags.personal);
2248
2248
  const workingDirectory =
2249
2249
  flags['working-directory'] ?? (!flags['project-id'] && !personal ? process.cwd() : undefined);
@@ -2920,7 +2920,7 @@ prompt:
2920
2920
  Purpose:
2921
2921
  Create a ticket and attach to it in one call.
2922
2922
  When --project-id is omitted, automatically resolves the project from the
2923
- current working directory (matching against the caller's project_user.local_working_directory).
2923
+ current working directory (matching against the caller's project resource directories).
2924
2924
  Required:
2925
2925
  --objective <text>
2926
2926
  or: --objectives-json <json> / --objectives-file <path|-> with [{ "objective": "...", "title": "...", "autoAdvance": true }]
@@ -3028,7 +3028,7 @@ record-work:
3028
3028
  Notes:
3029
3029
  Project resolution mirrors \`prompt\`: if --project-id is not set and --personal is not used,
3030
3030
  the CLI sends cwd as workingDirectory and the API matches it against your configured
3031
- project_user.local_working_directory rows. If no match, the API returns 400 — re-run with
3031
+ project_resource_directories rows. If no match, the API returns 400 — re-run with
3032
3032
  --project-id <id> or --personal.
3033
3033
  Use this for completed-from-chat work. If you still need to execute the work, use \`create\`
3034
3034
  for a draft ticket or \`prompt\` to create and start execution immediately.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "overlord-cli",
3
- "version": "0.2605312007.0",
3
+ "version": "0.2606010644.0",
4
4
  "description": "Overlord CLI — launch AI agents on tickets from anywhere",
5
5
  "homepage": "https://www.ovld.ai/docs/",
6
6
  "type": "module",
@@ -123,7 +123,7 @@ Use this mode when the conversation starts normally and the user asks you to cre
123
123
 
124
124
  1. If the user wants to create tickets (and does not ask to start execution), run `ovld protocol create --agent antigravity --objectives-json '[{"objective":"..."}]'`.
125
125
  - When `--session-key` and `--ticket-id` are provided, it creates a follow-up draft.
126
- - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord `local_working_directory`, then creates a standalone draft.
126
+ - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord project resource directories, then creates a standalone draft.
127
127
  - Pass multiple items in `--objectives-json` when creating ordered steps for the same feature or goal.
128
128
  2. Default to `create` for new tickets. Only use `/overlord:prompt` or `ovld protocol prompt --agent antigravity --objectives-json '[{"objective":"..."}]'` when the user explicitly asks to create and execute immediately.
129
129
  `prompt` creates the ticket in `execute` status and attaches immediately.
@@ -276,4 +276,4 @@ This keeps the ticket feed readable while preserving the full document in versio
276
276
  - Do not add or commit changes unless the user explicitly asks you to commit.
277
277
  - Delivery is the concluding step. After delivering, stop implementation work unless the user explicitly asks for follow-up execution; once follow-up execution is complete, deliver again.
278
278
 
279
- <!-- version: 0.1.5 -->
279
+ <!-- version: 0.1.6 -->
@@ -60,7 +60,7 @@ Use this mode when the conversation starts normally and the user asks Claude to
60
60
 
61
61
  1. If the user wants to create tickets (and does not ask to start execution), use `/overlord:create` or run `ovld protocol create --agent claude-code --objectives-json '[{"objective":"..."}]'`.
62
62
  - When `--session-key` and `--ticket-id` are provided, it creates a follow-up draft.
63
- - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord `local_working_directory`, then creates a standalone draft.
63
+ - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord project resource directories, then creates a standalone draft.
64
64
  - Pass multiple items in `--objectives-json` when creating ordered steps for the same feature or goal.
65
65
  - If the user wants to **add more objectives to an existing ticket** (not create a new ticket), use `ovld protocol add-objectives --ticket-id <ticket_id> --objectives-json '[{"objective":"..."}]'` instead.
66
66
  2. Default to `create` for new tickets. Only use `/overlord:prompt` or `ovld protocol prompt --agent claude-code --objectives-json '[{"objective":"..."}]'` when the user explicitly asks to create and execute immediately.
@@ -114,5 +114,5 @@ For the `record-change-rationales` command and full payload shape with optional
114
114
  - [reference/context.md](reference/context.md) — Shared state, attachments, and large artifact policy
115
115
  - [reference/shell-escaping.md](reference/shell-escaping.md) — Heredoc stdin piping for special characters in summaries and payloads
116
116
 
117
- <!-- version: 0.5.9 -->
117
+ <!-- version: 0.5.10 -->
118
118
 
@@ -60,7 +60,7 @@ Use this mode when the conversation starts normally and the user asks Cursor to
60
60
 
61
61
  1. If the user wants to create tickets (and does not ask to start execution), use `/create` or run `ovld protocol create --agent cursor --objectives-json '[{"objective":"..."}]'`.
62
62
  - When `--session-key` and `--ticket-id` are provided, it creates a follow-up draft.
63
- - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord `local_working_directory`, then creates a standalone draft.
63
+ - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord project resource directories, then creates a standalone draft.
64
64
  - Pass multiple items in `--objectives-json` when creating ordered steps for the same feature or goal.
65
65
  - If the user wants to **add more objectives to an existing ticket** (not create a new ticket), use `ovld protocol add-objectives --ticket-id <ticket_id> --objectives-json '[{"objective":"..."}]'` instead.
66
66
  2. Default to `create` for new tickets. Only use `/prompt` or `ovld protocol prompt --agent cursor --objectives-json '[{"objective":"..."}]'` when the user explicitly asks to create and execute immediately.
@@ -114,5 +114,5 @@ For the `record-change-rationales` command and full payload shape with optional
114
114
  - [reference/context.md](reference/context.md) — Shared state, attachments, and large artifact policy
115
115
  - [reference/shell-escaping.md](reference/shell-escaping.md) — Heredoc stdin piping for special characters in summaries and payloads
116
116
 
117
- <!-- version: 0.5.9 -->
117
+ <!-- version: 0.5.10 -->
118
118
 
@@ -60,7 +60,7 @@ Use this mode when the conversation starts normally and the user asks Codex to c
60
60
 
61
61
  1. If the user wants to create tickets (and does not ask to start execution), run `ovld protocol create --agent codex --objectives-json '[{"objective":"..."}]'`.
62
62
  - When `--session-key` and `--ticket-id` are provided, it creates a follow-up draft.
63
- - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord `local_working_directory`, then creates a standalone draft.
63
+ - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord project resource directories, then creates a standalone draft.
64
64
  - Pass multiple items in `--objectives-json` when creating ordered steps for the same feature or goal.
65
65
  - If the user wants to **add more objectives to an existing ticket** (not create a new ticket), use `ovld protocol add-objectives --ticket-id <ticket_id> --objectives-json '[{"objective":"..."}]'` instead.
66
66
  2. Default to `create` for new tickets. Only use `ovld protocol prompt --agent codex --objectives-json '[{"objective":"..."}]'` when the user explicitly asks to create and execute immediately.
@@ -115,5 +115,5 @@ For the `record-change-rationales` command and full payload shape with optional
115
115
  - [reference/context.md](reference/context.md) — Shared state, attachments, and large artifact policy
116
116
  - [reference/shell-escaping.md](reference/shell-escaping.md) — Heredoc stdin piping for special characters in summaries and payloads
117
117
 
118
- <!-- version: 0.5.9 -->
118
+ <!-- version: 0.5.10 -->
119
119