overlord-cli 0.2607151113.0 → 0.2607151850.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.1
+0.3.2

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

@@ -1,7 +1,7 @@
 {
   "$schema": "https://antigravity.google/schemas/v1/plugin.json",
   "name": "overlord",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Chat-driven access to Overlord mission protocol workflows with hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/antigravity/scripts/overlord-mcp.mjs

@@ -328,7 +328,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-antigravity', version: '0.3.1' }
+          serverInfo: { name: 'overlord-antigravity', version: '0.3.2' }
         }
       });
       continue;

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "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/prompt-wrapper.md

@@ -5,13 +5,13 @@ Claude launch prompts should keep the mission objective compact and place large
 Recommended launch shape:
 
 ```bash
-claude --append-system-prompt-file <context-file> --model <model> --effort <level> "Begin working on this mission."
+claude --append-system-prompt-file <context-file> --model <model> --effort <level> "Attach, then immediately execute this mission's current objective."
 ```
 
 Rules:
 
 - The context file should contain the Overlord mission prompt, objective metadata, history, artifacts, attachments, and shared context assembled by the protocol layer.
-- The visible user prompt should point Claude at the context file and name the active mission ID; for normal execution this is a short instruction such as `Begin working on this mission.`
+- The visible user prompt should point Claude at the context file, name the active mission ID, and explicitly direct execution without waiting for confirmation.
 - `--model` is passed only when the execution target has a model configured.
 - `--effort` is passed only when the installed Claude binary supports it and the execution target has an effort level configured.
 - Do not embed secrets in the prompt wrapper. Authentication comes from shared `ovld auth` credentials, Overlord-launched environment variables, `Overlord_USER_TOKEN` / `OVLD_USER_TOKEN`, or the Claude plugin `user_token` config passed to `ovld protocol` as `Overlord_USER_TOKEN`.

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

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

package/dist/connectors/adapters/codex/prompt-wrapper.md

@@ -5,13 +5,13 @@ Codex launch prompts should keep the mission objective compact and pass model an
 Recommended launch shape:
 
 ```bash
-codex [--model <model>] [-c model_reasoning_effort="<level>"] "Begin working on this mission."
+codex [--model <model>] [-c model_reasoning_effort="<level>"] "Attach, then immediately execute this mission's current objective."
 ```
 
 Rules:
 
 - The assembled Overlord mission prompt, objective metadata, history, artifacts, attachments, and shared context should be injected as the initial session prompt by the protocol layer.
-- The visible user prompt should name the active mission ID; for normal execution this is a short instruction such as `Begin working on this mission.`
+- The visible user prompt should name the active mission ID and explicitly direct execution without waiting for confirmation.
 - `--model` is passed only when the execution target has a model configured.
 - `-c model_reasoning_effort="<level>"` is passed only when the execution target has an effort level configured.
 - For large context, write a context file and pass a short prompt that points Codex at it.

package/dist/connectors/adapters/codex/scripts/overlord-mcp.mjs

@@ -328,7 +328,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-codex', version: '0.3.1' }
+          serverInfo: { name: 'overlord-codex', version: '0.3.2' }
         }
       });
       continue;

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "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/scripts/overlord-mcp.mjs

@@ -328,7 +328,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-cursor', version: '0.3.1' }
+          serverInfo: { name: 'overlord-cursor', version: '0.3.2' }
         }
       });
       continue;

package/dist/connectors/adapters/pi/prompt-wrapper.md

@@ -3,7 +3,7 @@
 PI receives Overlord's generated mission context as a native file input and a short visible launch message:
 
 ```bash
-pi --model <provider/id> --thinking <level> @<context-file> "Start work on <mission>."
+pi --model <provider/id> --thinking <level> @<context-file> "Attach, then immediately execute <mission>'s current objective."
 ```
 
 Rules:
@@ -12,3 +12,4 @@ Rules:
 - Pass thinking separately with `--thinking` only when the selected launch configuration specifies it.
 - Place user-configured launch flags before the `@<context-file>` and visible message arguments.
 - The context file contains the mission, objectives, history, artifacts, attachments, and lifecycle instructions. Do not put credentials in it.
+- The visible message must explicitly direct execution without waiting for confirmation.

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

@@ -15,7 +15,7 @@ Use this mode when the prompt already contains a mission ID or explicitly says t
 
 1. Attach first with `ovld protocol attach --mission-id <mission_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 implementing the objective immediately after attach. This differs from `connect` or `load-context`, which only retrieve mission context and never imply the agent should act.
+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.
 4. Post updates while working: `ovld protocol update --session-key <sessionKey> --mission-id <mission_id> --summary "..." --phase execute`.
    During long mechanical stretches with nothing meaningful to post, send `ovld protocol heartbeat --session-key <sessionKey> --mission-id <mission_id> [--phase execute] [--percent <0-100>] [--note "..."]` instead of an empty update.
 5. Follow-up messages after the initial mission are captured automatically by the installed `UserPromptSubmit` hook and stay in discussion intent while the mission is in review. Do not post `user_follow_up` manually unless the hook is unavailable.
@@ -29,6 +29,7 @@ For full command syntax, flags, phase values, and event types see **CLI Command
 **Missions** represent whole features or goals. **Objectives** are the individual steps to implement that goal — one objective equals one agent prompt.
 
 Example:
+
 ```
 Mission: add CLI command for editing user profile
  - Objective 1: draft plan for this command
@@ -38,10 +39,12 @@ Mission: add CLI command for editing user profile
 ```
 
 When to create a mission vs an objective:
+
 - **Create a new mission** when the user describes a distinct feature, bug, or goal that stands on its own.
 - **Add objectives to an existing mission** when the work is a sequential step toward the same feature or goal already tracked in a mission.
 
 To add further objectives to an existing mission (Mode 2):
+
 ```
 ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"..."},{"objective":"..."}]'
 ```
@@ -343,7 +346,7 @@ If `.overlord/project.json` contains more than one project, show the user the pr
 
 ## Change Rationales
 
-Always include `changeRationales` when delivering; optionally on updates during long-running work. Your job is rationale for *what* changed and why — the CLI captures *which* files changed (see **Deliver** above).
+Always include `changeRationales` when delivering; optionally on updates during long-running work. Your job is rationale for _what_ changed and why — the CLI captures _which_ files changed (see **Deliver** above).
 
 - Rationales only for meaningful behavioral changes you made for this mission; skip formatting-only noise. Do not send `file_changes` as an artifact.
 - Do not include unrelated worktree changes in the delivery report, payload, artifacts, or rationales — even to label them pre-existing.

package/dist/index.js

@@ -13820,6 +13820,7 @@ async function loadMissionContext({
     "",
     "## Instructions",
     "Use the Overlord skill. Follow the required protocol workflow.",
+    EXECUTION_DIRECTIVE,
     "",
     "## Objectives",
     ...objectives.map((objective, index) => {
@@ -13938,7 +13939,7 @@ Execution request: ${options.executionRequestId}` : context.launchContext;
     executionRequestId: options.executionRequestId,
     projectResources
   });
-  const prompt = launchContext.length > 4e3 ? `Use the Overlord context file at ${contextFile} and attach to mission ${context.displayId}.` : launchContext;
+  const prompt = launchContext.length > 4e3 ? `Read the Overlord context file at ${contextFile}, attach to mission ${context.displayId}, then immediately execute its current objective. Do not wait for more instructions.` : launchContext;
   const command = buildAgentCommand({
     agent: options.agent,
     model: options.model,
@@ -13946,7 +13947,7 @@ Execution request: ${options.executionRequestId}` : context.launchContext;
     flags: options.flags,
     prompt,
     contextFile,
-    launchMessage: `Start work on ${context.title} (ovld mission ${context.displayId})`
+    launchMessage: `Attach to ovld mission ${context.displayId}, then immediately execute ${context.title}. Do not wait for more instructions.`
   });
   const terminalScriptPath = options.terminalLauncher?.trim() ? launchScriptPath({
     tmpDir,
@@ -14012,7 +14013,7 @@ async function launchAgent({
   });
   return { plan, status: result.status, signal: result.signal };
 }
-var AGENT_HISTORY_EXCLUDED_EVENT_TYPES;
+var AGENT_HISTORY_EXCLUDED_EVENT_TYPES, EXECUTION_DIRECTIVE;
 var init_launch = __esm({
   "src/launch.ts"() {
     "use strict";
@@ -14024,6 +14025,7 @@ var init_launch = __esm({
       "execution_requested",
       "awaiting_approval"
     ]);
+    EXECUTION_DIRECTIVE = "This is an execution session. After attaching, immediately execute the current objective. Do not wait for more instructions or ask for confirmation; only stop to ask a question when blocked.";
   }
 });