overlord-cli 0.2605230834.0 → 0.2605231102.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.
Files changed (7) hide show
  1. package/package.json +1 -1
  2. package/plugins/claude/skills/overlord-ticket/SKILL.md +4 -4
  3. package/plugins/claude/skills/overlord-ticket/reference/devices.md +3 -3
  4. package/plugins/cursor/skills/overlord-ticket/SKILL.md +4 -4
  5. package/plugins/cursor/skills/overlord-ticket/reference/devices.md +3 -3
  6. package/plugins/overlord/skills/overlord-ticket/SKILL.md +4 -4
  7. package/plugins/overlord/skills/overlord-ticket/reference/devices.md +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "overlord-cli",
3
- "version": "0.2605230834.0",
3
+ "version": "0.2605231102.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",
package/plugins/claude/skills/overlord-ticket/SKILL.md CHANGED
@@ -12,12 +12,12 @@ Use this skill whenever Claude Code needs to work with Overlord, whether the ses
12
12
  Use this mode when the prompt already contains a ticket ID or explicitly says the session was launched by Overlord.
13
13
 
14
14
  1. Attach first with `ovld protocol attach --ticket-id <ticket_id>`.
15
- 2. Keep the returned `session.sessionKey` for all follow-up calls.
15
+ 2. The attach response prints JSON to stdout containing `session.sessionKey`. The CLI also persists this key automatically so subsequent `ovld protocol` commands in the same working directory resolve it without `--session-key`. If auto-resolution fails, pass `--session-key <sessionKey>` explicitly on every subsequent call.
16
16
  3. Treat the Overlord ticket prompt as authoritative for the objective, constraints, and delivery target.
17
- 4. Post updates while working with `ovld protocol update --phase execute`.
17
+ 4. Post updates while working: `ovld protocol update --session-key <sessionKey> --ticket-id <ticket_id> --summary "..." --phase execute`.
18
18
  5. Follow-up messages after the initial ticket are captured automatically by the installed `UserPromptSubmit` hook. Do not post `user_follow_up` manually unless the hook is unavailable.
19
- 6. If blocked, call `ovld protocol ask` and stop.
20
- 7. Deliver last with `ovld protocol deliver`, including `changeRationales` for each meaningful behavioral file change.
19
+ 6. If blocked, call `ovld protocol ask --session-key <sessionKey> --ticket-id <ticket_id> --question "..."` and stop.
20
+ 7. Deliver last with `ovld protocol deliver --session-key <sessionKey> --ticket-id <ticket_id> --summary "..."`, including `changeRationales` for each meaningful behavioral file change.
21
21
 
22
22
  For full command syntax, flags, phase values, and event types see [reference/cli.md](reference/cli.md).
23
23
 
package/plugins/claude/skills/overlord-ticket/reference/devices.md CHANGED
@@ -1,13 +1,13 @@
1
- # Devices And Checkout Paths
1
+ # Execution Targets And Checkout Paths
2
2
 
3
- Device rows use **(organization_id, user_id, device_fingerprint)**, so the same physical machine can register independently in each org you belong to. Persist a fingerprint per workstation, upsert via `ovld protocol get-device`, then maintain checkout paths via `list-project-resources`, `add-project-resource`, `update-project-resource`, and `update-device` (`ovld protocol help` lists flags).
3
+ Execution targets are canonical rows keyed by a real `device_fingerprint` when known, or by an SSH placeholder until the remote target registers. Organization labels, user access, SSH credential references, and project membership live in separate association rows. Persist a fingerprint per workstation, upsert via `ovld protocol get-device`, then maintain checkout paths via `list-project-resources`, `add-project-resource`, `update-project-resource`, and `update-device` (`ovld protocol help` lists flags).
4
4
 
5
5
  ```bash
6
6
  ovld protocol get-device --device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"
7
7
  ovld protocol list-project-resources --project-id <project_uuid> --device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"
8
8
  ```
9
9
 
10
- `ovld runner start` uses the same device identity and project resource directories to claim queued execution requests from manual Run and auto-advance. `ovld runner once` claims at most one request and exits.
10
+ `ovld runner start` uses the same execution target identity and project resource directories to claim queued execution requests from manual Run and auto-advance. Primary resource directories are scoped per `(project, execution target)`. `ovld runner once` claims at most one request and exits.
11
11
 
12
12
  ## Choosing `--execution-target`
13
13
 
package/plugins/cursor/skills/overlord-ticket/SKILL.md CHANGED
@@ -12,12 +12,12 @@ Use this skill whenever Cursor needs to work with Overlord, whether the session
12
12
  Use this mode when the prompt already contains a ticket ID or explicitly says the session was launched by Overlord.
13
13
 
14
14
  1. Attach first with `ovld protocol attach --ticket-id <ticket_id>`.
15
- 2. Keep the returned `session.sessionKey` for all follow-up calls.
15
+ 2. The attach response prints JSON to stdout containing `session.sessionKey`. The CLI also persists this key automatically so subsequent `ovld protocol` commands in the same working directory resolve it without `--session-key`. If auto-resolution fails, pass `--session-key <sessionKey>` explicitly on every subsequent call.
16
16
  3. Treat the Overlord ticket prompt as authoritative for the objective, constraints, and delivery target.
17
- 4. Post updates while working with `ovld protocol update --phase execute`.
17
+ 4. Post updates while working: `ovld protocol update --session-key <sessionKey> --ticket-id <ticket_id> --summary "..." --phase execute`.
18
18
  5. Follow-up messages after the initial ticket are captured automatically by the installed Cursor `beforeSubmitPrompt` hook (see `~/.cursor/hooks.json`). Do not post `user_follow_up` manually unless the hook is unavailable.
19
- 6. If blocked, call `ovld protocol ask` and stop.
20
- 7. Deliver last with `ovld protocol deliver`, including `changeRationales` for each meaningful behavioral file change.
19
+ 6. If blocked, call `ovld protocol ask --session-key <sessionKey> --ticket-id <ticket_id> --question "..."` and stop.
20
+ 7. Deliver last with `ovld protocol deliver --session-key <sessionKey> --ticket-id <ticket_id> --summary "..."`, including `changeRationales` for each meaningful behavioral file change.
21
21
 
22
22
  For full command syntax, flags, phase values, and event types see [reference/cli.md](reference/cli.md).
23
23
 
package/plugins/cursor/skills/overlord-ticket/reference/devices.md CHANGED
@@ -1,13 +1,13 @@
1
- # Devices And Checkout Paths
1
+ # Execution Targets And Checkout Paths
2
2
 
3
- Device rows use **(organization_id, user_id, device_fingerprint)**, so the same physical machine can register independently in each org you belong to. Persist a fingerprint per workstation, upsert via `ovld protocol get-device`, then maintain checkout paths via `list-project-resources`, `add-project-resource`, `update-project-resource`, and `update-device` (`ovld protocol help` lists flags).
3
+ Execution targets are canonical rows keyed by a real `device_fingerprint` when known, or by an SSH placeholder until the remote target registers. Organization labels, user access, SSH credential references, and project membership live in separate association rows. Persist a fingerprint per workstation, upsert via `ovld protocol get-device`, then maintain checkout paths via `list-project-resources`, `add-project-resource`, `update-project-resource`, and `update-device` (`ovld protocol help` lists flags).
4
4
 
5
5
  ```bash
6
6
  ovld protocol get-device --device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"
7
7
  ovld protocol list-project-resources --project-id <project_uuid> --device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"
8
8
  ```
9
9
 
10
- `ovld runner start` uses the same device identity and project resource directories to claim queued execution requests from manual Run and auto-advance. `ovld runner once` claims at most one request and exits.
10
+ `ovld runner start` uses the same execution target identity and project resource directories to claim queued execution requests from manual Run and auto-advance. Primary resource directories are scoped per `(project, execution target)`. `ovld runner once` claims at most one request and exits.
11
11
 
12
12
  ## Choosing `--execution-target`
13
13
 
package/plugins/overlord/skills/overlord-ticket/SKILL.md CHANGED
@@ -12,12 +12,12 @@ Use this skill whenever Codex needs to work with Overlord, whether the session w
12
12
  Use this mode when the prompt already contains a ticket ID or explicitly says the session was launched by Overlord.
13
13
 
14
14
  1. Attach first with `ovld protocol attach --ticket-id <ticket_id>`.
15
- 2. Keep the returned `session.sessionKey` for all follow-up calls.
15
+ 2. The attach response prints JSON to stdout containing `session.sessionKey`. The CLI also persists this key automatically so subsequent `ovld protocol` commands in the same working directory resolve it without `--session-key`. If auto-resolution fails, pass `--session-key <sessionKey>` explicitly on every subsequent call.
16
16
  3. Treat the Overlord ticket prompt as authoritative for the objective, constraints, and delivery target.
17
- 4. Post updates while working with `ovld protocol update --phase execute`.
17
+ 4. Post updates while working: `ovld protocol update --session-key <sessionKey> --ticket-id <ticket_id> --summary "..." --phase execute`.
18
18
  5. Follow-up messages after the initial ticket are captured automatically by the installed `UserPromptSubmit` hook. Do not post `user_follow_up` manually unless the hook is unavailable.
19
- 6. If blocked, call `ovld protocol ask` and stop.
20
- 7. Deliver last with `ovld protocol deliver`, including `changeRationales` for each meaningful behavioral file change.
19
+ 6. If blocked, call `ovld protocol ask --session-key <sessionKey> --ticket-id <ticket_id> --question "..."` and stop.
20
+ 7. Deliver last with `ovld protocol deliver --session-key <sessionKey> --ticket-id <ticket_id> --summary "..."`, including `changeRationales` for each meaningful behavioral file change.
21
21
 
22
22
  For full command syntax, flags, phase values, and event types see [reference/cli.md](reference/cli.md).
23
23
 
package/plugins/overlord/skills/overlord-ticket/reference/devices.md CHANGED
@@ -1,13 +1,13 @@
1
- # Devices And Checkout Paths
1
+ # Execution Targets And Checkout Paths
2
2
 
3
- Device rows use **(organization_id, user_id, device_fingerprint)**, so the same physical machine can register independently in each org you belong to. Persist a fingerprint per workstation, upsert via `ovld protocol get-device`, then maintain checkout paths via `list-project-resources`, `add-project-resource`, `update-project-resource`, and `update-device` (`ovld protocol help` lists flags).
3
+ Execution targets are canonical rows keyed by a real `device_fingerprint` when known, or by an SSH placeholder until the remote target registers. Organization labels, user access, SSH credential references, and project membership live in separate association rows. Persist a fingerprint per workstation, upsert via `ovld protocol get-device`, then maintain checkout paths via `list-project-resources`, `add-project-resource`, `update-project-resource`, and `update-device` (`ovld protocol help` lists flags).
4
4
 
5
5
  ```bash
6
6
  ovld protocol get-device --device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"
7
7
  ovld protocol list-project-resources --project-id <project_uuid> --device-fingerprint "$OVERLORD_DEVICE_FINGERPRINT"
8
8
  ```
9
9
 
10
- `ovld runner start` uses the same device identity and project resource directories to claim queued execution requests from manual Run and auto-advance. `ovld runner once` claims at most one request and exits.
10
+ `ovld runner start` uses the same execution target identity and project resource directories to claim queued execution requests from manual Run and auto-advance. Primary resource directories are scoped per `(project, execution target)`. `ovld runner once` claims at most one request and exits.
11
11
 
12
12
  ## Choosing `--execution-target`
13
13