overlord-cli 0.2608181255.0 → 0.2608181615.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.26
+0.3.28

package/dist/connectors/adapters/antigravity/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://antigravity.google/schemas/v1/plugin.json",
   "name": "overlord",
-  "version": "0.3.26",
+  "version": "0.3.28",
   "description": "Chat-driven access to Overlord mission protocol workflows through skills and MCP.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/antigravity/skills/attach.md

@@ -10,7 +10,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol attach --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol attach --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `attach` only when the user explicitly wants this Antigravity session to execute mission work.
 - After the command succeeds, report the returned `SESSION_KEY`.
 - Follow the `overlord-mission` skill workflow after attaching: update while working, ask exactly one blocking question if blocked, and deliver last.

package/dist/connectors/adapters/antigravity/skills/connect.md

@@ -10,7 +10,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol connect --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol connect --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `connect`, not `attach`.
 - Do not load extra mission context unless the user explicitly asks for it.
 - After the command succeeds, report the returned `SESSION_KEY` and confirm that future updates should use that mission.

package/dist/connectors/adapters/antigravity/skills/discuss-objective.md

@@ -10,7 +10,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol discuss-objective --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol discuss-objective --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `discuss-objective`, not `attach`, when the user is opening or discussing a mission but has not asked Antigravity to execute it.
 - Do not create or switch sessions.
 - Summarize the returned objective state for the user.

package/dist/connectors/adapters/antigravity/skills/load.md

@@ -10,7 +10,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol load-context --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol load-context --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `load-context`, not `attach`.
 - Do not create or switch sessions.
 - Summarize the returned mission details, history, artifacts, and shared context for the user.

package/dist/connectors/adapters/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.26",
+  "version": "0.3.28",
   "description": "Overlord mission protocol workflow for Claude Code — attach/update/ask/deliver, slash commands, and hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/claude/commands/attach.md

@@ -12,7 +12,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol attach --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol attach --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `attach` only when the user explicitly wants this Claude session to execute mission work.
 - After the command succeeds, report the returned `SESSION_KEY`.
 - Follow the `overlord-mission` skill workflow after attaching: update while working, ask exactly one blocking question if blocked, and deliver last.

package/dist/connectors/adapters/claude/commands/connect.md

@@ -13,7 +13,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol connect --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol connect --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `connect`, not `attach`.
 - Do not load extra mission context unless the user explicitly asks for it.
 - After the command succeeds, report the returned `SESSION_KEY` and confirm that future updates should use that mission.

package/dist/connectors/adapters/claude/commands/discuss-objective.md

@@ -12,7 +12,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol discuss-objective --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol discuss-objective --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `discuss-objective`, not `attach`, when the user is opening or discussing a mission but has not asked Claude to execute it.
 - Do not create or switch sessions.
 - Summarize the returned objective state for the user.

package/dist/connectors/adapters/claude/commands/load.md

@@ -14,7 +14,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol load-context --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol load-context --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use `load-context`, not `attach`.
 - Do not create or switch sessions.
 - Summarize the returned mission details, history, artifacts, and shared context for the user.

package/dist/connectors/adapters/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.26",
+  "version": "0.3.28",
   "description": "Chat-driven access to Overlord mission protocol workflows with hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/cursor/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.26",
+  "version": "0.3.28",
   "description": "Overlord mission protocol workflow for Cursor — attach/update/ask/deliver, slash commands, MCP bridge, and follow-up capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/cursor/commands/attach.md

@@ -6,7 +6,12 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol attach --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol attach --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use attach only when the user explicitly wants this session to execute mission work.
 - After the command succeeds, report the returned `SESSION_KEY`.
 - Follow the `overlord-mission` skill workflow after attaching: update while working, ask exactly one blocking question if blocked, and deliver last.

package/dist/connectors/adapters/cursor/commands/connect.md

@@ -4,3 +4,10 @@ Use the text after `/connect` as the mission ID.
 
 Run:
 `ovld protocol connect --mission-id <missionId>`
+
+or, when the argument is an objective display id:
+
+`ovld protocol connect --objective-id <objectiveId>`
+
+Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.

package/dist/connectors/adapters/cursor/commands/discuss-objective.md

@@ -6,6 +6,11 @@ If no mission ID was provided, ask the user for one and stop.
 Run:
 `ovld protocol discuss-objective --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol discuss-objective --objective-id <objectiveId>`
+
 Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.
 - Use this when the user wants to open or discuss a mission, not execute it.
 - Do not attach after this command unless the user explicitly asks to execute.

package/dist/connectors/adapters/cursor/commands/load.md

@@ -5,5 +5,12 @@ Use the text after `/load` as the mission ID.
 Run:
 `ovld protocol load-context --mission-id <missionId>`
 
+or, when the argument is an objective display id:
+
+`ovld protocol load-context --objective-id <objectiveId>`
+
 When you open or discuss an existing mission that has a draft objective, submit it with:
 `ovld protocol discuss-objective --mission-id <missionId>`
+
+Rules:
+- The argument may be a mission display id (`coo:756`) or an objective display id (`coo:756.k7xm`). An objective display id already names its mission, so pass it as `--objective-id` on its own — do not split it or pass it as `--mission-id`.

package/dist/connectors/core/overlord-mission/SKILL.md

@@ -15,6 +15,8 @@ Use this mode when the prompt already contains a mission ID or explicitly says t
 
 **`<mission_id>` is always the short display id** — `coo:695`, `1:899`: a workspace prefix, a colon, and a number. Pass it as `--mission-id`. **`<objective_id>`** is the objective display id (`coo:695.k7xm`) or UUID; pass it as `--objective-id` when you know which objective to execute. Never pass an objective id as `--mission-id`. If the prompt includes `OVERLORD_OBJECTIVE_ID` or an Objective ID line, include `--objective-id` on attach. If the only id you can find is a bare UUID with no mission display id, re-read the prompt or run `ovld protocol search-missions` rather than guessing.
 
+**An objective display id is a complete address.** `coo:695.k7xm` already spells its mission, so `--mission-id` is optional on every command whenever you pass a full objective display id as `--objective-id`; Overlord derives `coo:695` from it. This is the identifier to reach for when reconnecting to a mission that is running more than one objective, where "the active objective" is ambiguous and a mission id alone is not enough. An objective **UUID** names no mission, so it still needs `--mission-id` alongside it.
+
 1. Attach first with `ovld protocol attach --mission-id <mission_id> [--objective-id <objective_id>]`.
 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.
 3. Treat the Overlord mission prompt as authoritative for the objective, constraints, and delivery target. Begin executing the current objective immediately after attach; do not wait for more instructions or ask for confirmation. This differs from `connect` or `load-context`, which only retrieve mission context and never imply the agent should act.
@@ -61,7 +63,7 @@ ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"obj
 
 Discussing or otherwise opening a mission from within a chat should cause the draft objective to be marked **submitted** — this signals the mission is in active discussion with an agent, but not yet being executed. Only an explicit order to execute (e.g. "execute this", "do this", "start working on it") should cause you to **attach** to the mission and trigger execution.
 
-- **Discussing / opening a mission** → `ovld protocol discuss-objective --mission-id $MISSION_ID` (draft → submitted, no session).
+- **Discussing / opening a mission** → `ovld protocol discuss-objective --mission-id $MISSION_ID` (draft → submitted, no session). Add `--objective-id <objective_id>` when the mission holds more than one draft and you mean a specific one.
 - **Creating a mission** via `ovld protocol create` keeps the objective in `draft` state.
 - **Explicitly ordered to execute** → `ovld protocol attach --mission-id $MISSION_ID` (draft/submitted → executing, session begins).
 
@@ -78,9 +80,9 @@ Use this mode when the conversation starts normally and the user asks the agent
    - If the user wants to **add more objectives to an existing mission** (not create a new mission), use `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"..."}]'` instead.
 2. Default to `create` for new missions. Only use `ovld protocol prompt --agent <agent-identifier> --objectives-json '[{"objective":"..."}]'` when the user explicitly asks to create and execute immediately.
    `prompt` creates the mission in `execute` status and attaches immediately.
-3. If the user already has a mission ID and only wants to inspect it, run `ovld protocol load-context --mission-id <mission_id>`.
+3. If the user already has a mission ID and only wants to inspect it, run `ovld protocol load-context --mission-id <mission_id>`. To read one specific objective's context — the only way to read context on a mission running objectives in parallel — add `--objective-id <objective_id>` (or pass it alone).
    When you open or discuss an existing mission that has a draft objective, submit it with `ovld protocol discuss-objective --mission-id <mission_id>`.
-4. If the user wants to route the current session onto an existing mission by ID, run `ovld protocol connect --mission-id <mission_id>`.
+4. If the user wants to route the current session onto an existing mission by ID, run `ovld protocol connect --mission-id <mission_id>` (add `--objective-id <objective_id>` to pin the session to a specific objective).
 5. If the user wants to establish a persistent session with a mission by ID, run `ovld protocol attach --mission-id <mission_id>`.
 6. If the user wants to find a mission but does not know the ID, run `ovld protocol search-missions --query "..." --status next-up,execute` and ask the user to confirm.
 7. If you need to understand project routing before prompting, use `ovld protocol discover-project`.
@@ -96,8 +98,13 @@ For mission creation examples, project discovery, and `--objectives-json` format
 
 ```bash
 ovld protocol attach --mission-id $MISSION_ID
+ovld protocol attach --mission-id $MISSION_ID --objective-id $OBJECTIVE_ID   # pin the objective
+ovld protocol attach --objective-id $OBJECTIVE_ID                            # display id only
 ```
 
+The third form works because an objective display id (`coo:695.k7xm`) already
+names its mission — use it when reconnecting and the mission id is not at hand.
+
 In a git workspace, `attach` records a VCS baseline (changed file paths from local `git status`) so delivery can compute the run-attributable delta automatically.
 
 ### Update
@@ -394,6 +401,7 @@ Field shape, inline vs stdin piping, and `record-change-rationales` syntax are i
 ## Rules
 
 - Always attach first and always deliver last once you are on a mission.
+- `--objective-id` is accepted anywhere `--mission-id` is, and a full objective display id (`coo:695.k7xm`) makes `--mission-id` optional. Prefer passing it on every call once you know which objective you are running, so events, artifacts, and file changes land on that objective rather than on whichever one Overlord would rediscover.
 - `attach` is itself the go-ahead to start work — proceed with implementation immediately after attaching, without pausing to ask the user whether to continue. Only `connect` or `load-context` are for inspection without action; do not treat `attach` the same way.
 - Use `ovld protocol` commands and the connector's native commands/tools instead of ad hoc scripts.
 - Do not invent protocol subcommands. Use `ovld protocol help` when unsure.

package/dist/connectors/core/overlord-mission/reference/cli.md

@@ -1,9 +1,33 @@
 # CLI Command Reference
 
+## Addressing a mission or an objective
+
+Every `ovld protocol` subcommand that takes `--mission-id` also takes
+`--objective-id`, and an objective **display** id (`coo:756.k7xm`) already names
+its mission — so `--mission-id` is optional whenever you pass one:
+
+```bash
+ovld protocol update --objective-id coo:756.k7xm --summary "..."      # mission derived
+ovld protocol update --mission-id coo:756 --objective-id coo:756.k7xm # same thing
+```
+
+Use the objective form when reconnecting to a mission that is running more than
+one objective: "the active objective" is ambiguous there, and commands that
+rediscover it (`attach`, `load-context`, `connect`) fail with
+`ambiguous_active_objective` until you name one.
+
+An objective **UUID** carries no parent mission, so it still needs
+`--mission-id` next to it. The CLI also fills `--objective-id` in from
+`OVERLORD_OBJECTIVE_ID` on session-scoped commands, so a launched agent rarely
+types it at all. Two commands deliberately never inherit it:
+`update-objective` (the id names the row being changed) and `discuss-objective`
+(it wants a draft, not the objective already executing).
+
 ## Attach
 
 ```bash
 ovld protocol attach --mission-id $MISSION_ID [--objective-id $OVERLORD_OBJECTIVE_ID]
+ovld protocol attach --objective-id coo:756.k7xm
 ```
 
 In a git workspace, `attach` records a VCS baseline (changed file paths from local `git status`) so delivery can compute the run-attributable delta automatically.

package/dist/connectors/core/overlord-mission/reference/context.md

@@ -12,7 +12,7 @@ ovld protocol attachment-upload-file --session-key <sessionKey> --objective-id <
 ovld protocol attachment-download-url --session-key <sessionKey> --attachment-id <attachment-id>
 ```
 
-The `attach` and `load-context` responses already include an `attachments` array plus `previousObjectives` and `futureObjectives` arrays — use those for `<attachment-id>` and `<objective-id>` values. The objective currently being executed is not repeated in those arrays; it is the top-level `objective`. `previousObjectives` are the objectives already worked (before the current one) and `futureObjectives` are the ones queued after it. Run `attachment-list` mid-session if new files have been uploaded since attach. `--mission-id` is optional for attachment calls when `--objective-id` or `--attachment-id` lets the server derive the mission.
+The `attach` and `load-context` responses already include an `attachments` array plus `previousObjectives` and `futureObjectives` arrays — use those for `<attachment-id>` and `<objective-id>` values. The objective currently being executed is not repeated in those arrays; it is the top-level `objective`. `previousObjectives` are the objectives already worked (before the current one) and `futureObjectives` are the ones queued after it. Run `attachment-list` mid-session if new files have been uploaded since attach. `--mission-id` is optional for attachment calls when `--objective-id` is a full display ID that lets the server derive the mission; an attachment ID alone does not carry mission scope.
 
 ## Creating artifacts during a turn
 
@@ -31,4 +31,3 @@ For large artifacts such as planning documents, architecture decisions, research
 - Prefer `add-artifact` mid-turn (or a delivery artifact) with a `note` or `decision` type, a concise summary, and the repository file path — not the full document content.
 
 This keeps the mission feed readable while preserving the full document in version control where it can be reviewed, diffed, and referenced later. If that summary artifact already exists on the mission, revise it with `update-artifact` rather than creating another copy.
-

package/dist/connectors/core/overlord-mission/reference/mcp.md

@@ -1,5 +1,6 @@
 # MCP And API Defaults
 
+- Every mission-scoped tool accepts `objectiveId` (hosted MCP) / `objective_id` (local shim) alongside `missionId`, taking an objective UUID or a display id such as `coo:756.k7xm`. A display id already names its mission, so `missionId` is **optional** whenever one is supplied — `overlord_load_mission_context`, `overlord_attach_session`, `overlord_update_session`, `overlord_deliver_session`, `overlord_add_artifact`, `overlord_add_objectives`, and `overlord_update_artifact` all resolve the mission from it. An objective **UUID** names no mission and still needs `missionId`. On `overlord_load_mission_context` and `overlord_attach_session` the objective is also a *pin*: it selects which objective to read or execute, which is the only way to address a mission that is running objectives in parallel.
 - API requires `agentIdentifier` and `connectionMethod` on attach/connect/prompt. Connector adapters set the appropriate agent identifier; the CLI uses `cli` as the connection method, and the MCP tool defaults to `mcp`. Override with `--agent` / `--method` when calling from a different runtime.
 - Hosted Overlord MCP (`/mcp`) uses camelCase JSON keys (`missionId`, `sessionKey`, `deviceFingerprint`) matching `POST /api/protocol/*` bodies. The local shim uses snake_case keys mapped to CLI flags (`mission_id`, `session_key`, `device_fingerprint`). Some local-only operations (`connect`, `revert`, `prompt`, runner queue tools) intentionally remain out of hosted MCP for now.
 - `discover_project` accepts an explicit project id (`projectId` hosted, `project_id` local shim) or a working directory (`workingDirectory` hosted, `working_directory` local shim). When resolving by directory and a device fingerprint is available, include `deviceFingerprint` / `device_fingerprint` so resource-directory matching prefers the current device.
@@ -7,8 +8,8 @@
 - Execution request tools (`request_execution`, `claim_execution`, `list_execution_requests`, `clear_execution_requests`, `complete_execution_launch`, `fail_execution_launch`) back the local runner queue. Agents normally work missions with `attach`/`update`/`deliver`; runner processes use these queue tools.
 - `record_change_rationales` (MCP) and `ovld protocol record-change-rationales` (CLI) both write to the same `file_changes` table. The dedicated CLI route is `POST /api/protocol/record-change-rationales`.
 - `overlord_record_work` (hosted MCP) and `ovld protocol record-work` (CLI) record already-completed chat work as a single review-column mission with a completed objective, file-change rationales, and the standard Gemini delivery summary — no `attach`/`deliver`. Hosted MCP requires `projectId` (it never chooses a project implicitly); the CLI resolves the project from the working directory or `--project-id`. The submission format is in [record-work.md](record-work.md). The route is `POST /api/protocol/record-work`.
-- `overlord_add_artifact` (hosted MCP) and `ovld protocol add-artifact` (CLI) create a mission artifact during a turn without delivering. Required: `missionId` / `--mission-id`, `type` / `--type`, `label` / `--label`, plus at least one of `contentText` / `--content-text`/`--content-text-file` or `externalUrl` / `--external-url`. Optional `sessionKey` / `--session-key` stamps session/objective provenance. Same service as REST `POST /api/missions/:id/artifacts`. The route is `POST /api/protocol/add-artifact`.
-- `overlord_update_artifact` (hosted MCP) and `ovld protocol update-artifact` (CLI) revise an existing mission artifact's label, Markdown content, and/or HTTP(S) URL in place. Required: `missionId` / `--mission-id`, `artifactId` / `--artifact-id`, `expectedRevision` / `--expected-revision`. Provide at least one editable field. No session key is required. Same service as REST `PATCH /api/missions/:id/artifacts/:artifactId`. The route is `POST /api/protocol/update-artifact`.
+- `overlord_add_artifact` (hosted MCP) and `ovld protocol add-artifact` (CLI) create a mission artifact during a turn without delivering. Required: `type` / `--type`, `label` / `--label`, mission scope (`missionId` / `--mission-id`, or an objective display id as `objectiveId` / `--objective-id`), plus at least one of `contentText` / `--content-text`/`--content-text-file` or `externalUrl` / `--external-url`. Optional `sessionKey` / `--session-key` stamps session/objective provenance; `objectiveId` / `--objective-id` does the same when there is no live session, and the session key wins if both are given. Same service as REST `POST /api/missions/:id/artifacts`. The route is `POST /api/protocol/add-artifact`.
+- `overlord_update_artifact` (hosted MCP) and `ovld protocol update-artifact` (CLI) revise an existing mission artifact's label, Markdown content, and/or HTTP(S) URL in place. Required: `artifactId` / `--artifact-id`, `expectedRevision` / `--expected-revision`, and mission scope (`missionId` / `--mission-id`, or an objective display id as `objectiveId` / `--objective-id`). Provide at least one editable field. No session key is required. Same service as REST `PATCH /api/missions/:id/artifacts/:artifactId`. The route is `POST /api/protocol/update-artifact`.
 - `overlord_create_mission` / `overlord_add_objectives` accept optional `autoAdvance` (boolean; default false). `overlord_update_objective` (`objectiveId` plus optional `autoAdvance` and/or `instructionText`) and `ovld protocol update-objective --objective-id <id>` with `--auto-advance|--no-auto-advance` and/or `--instruction-text|--instruction-text-file` update an existing objective. Instruction text is editable only in `draft` or `future` state. The route is `POST /api/protocol/update-objective`.
 - Objective attachment tools follow the `<verb>_<noun>` MCP naming: `list_attachments`, `prepare_attachment_upload`, `finalize_attachment_upload`, `get_attachment_download_url`, `upload_attachment_file`. CLI commands use `attachment-*`. `mission_id` / `missionId` is optional for attachment calls when the objective or attachment id lets the server derive mission scope.
 - "Artifacts" may be published mid-turn with `add-artifact` / `overlord_add_artifact`, revised with `update-artifact` / `overlord_update_artifact`, or attached at `deliver` time (next_steps, test_results, migration, decision, note, url) — not user-uploaded files. Files attached by users live on objectives via the attachment tools above.

package/dist/connectors/core/scripts/overlord-mcp.mjs

@@ -164,12 +164,17 @@ const tools = [
       'Load structured mission context, objectives, history, artifacts, and shared context.',
     inputSchema: objectSchema(
       {
-        missionId: stringProperty('Mission UUID or workspace display id such as coo:150.'),
+        missionId: stringProperty(
+          'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+        ),
+        objectiveId: stringProperty(
+          'Objective UUID or display id such as coo:756.k7xm. Returns that objective as the current one instead of rediscovering the mission active objective.'
+        ),
         executionTargetId: stringProperty(
           'Optional local execution target id for resolving sibling project resource paths.'
         )
       },
-      ['missionId']
+      []
     )
   },
   {
@@ -178,7 +183,12 @@ const tools = [
     description: 'Append one or more draft objectives to an existing mission.',
     inputSchema: objectSchema(
       {
-        missionId: stringProperty('Mission UUID or workspace display id.'),
+        missionId: stringProperty(
+          'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+        ),
+        objectiveId: stringProperty(
+          'Objective UUID or display id such as coo:756.k7xm. Used only to supply missionId when it is omitted.'
+        ),
         objectives: {
           type: 'array',
           description:
@@ -193,7 +203,7 @@ const tools = [
           })
         }
       },
-      ['missionId', 'objectives']
+      ['objectives']
     )
   },
   {
@@ -221,7 +231,9 @@ const tools = [
       'Attach an MCP-hosted agent session to a mission before update/ask/deliver. Pass objectiveId when the caller already knows which objective to execute.',
     inputSchema: objectSchema(
       {
-        missionId: stringProperty('Mission UUID or workspace display id.'),
+        missionId: stringProperty(
+          'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+        ),
         objectiveId: stringProperty(
           'Optional objective UUID or display id (e.g. coo:756.k7xm). Pins attach to that objective.'
         ),
@@ -231,7 +243,7 @@ const tools = [
           'Optional local execution target id for resolving sibling project resource paths.'
         )
       },
-      ['missionId']
+      []
     )
   },
   {
@@ -240,13 +252,18 @@ const tools = [
     description: 'Post an update, alert, decision, or discussion summary for an attached session.',
     inputSchema: objectSchema(
       {
-        missionId: stringProperty('Mission UUID or workspace display id.'),
+        missionId: stringProperty(
+          'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+        ),
+        objectiveId: stringProperty(
+          'Objective UUID or display id such as coo:756.k7xm. Supplies missionId when it is omitted; the session key still determines which objective the event lands on.'
+        ),
         sessionKey: stringProperty('Session key returned by overlord_attach_session.'),
         summary: stringProperty('Update text.'),
         phase: stringProperty('Optional protocol phase.'),
         eventType: stringProperty('Optional event type. Defaults to update.')
       },
-      ['missionId', 'sessionKey', 'summary']
+      ['sessionKey', 'summary']
     )
   },
   {
@@ -256,7 +273,12 @@ const tools = [
       'Deliver an attached session with explicit summary, optional change rationales, and optional human-action/tradeoff evidence.',
     inputSchema: objectSchema(
       {
-        missionId: stringProperty('Mission UUID or workspace display id.'),
+        missionId: stringProperty(
+          'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+        ),
+        objectiveId: stringProperty(
+          'Objective UUID or display id such as coo:756.k7xm. Supplies missionId when it is omitted; the session key still determines which objective is delivered.'
+        ),
         sessionKey: stringProperty('Session key returned by overlord_attach_session.'),
         summary: stringProperty('Delivery summary.'),
         artifacts: {
@@ -284,7 +306,7 @@ const tools = [
         deferredWork: { type: 'array', description: 'Intentionally deferred work.' },
         assumptions: { type: 'array', description: 'Material implementation assumptions.' }
       },
-      ['missionId', 'sessionKey', 'summary']
+      ['sessionKey', 'summary']
     )
   },
   {
@@ -294,7 +316,12 @@ const tools = [
       'Create a mission artifact during a turn without delivering (plan, notes, decision, URL). Provide type, label, and at least one of contentText or externalUrl. Optional sessionKey stamps provenance. Revise later with overlord_update_artifact.',
     inputSchema: objectSchema(
       {
-        missionId: stringProperty('Mission UUID or workspace display id.'),
+        missionId: stringProperty(
+          'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+        ),
+        objectiveId: stringProperty(
+          'Objective UUID or display id such as coo:756.k7xm. Stamps objective provenance when no live sessionKey is available.'
+        ),
         type: stringProperty(
           'Artifact type: test_results, next_steps, note, url, decision, or migration.'
         ),
@@ -303,7 +330,7 @@ const tools = [
         externalUrl: stringProperty('Optional HTTP(S) URL.'),
         sessionKey: stringProperty('Optional live session key from attach.')
       },
-      ['missionId', 'type', 'label']
+      ['type', 'label']
     )
   },
   {
@@ -313,7 +340,12 @@ const tools = [
       'Revise an existing mission artifact in place (label, Markdown content, and/or URL) using optimistic concurrency via expectedRevision.',
     inputSchema: objectSchema(
       {
-        missionId: stringProperty('Mission UUID or workspace display id.'),
+        missionId: stringProperty(
+          'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+        ),
+        objectiveId: stringProperty(
+          'Objective UUID or display id such as coo:756.k7xm. Used only to supply missionId when it is omitted.'
+        ),
         artifactId: stringProperty('Artifact id from mission context.'),
         expectedRevision: {
           type: 'number',
@@ -323,7 +355,7 @@ const tools = [
         contentText: stringProperty('Optional new Markdown/text content.'),
         externalUrl: stringProperty('Optional HTTP(S) URL.')
       },
-      ['missionId', 'artifactId', 'expectedRevision']
+      ['artifactId', 'expectedRevision']
     )
   },
   {
@@ -339,7 +371,8 @@ const tools = [
         title: stringProperty('Optional mission title.'),
         changeRationales: {
           type: 'array',
-          description: 'One entry per meaningful file change (filePath, label, summary, why, impact).'
+          description:
+            'One entry per meaningful file change (filePath, label, summary, why, impact).'
         },
         changedFiles: {
           type: 'array',
@@ -366,6 +399,26 @@ function requiredString(args, name) {
   return value;
 }
 
+/**
+ * Forward mission/objective addressing to the CLI. The CLI owns the shared
+ * `@overlord/contract` parser and derives a mission from a display id before it
+ * performs local bookkeeping or calls the backend, so this standalone shim
+ * does not carry a second copy of the public-id regex.
+ */
+function missionScopeFlags(args) {
+  const objectiveId = optionalString(args, 'objectiveId');
+  const missionId = optionalString(args, 'missionId');
+  if (!missionId && !objectiveId) {
+    throw new Error(
+      'Missing required argument: missionId (pass it, or an objective display id such as coo:756.k7xm as objectiveId)'
+    );
+  }
+  return {
+    ...(missionId ? { 'mission-id': missionId } : {}),
+    ...(objectiveId ? { 'objective-id': objectiveId } : {})
+  };
+}
+
 function callOverlordTool(name, args) {
   if (name === 'overlord_resolve_project') {
     return runProtocol('discover-project', {
@@ -425,7 +478,7 @@ function callOverlordTool(name, args) {
   }
   if (name === 'overlord_load_mission_context') {
     return runProtocol('load-context', {
-      'mission-id': requiredString(args, 'missionId'),
+      ...missionScopeFlags(args),
       ...(optionalString(args, 'executionTargetId')
         ? { 'execution-target-id': requiredString(args, 'executionTargetId') }
         : {})
@@ -434,7 +487,7 @@ function callOverlordTool(name, args) {
   if (name === 'overlord_add_objectives') {
     if (!Array.isArray(args.objectives)) throw new Error('objectives must be an array');
     return runProtocol('add-objectives', {
-      'mission-id': requiredString(args, 'missionId'),
+      ...missionScopeFlags(args),
       'objectives-json': args.objectives
     });
   }
@@ -446,17 +499,18 @@ function callOverlordTool(name, args) {
     }
     return runProtocol('update-objective', {
       'objective-id': requiredString(args, 'objectiveId'),
-      ...(hasAutoAdvance ? (args.autoAdvance ? { 'auto-advance': true } : { 'no-auto-advance': true }) : {}),
+      ...(hasAutoAdvance
+        ? args.autoAdvance
+          ? { 'auto-advance': true }
+          : { 'no-auto-advance': true }
+        : {}),
       ...(hasInstructionText ? { 'instruction-text': requiredString(args, 'instructionText') } : {})
     });
   }
   if (name === 'overlord_attach_session') {
     return runProtocol('attach', {
-      'mission-id': requiredString(args, 'missionId'),
+      ...missionScopeFlags(args),
       agent: optionalString(args, 'agent') ?? DEFAULT_AGENT,
-      ...(optionalString(args, 'objectiveId')
-        ? { 'objective-id': requiredString(args, 'objectiveId') }
-        : {}),
       ...(optionalString(args, 'model') ? { model: requiredString(args, 'model') } : {}),
       ...(optionalString(args, 'executionTargetId')
         ? { 'execution-target-id': requiredString(args, 'executionTargetId') }
@@ -465,7 +519,7 @@ function callOverlordTool(name, args) {
   }
   if (name === 'overlord_update_session') {
     return runProtocol('update', {
-      'mission-id': requiredString(args, 'missionId'),
+      ...missionScopeFlags(args),
       'session-key': requiredString(args, 'sessionKey'),
       summary: requiredString(args, 'summary'),
       ...(optionalString(args, 'phase') ? { phase: requiredString(args, 'phase') } : {}),
@@ -476,7 +530,7 @@ function callOverlordTool(name, args) {
   }
   if (name === 'overlord_deliver_session') {
     return runProtocol('deliver', {
-      'mission-id': requiredString(args, 'missionId'),
+      ...missionScopeFlags(args),
       'session-key': requiredString(args, 'sessionKey'),
       summary: requiredString(args, 'summary'),
       ...(args.noFileChanges === true ? { 'no-file-changes': true } : {}),
@@ -515,7 +569,7 @@ function callOverlordTool(name, args) {
       throw new Error('Provide at least one of contentText or externalUrl');
     }
     return runProtocol('add-artifact', {
-      'mission-id': requiredString(args, 'missionId'),
+      ...missionScopeFlags(args),
       type: requiredString(args, 'type'),
       label: requiredString(args, 'label'),
       ...(hasContentText ? { 'content-text': args.contentText } : {}),
@@ -536,7 +590,7 @@ function callOverlordTool(name, args) {
       throw new Error('Provide at least one of label, contentText, or externalUrl');
     }
     return runProtocol('update-artifact', {
-      'mission-id': requiredString(args, 'missionId'),
+      ...missionScopeFlags(args),
       'artifact-id': requiredString(args, 'artifactId'),
       'expected-revision': String(Math.trunc(args.expectedRevision)),
       ...(hasLabel ? { label: args.label } : {}),
@@ -590,7 +644,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.26' }
+          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.28' }
         }
       });
       continue;