overlord-cli 0.2609071353.0 → 0.2609080806.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.41
+0.3.43

package/dist/connectors/adapters/antigravity/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "134"
+contractVersion: "137"
 componentType: connector
 componentKey: antigravity
 label: "Antigravity Connector"

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

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

package/dist/connectors/adapters/antigravity/skills/add-objectives.md

@@ -9,4 +9,6 @@ Use this when the prompts are sequential steps toward the same feature or goal.
 Run:
 `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"Step one"},{"objective":"Step two"}]'`
 
+To assign an agent to the appended objectives, add `"agent":"<id>"` (and optional `"model"`) to each item, or pass `--objective-agent <id>` / `--objective-model <id>` as the default.
+
 Index 0 is the first newly added objective to execute; later indexes queue after it.

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

@@ -9,6 +9,8 @@ If it already contains flags such as `--title`, `--priority`, `--project-id`, `-
 Otherwise, treat the argument as the objective text and run:
 `ovld protocol create --agent antigravity --objectives-json '[{"objective":"<objective>"}]'`
 
+When the user names an agent for the work, assign it on the objective itself — add `"agent":"<id>"` (and optional `"model"`) to the objectives item, or pass `--objective-agent <id>` / `--objective-model <id>`. Never create the mission and then append a second objective just to name an agent.
+
 If no objective was provided, ask the user for one and stop.
 
 After the command succeeds, report the new `MISSION_ID`.

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.41",
+  "version": "0.3.43",
   "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/add-objectives.md

@@ -11,5 +11,7 @@ Use this when the prompts are sequential steps toward the same feature or goal.
 Run:
 `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"Step one"},{"objective":"Step two"}]'`
 
+To assign an agent to the appended objectives, add `"agent":"<id>"` (and optional `"model"`) to each item, or pass `--objective-agent <id>` / `--objective-model <id>` as the default.
+
 Index 0 is the first newly added objective to execute; later indexes queue after it.
 

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

@@ -12,6 +12,8 @@ If it already contains flags such as `--title`, `--priority`, `--project-id`, `-
 Otherwise, treat `$ARGUMENTS` as the objective text and run:
 `ovld protocol create --agent claude-code --objectives-json '[{"objective":"<objective>"}]'`
 
+When the user names an agent for the work, assign it on the objective itself — add `"agent":"<id>"` (and optional `"model"`) to the objectives item, or pass `--objective-agent <id>` / `--objective-model <id>`. Never create the mission and then append a second objective just to name an agent.
+
 If no objective was provided, ask the user for one and stop.
 
 After the command succeeds, report the new `MISSION_ID`.

package/dist/connectors/adapters/claude/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "134"
+contractVersion: "137"
 componentType: connector
 componentKey: claude
 label: "Claude Code Connector"

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

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

package/dist/connectors/adapters/codex/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "134"
+contractVersion: "137"
 componentType: connector
 componentKey: codex
 label: "Codex Connector"

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.41",
+  "version": "0.3.43",
   "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/add-objectives.md

@@ -5,4 +5,6 @@ Use this when the prompts are sequential steps toward the same feature or goal.
 Run:
 `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"Step one"},{"objective":"Step two"}]'`
 
+To assign an agent to the appended objectives, add `"agent":"<id>"` (and optional `"model"`) to each item, or pass `--objective-agent <id>` / `--objective-model <id>` as the default.
+
 Index 0 is the first newly added objective to execute; later indexes queue after it.

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

@@ -8,6 +8,8 @@ If it already contains flags such as `--title`, `--priority`, `--project-id`, `-
 Otherwise, treat the input as the objective text and run:
 `ovld protocol create --agent cursor --objectives-json '[{"objective":"<objective>"}]'`
 
+When the user names an agent for the work, assign it on the objective itself — add `"agent":"<id>"` (and optional `"model"`) to the objectives item, or pass `--objective-agent <id>` / `--objective-model <id>`. Never create the mission and then append a second objective just to name an agent.
+
 If no objective was provided, ask the user for one and stop.
 
 After the command succeeds, report the new `MISSION_ID`.

package/dist/connectors/adapters/cursor/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "134"
+contractVersion: "137"
 componentType: connector
 componentKey: cursor
 label: "Cursor Connector"

package/dist/connectors/adapters/opencode/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "134"
+contractVersion: "137"
 componentType: connector
 componentKey: opencode
 label: "OpenCode Connector"

package/dist/connectors/adapters/pi/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "134"
+contractVersion: "137"
 componentType: connector
 componentKey: pi
 label: "PI Connector"

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

@@ -29,8 +29,11 @@ Use this mode when the prompt already contains a mission ID or explicitly says t
 When review facts genuinely apply, you may add `deliveryReport.agentReport` through `--payload-json` / `--payload-file`: use
 `humanActions`, `tradeoffsMade`, `knownRisks`, `deferredWork`, and `assumptions`, with empty arrays
 when none apply. Human actions are concrete work a user must perform outside completed agent work;
-never include Git operations or routine review/testing. Tradeoffs record the implementation decision,
-alternatives considered, and rationale. These fields improve review visibility but never block delivery.
+never include Git operations or routine review/testing. Every human action needs `action`, `reason`,
+and `category`; add `command`, `verify`, and `link` whenever they exist so the operator can act
+without re-reading the delivery (see **Delivery Evidence** below). Tradeoffs record the
+implementation decision, alternatives considered, and rationale. These fields improve review
+visibility but never block delivery.
 
 For full command syntax, flags, phase values, and event types see **CLI Command Reference** below.
 
@@ -205,6 +208,46 @@ configure an external integration). Never list committing, pushing, opening a pu
 reviewing code, or ordinary tests. A tradeoff must state the decision, alternatives considered,
 and rationale. Omit the report when none of these facts apply.
 
+#### Writing a human action the operator can complete
+
+Human actions are collected across every mission into the Feed page's **Human actions** rail,
+where the operator reads them without the delivery context. Each item must stand alone:
+
+| Field      | Expected | What to write                                                                                  |
+| ---------- | -------- | ---------------------------------------------------------------------------------------------- |
+| `action`   | required | One imperative sentence naming the exact thing to do, where, and with what value.              |
+| `reason`   | expected | Why the step is needed and what breaks or stays incomplete until it is done.                   |
+| `category` | expected | `environment`, `database`, `deployment`, `codegen`, `packaging`, `external_service`, or `other`.|
+| `blocking` | optional | `true` when the delivered work does not function until this is done.                           |
+| `command`  | when known | The exact command, setting name, or value to apply, verbatim. Placeholders in `<angle brackets>`. |
+| `verify`   | when known | How the operator confirms it worked: a command to run, a URL to open, or the state to observe. |
+| `link`     | when known | An HTTP(S) URL or a repository-relative file path (never another URI scheme).                   |
+
+Vague (the operator has to rediscover everything):
+
+```json
+{ "action": "Set up the env var for Gemini." }
+```
+
+Good (the operator can finish it from the rail alone):
+
+```json
+{
+  "action": "Add GEMINI_API_KEY to the production backend service on Railway.",
+  "reason": "The delivery-compose worker falls back to the raw summary until a provider key is present.",
+  "category": "environment",
+  "blocking": false,
+  "command": "railway variables set GEMINI_API_KEY=<key> --service backend",
+  "verify": "The next delivery card shows a composed presentation instead of 'fallback' in the worker log.",
+  "link": ".env.example"
+}
+```
+
+Overlord also derives its own `deterministic_rule` actions from the changed paths (new
+migrations, `.env.example` changes, dependency manifests, CI workflow files) and always shows
+them, so leaving one out never hides it; reporting it yourself with a real `command` and
+`verify` replaces the generic wording with something the operator can follow.
+
 ### Change ledger health (diagnostic)
 
 Use this only to inspect or troubleshoot objective-ledger synchronization and hook health:
@@ -284,6 +327,7 @@ When creating missions from within a repository:
 - Add objectives to the same mission when each prompt is a sequential step toward the same feature or goal; use `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"..."}]'`.
 - `create` and `prompt` 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. `--auto-advance` / `--no-auto-advance` set the default when an item omits `autoAdvance` (default off).
 - `add-objectives` uses the same per-item `autoAdvance` field and `--auto-advance` / `--no-auto-advance` default.
+- **Assign the agent on the objectives you are already creating.** Every objective item on `create`, `prompt`, and `add-objectives` takes optional `"agent"` (and `"model"`, which requires an agent), and `--objective-agent <id>` / `--objective-model <id>` set the default for items that name no `agent` of their own. Never create a mission and then append a second objective just to name an agent — that leaves a duplicate objective behind. Note this is **not** `--agent`, which records who created the mission (and, on `prompt`, which agent attaches).
 - To change auto-advance on an existing objective: `ovld protocol update-objective --objective-id <id> --auto-advance` or `--no-auto-advance`.
 - `record-work` is different: it creates exactly one **completed** objective. It takes a single `--objective` (or positional / an `objective` field in `--payload-json`) plus a `--summary` and the file-change data — not `--objectives-json`. See [reference/record-work.md](reference/record-work.md).
 - `create`, `prompt`, `create-mission`, and `record-work` accept `--assigned-to <member>` to set the mission's human owner. Accepts a username, an email, a user-id UUID, or the `orgid:username` member ID. When omitted, the assignee defaults to the mission creator.
@@ -292,6 +336,12 @@ When creating missions from within a repository:
 ovld protocol create --agent <agent-identifier> --objectives-json '[{"objective":"Capture follow-up work from this repository"}]'
 ```
 
+```bash
+# One call: a draft mission whose first objective is already assigned to Codex.
+ovld protocol create --agent <agent-identifier> \
+  --objectives-json '[{"objective":"Implement the API","agent":"codex","model":"gpt-5.6-terra"},{"objective":"Add CLI docs","agent":"claude"}]'
+```
+
 ```bash
 ovld protocol prompt --agent <agent-identifier> --objectives-json '[{"objective":"Implement feature X"}]'
 ```

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

@@ -181,6 +181,7 @@ When creating missions from within a repository:
 - Add objectives to the same mission when each prompt is a sequential step toward the same feature or goal; use `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"..."}]'`.
 - `create` and `prompt` 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. `--auto-advance` / `--no-auto-advance` map each opted-in item to authoritative Run Queue membership (default off).
 - `add-objectives` uses the same per-item `autoAdvance` field and `--auto-advance` / `--no-auto-advance` mapping.
+- Every objective item on `create`, `prompt`, and `add-objectives` also takes optional `"agent"` and `"model"` (a model requires an agent), and `--objective-agent <id>` / `--objective-model <id>` set the default for items that name no `agent` of their own. Assign the agent on the objectives you are already creating rather than appending a second objective just to name one. `--objective-agent` is distinct from `--agent`, which records creation provenance (and, on `prompt`, the attaching agent).
 - Use `ovld protocol run-queue [--project-id <id|slug|name>|--objective-id <id>|--mission-id <id>] [--queue <id|name>]` to inspect live queues. Entry operations use `queue-objective --objective-id <id> [--queue <id|name>] [--after <queued-entry|objective>|--front|--position <rank>]`, `dequeue-objective --objective-id <id>`, and `reorder-run-queue --queue <id|name> --ordered-entries-json <json>`; they require `execution_request:create`. Queue-definition operations use `create-run-queue`, `update-run-queue`, `delete-run-queue`, and `reorder-project-run-queues`; they require `project:update` and therefore a full-scope token.
 - `record-work` creates exactly one **completed** objective from a single `--objective` (or positional / an `objective` field in `--payload-json`) plus a `--summary` and file-change data — it does not take `--objectives-json`. See [record-work.md](record-work.md).
 
@@ -188,6 +189,12 @@ When creating missions from within a repository:
 ovld protocol create --agent <agent-identifier> --objectives-json '[{"objective":"Capture follow-up work from this repository"}]'
 ```
 
+```bash
+# One call: a draft mission whose first objective is already assigned to Codex.
+ovld protocol create --agent <agent-identifier> \
+  --objectives-json '[{"objective":"Implement the API","agent":"codex","model":"gpt-5.6-terra"},{"objective":"Add CLI docs","agent":"claude"}]'
+```
+
 ```bash
 ovld protocol prompt --agent <agent-identifier> --objectives-json '[{"objective":"Implement feature X"}]'
 ```

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

@@ -264,6 +264,12 @@ const tools = [
         objective: stringProperty('Initial objective text.'),
         title: stringProperty('Optional mission title.'),
         resourceKey: stringProperty('Optional logical project resource key for the objective.'),
+        agent: stringProperty(
+          'Optional agent identifier to assign to the initial objective, such as codex or claude. Omitted leaves the project launch-preference default; set it here instead of appending a second objective just to name an agent.'
+        ),
+        model: stringProperty(
+          'Optional model identifier for the assigned agent. Requires agent; rejected without it.'
+        ),
         assignedTo: stringProperty(
           'Optional workspace member to own the mission (workspace_users.id, profile UUID, orgid:username, bare username, or email). Rejected when the member is not in the workspace; meaningless on the inbox fallback.'
         ),
@@ -622,7 +628,25 @@ const tools = [
         humanActions: {
           type: 'array',
           description:
-            'Concrete actions a human must perform; exclude Git operations and routine review/testing.'
+            'Concrete actions a human must perform; exclude Git operations and routine review/testing. ' +
+            'Each item needs action, reason, and category, plus command (exact command or setting), verify (how to confirm it worked), and link (HTTP(S) URL or repo-relative path) whenever they exist. ' +
+            'Vague: { action: "Set up the env var for Gemini." }. Good: { action: "Add GEMINI_API_KEY to the production backend service on Railway.", reason: "Compose falls back to the raw summary without it.", category: "environment", command: "railway variables set GEMINI_API_KEY=<key> --service backend", verify: "The next delivery card shows a composed presentation.", link: ".env.example" }.',
+          items: {
+            type: 'object',
+            properties: {
+              action: { type: 'string', description: 'Required. One imperative sentence: what, where, which value.' },
+              reason: { type: 'string', description: 'Expected. Why it is needed and what stays broken until done.' },
+              category: {
+                type: 'string',
+                description: 'Expected. environment, database, deployment, codegen, packaging, external_service, or other.'
+              },
+              blocking: { type: 'boolean', description: 'True when the delivered work does not function until this is done.' },
+              command: { type: 'string', description: 'Exact command, setting, or value to apply, verbatim.' },
+              verify: { type: 'string', description: 'How the operator confirms it worked.' },
+              link: { type: 'string', description: 'HTTP(S) URL or repository-relative file path.' }
+            },
+            required: ['action']
+          }
         },
         tradeoffsMade: {
           type: 'array',
@@ -830,6 +854,12 @@ async function callOverlordTool(name, args) {
       ...(optionalString(args, 'resourceKey')
         ? { resource: requiredString(args, 'resourceKey') }
         : {}),
+      ...(optionalString(args, 'agent')
+        ? { 'objective-agent': requiredString(args, 'agent') }
+        : {}),
+      ...(optionalString(args, 'model')
+        ? { 'objective-model': requiredString(args, 'model') }
+        : {}),
       ...(optionalString(args, 'assignedTo')
         ? { 'assigned-to': requiredString(args, 'assignedTo') }
         : {}),
@@ -1175,7 +1205,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.41' }
+          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.43' }
         }
       });
       continue;

package/dist/index.js

@@ -35542,7 +35542,7 @@ var init_zod = __esm({
 });
 
 // ../packages/core/dist/service/delivery-report.js
-var MAX_ITEMS, MAX_ALTERNATIVES, MAX_ACTION_LENGTH, MAX_DETAIL_LENGTH, humanActionCategorySchema, conciseTextSchema, humanActionSchema, tradeoffSchema, MAX_WARNINGS, normalizedHumanActionSchema, normalizedTradeoffSchema, normalizedAgentReportSchema, deliveryPresentationSchema, persistedDeliveryReportSchema;
+var MAX_ITEMS, MAX_ALTERNATIVES, MAX_ACTION_LENGTH, MAX_DETAIL_LENGTH, humanActionCategorySchema, MAX_COMMAND_LENGTH2, MAX_LINK_LENGTH, conciseTextSchema, commandTextSchema, LINK_PATTERN, linkSchema, humanActionSchema, tradeoffSchema, MAX_WARNINGS, normalizedHumanActionSchema, normalizedTradeoffSchema, normalizedAgentReportSchema, deliveryPresentationSchema, persistedDeliveryReportSchema;
 var init_delivery_report = __esm({
   "../packages/core/dist/service/delivery-report.js"() {
     "use strict";
@@ -35560,12 +35560,20 @@ var init_delivery_report = __esm({
       "external_service",
       "other"
     ]);
+    MAX_COMMAND_LENGTH2 = 600;
+    MAX_LINK_LENGTH = 400;
     conciseTextSchema = external_exports.string().trim().min(1).max(MAX_DETAIL_LENGTH);
+    commandTextSchema = external_exports.string().trim().min(1).max(MAX_COMMAND_LENGTH2);
+    LINK_PATTERN = /^(?:https?:\/\/\S+|(?![a-z][a-z0-9+.-]*:)[^\s<>"'`]+)$/i;
+    linkSchema = external_exports.string().trim().min(1).max(MAX_LINK_LENGTH).regex(LINK_PATTERN);
     humanActionSchema = external_exports.strictObject({
       action: external_exports.string().trim().min(1).max(MAX_ACTION_LENGTH),
       reason: conciseTextSchema.optional(),
       category: humanActionCategorySchema.optional(),
-      blocking: external_exports.boolean().optional()
+      blocking: external_exports.boolean().optional(),
+      command: commandTextSchema.optional(),
+      verify: conciseTextSchema.optional(),
+      link: linkSchema.optional()
     });
     tradeoffSchema = external_exports.strictObject({
       decision: external_exports.string().trim().min(1).max(MAX_ACTION_LENGTH),
@@ -35580,6 +35588,9 @@ var init_delivery_report = __esm({
       reason: conciseTextSchema.optional(),
       category: humanActionCategorySchema,
       blocking: external_exports.boolean().optional(),
+      command: commandTextSchema.optional(),
+      verify: conciseTextSchema.optional(),
+      link: linkSchema.optional(),
       source: external_exports.enum(["agent", "change_rationale", "deterministic_rule"]),
       sourceRef: external_exports.string().trim().min(1).max(200).optional()
     });
@@ -38379,10 +38390,13 @@ add-objectives:
   Optional:
     --auto-advance / --no-auto-advance
         Default auto-advance for items that omit "autoAdvance". Defaults to off.
+    --objective-agent <id> / --objective-model <id>
+        Default launch selection for items that name no "agent" of their own.
+        --objective-model requires --objective-agent.
   Notes:
     Each item is { "objective": "...", "title": "...", "agent": "codex",
     "model": "gpt-5.6-terra", "autoAdvance": true|false, "resourceKey": "..." }.
-    model requires agent. Per-item autoAdvance wins over the flag.
+    model requires agent. Per-item autoAdvance and agent win over the flags.
 
 update-objective:
   Purpose:
@@ -38441,6 +38455,12 @@ create:
     --auto-advance / --no-auto-advance
         Add matching objectives to the authoritative Run Queue. Defaults to off.
         Per-item override: "autoAdvance": true|false in --objectives-json items.
+    --objective-agent <id> / --objective-model <id>
+        Assign a launch agent (and its model) to the objectives created here, so
+        a mission can be created already assigned instead of appending a second
+        objective just to name an agent. This is not --agent, which records
+        creation provenance. Seeds only items with no "agent" of their own;
+        --objective-model requires --objective-agent.
 
 prompt:
   Purpose:
@@ -38457,6 +38477,9 @@ prompt:
     --auto-advance / --no-auto-advance
         Add matching objectives to the authoritative Run Queue. Defaults to off.
         Per-item override: "autoAdvance": true|false in --objectives-json items.
+    --objective-agent <id> / --objective-model <id>
+        Assign a launch agent (and its model) to the objectives created here.
+        Distinct from --agent, which names the attaching agent for the session.
   Returns:
     New mission/session JSON plus SESSION_KEY on stderr when available.
 
@@ -38544,6 +38567,21 @@ deliver:
     The payload may also include deliveryReport: { schemaVersion: 1, agentReport: {
       humanActions, tradeoffsMade, knownRisks, deferredWork, assumptions } }. Use empty arrays
     when none apply. Human actions exclude Git operations and routine review/testing.
+  Human action shape (each item in agentReport.humanActions):
+    {
+      "action":   "Add GEMINI_API_KEY to the production backend service on Railway.", // required. one imperative sentence: what, where, which value.
+      "reason":   "Compose falls back to the raw summary without it.",  // expected. why, and what stays broken until done.
+      "category": "environment",  // expected. environment | database | deployment | codegen | packaging | external_service | other
+      "blocking": false,          // optional. true when the delivered work does not function until this is done.
+      "command":  "railway variables set GEMINI_API_KEY=<key> --service backend", // when known. exact command/setting, verbatim.
+      "verify":   "Next delivery card shows a composed presentation.", // when known. how the operator confirms it worked.
+      "link":     ".env.example"  // when known. HTTP(S) URL or repo-relative path only.
+    }
+    Vague: { "action": "Set up the env var for Gemini." } forces the operator to rediscover
+    the name, the place, and the check. Actions are read from the Feed rail without the
+    delivery, so each must stand alone. Overlord adds deterministic_rule actions for new
+    migrations, .env.example edits, dependency manifests, and CI workflow files on its own;
+    report those yourself when you can supply the real command and verify step.
   Optional:
     --artifacts-json / --artifacts-file <path|->
     --change-rationales-json / --change-rationales-file <path|->
@@ -40493,17 +40531,25 @@ async function runManagementCommand({
         name: "--auto-advance",
         negatedName: "--no-auto-advance"
       });
+      const objectiveAgent = flagValue(parsed.flags, "--objective-agent")?.trim() || void 0;
+      const objectiveModel = flagValue(parsed.flags, "--objective-model")?.trim() || void 0;
+      if (objectiveModel && !objectiveAgent) {
+        throw new CliError({ message: "--objective-model requires --objective-agent" });
+      }
+      const withAgentSelection = (item) => objectiveAgent && !item.agent ? { ...item, agent: objectiveAgent, model: item.model ?? objectiveModel ?? null } : item;
       const parsedObjectives = objectivesJson ? JSON.parse(objectivesJson) : null;
-      const objectives = parsedObjectives ? parsedObjectives.map((item) => ({
-        ...item,
-        ...item.autoAdvance === void 0 && autoAdvance !== void 0 ? { autoAdvance } : {}
-      })) : objective ? [
-        {
+      const objectives = parsedObjectives ? parsedObjectives.map(
+        (item) => withAgentSelection({
+          ...item,
+          ...item.autoAdvance === void 0 && autoAdvance !== void 0 ? { autoAdvance } : {}
+        })
+      ) : objective ? [
+        withAgentSelection({
           objective,
           title: flagValue(parsed.flags, "--title") ?? null,
           ...autoAdvance !== void 0 ? { autoAdvance } : {},
           ...flagValue(parsed.flags, "--resource") ? { resourceKey: flagValue(parsed.flags, "--resource") } : {}
-        }
+        })
       ] : [];
       const first = objectives[0];
       if (!first) {
@@ -41496,6 +41542,8 @@ var COMMAND_FLAGS = {
     "--project-id",
     "--title",
     "--resource",
+    "--objective-agent",
+    "--objective-model",
     "--auto-advance",
     "--no-auto-advance"
   ],
@@ -41507,6 +41555,8 @@ var COMMAND_FLAGS = {
     "--title",
     "--resource",
     "--agent",
+    "--objective-agent",
+    "--objective-model",
     "--auto-advance",
     "--no-auto-advance"
   ],