overlord-cli 0.2607151113.0 → 0.2607161024.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.1
+0.3.3

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.3",
   "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.3' }
         }
       });
       continue;

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "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.3",
   "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.3' }
         }
       });
       continue;

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

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

@@ -29,7 +29,7 @@ From an OpenOverlord checkout:
 ovld agent-setup cursor
 ```
 
-This copies managed plugin files to `~/.cursor/plugins/local/overlord`, merges a `beforeSubmitPrompt` hook into `~/.cursor/hooks.json`, and adds a `Shell(ovld protocol:*)` permission allow rule to `~/.cursor/settings.json` when missing.
+This copies managed plugin files to `~/.cursor/plugins/local/overlord`, merges Overlord's prompt, permission, tool-result, and stop hooks into `~/.cursor/hooks.json`, and adds a `Shell(ovld protocol:*)` permission allow rule to `~/.cursor/settings.json` when missing. Existing hooks and settings are preserved.
 
 Re-run safely any time the connector contract version changes:
 
@@ -76,9 +76,14 @@ This connector is intentionally reviewable against the four connector layers in
 - `skills/overlord-mission/SKILL.md` — Cursor adapter template with a `<!-- @connector-core -->` marker; setup interpolates shared core content at install time.
 - `commands/*.md` — slash commands for session routing, objective discussion, mission creation, and work recording.
 - `hooks/overlord-user-prompt-submit.sh` — `beforeSubmitPrompt` follow-up capture through `ovld protocol hook-event`.
+- `hooks/overlord-permission-request.sh` — observes `beforeShellExecution` and `beforeMCPExecution` through `ovld protocol permission-request`. It returns no allow/deny decision, leaving Cursor and user-installed hooks authoritative.
+- `hooks/overlord-post-tool-use.sh` — records `postToolUse` file edits and shell-mediated changes for exact per-session delivery attribution.
+- `hooks/overlord-stop.sh` — checks pending delivery through `ovld protocol hook-event`; when needed, it asks Cursor to continue once so the agent can finish delivery.
 - `rules/overlord-local.mdc` — always-on workflow rules for Cursor sessions.
 - `mcp.json` + `scripts/overlord-mcp.mjs` — MCP bridge to common `ovld protocol` operations.
 - `conformance-manifest.yaml` — connector conformance declaration for the Overlord contract.
 - `prompt-wrapper.md` — Cursor launch guidance.
 
 The shared Connector Core source lives at `connectors/core/overlord-mission`. `ovld agent-setup cursor` interpolates that core into the adapter skill template and installs core reference files so the runtime package is self-contained.
+
+Cursor's generic `preToolUse` hook is intentionally not used for permission capture. Cursor currently documents that `ask` is not enforced for `preToolUse`; the narrower shell and MCP hooks expose the native permission-decision schema without changing the user's policy. Cursor also documents hook execution as fail-open by default, so Overlord telemetry failures do not strand the agent.

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

@@ -8,11 +8,17 @@ connector:
   agentIdentifier: cursor
   capabilities:
     - followUpHook
+    - permissionHook
+    - stopHook
+    - editHook
     - modelFlag
     - permissionRules
     - slashCommands
   hookTypes:
     - UserPromptSubmit
+    - PermissionRequest
+    - PostToolUse
+    - Stop
   installPath: "~/.cursor/plugins/local/overlord"
   managedFiles:
     - ".cursor-plugin/plugin.json"
@@ -27,6 +33,9 @@ connector:
     - "commands/record-work.md"
     - "commands/spawn.md"
     - "hooks/overlord-user-prompt-submit.sh"
+    - "hooks/overlord-permission-request.sh"
+    - "hooks/overlord-post-tool-use.sh"
+    - "hooks/overlord-stop.sh"
     - "mcp.json"
     - "prompt-wrapper.md"
     - "rules/overlord-local.mdc"

package/dist/connectors/adapters/cursor/hooks/overlord-permission-request.sh

@@ -0,0 +1,25 @@
+#!/bin/bash
+# Overlord Cursor permission observation hook.
+#
+# Cursor invokes this script from beforeShellExecution and beforeMCPExecution,
+# its native permission-decision points. The hook records the request through
+# the Connector -> Protocol surface but intentionally returns no decision, so
+# Cursor's own permissions and any other user hooks remain authoritative.
+
+BODY=$(cat -)
+
+if [ -n "${MISSION_ID:-}" ] && command -v ovld >/dev/null 2>&1; then
+  (
+    USER_TOKEN="${Overlord_USER_TOKEN:-${OVLD_USER_TOKEN:-}}"
+    if [ -n "$USER_TOKEN" ]; then
+      export Overlord_USER_TOKEN="$USER_TOKEN"
+    fi
+    printf '%s' "$BODY" | ovld protocol permission-request \
+      --mission-id "$MISSION_ID" \
+      --payload-file - \
+      >/dev/null 2>&1
+  ) &
+  disown
+fi
+
+exit 0

package/dist/connectors/adapters/cursor/hooks/overlord-post-tool-use.sh

@@ -0,0 +1,23 @@
+#!/bin/bash
+# Overlord Cursor postToolUse hook.
+# Records Cursor Write/Edit and Shell effects in the per-session touched-files
+# log used by `ovld protocol deliver` for concurrent-work attribution.
+
+BODY=$(cat -)
+LOG_DIR="${HOME:-}/.ovld/logs"
+LOG_FILE="${LOG_DIR}/cursor-post-tool-use-hook.log"
+
+log_hook() {
+  mkdir -p "$LOG_DIR" 2>/dev/null || return 0
+  printf '%s [cursor-post-tool-use] %s\n' "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" "$1" >>"$LOG_FILE" 2>/dev/null || true
+}
+
+if ! command -v ovld >/dev/null 2>&1; then
+  log_hook "ovld not on PATH; skipping"
+  exit 0
+fi
+
+RESULT=$(printf '%s' "$BODY" | ovld protocol record-touched 2>>"$LOG_FILE")
+log_hook "record-touched: ${RESULT:-<no output>}"
+
+exit 0

package/dist/connectors/adapters/cursor/hooks/overlord-stop.sh

@@ -0,0 +1,73 @@
+#!/bin/bash
+# Overlord Cursor stop hook.
+# Checks whether the attached mission still needs delivery and, at most once,
+# asks Cursor to continue so the agent can deliver. It never delivers itself.
+
+BODY=$(cat -)
+LOG_DIR="${HOME:-}/.ovld/logs"
+LOG_FILE="${LOG_DIR}/cursor-stop-hook.log"
+
+log_hook() {
+  mkdir -p "$LOG_DIR" 2>/dev/null || return 0
+  printf '%s [cursor-stop] %s\n' "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" "$1" >>"$LOG_FILE" 2>/dev/null || true
+}
+
+if [ -z "${MISSION_ID:-}" ] || ! command -v ovld >/dev/null 2>&1; then
+  log_hook "missing required mission or ovld, skipping"
+  printf '{}'
+  exit 0
+fi
+
+LOOP_COUNT=$(printf '%s' "$BODY" | python3 -c '
+import json, sys
+try:
+    value = json.load(sys.stdin).get("loop_count", 0)
+    print(value if isinstance(value, int) else 0)
+except Exception:
+    print(0)
+' 2>/dev/null)
+
+if [ "${LOOP_COUNT:-0}" -gt 0 ]; then
+  log_hook "automatic follow-up already used, skipping"
+  printf '{}'
+  exit 0
+fi
+
+RESPONSE_FILE=$(mktemp "${TMPDIR:-/tmp}/overlord-cursor-stop.XXXXXX")
+USER_TOKEN="${Overlord_USER_TOKEN:-${OVLD_USER_TOKEN:-}}"
+if [ -n "$USER_TOKEN" ]; then
+  export Overlord_USER_TOKEN="$USER_TOKEN"
+fi
+
+ovld protocol hook-event \
+  --hook-type Stop \
+  --mission-id "$MISSION_ID" \
+  >"$RESPONSE_FILE" 2>/dev/null
+OVLD_EXIT=$?
+
+if [ "$OVLD_EXIT" -eq 0 ]; then
+  python3 - "$RESPONSE_FILE" <<'PY'
+import json, sys
+
+response = {}
+try:
+    with open(sys.argv[1]) as handle:
+        data = json.load(handle)
+    status = data.get("deliveryStatus") or {}
+    if status.get("needed"):
+        reason = status.get("reason") or "Pending Overlord delivery work detected."
+        response["followup_message"] = (
+            f"[Overlord] {reason} Complete the required verification and deliver the attached mission now."
+        )
+except Exception:
+    pass
+
+print(json.dumps(response, separators=(",", ":")))
+PY
+else
+  log_hook "hook-event failed exit=$OVLD_EXIT"
+  printf '{}'
+fi
+
+rm -f "$RESPONSE_FILE"
+exit 0

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.3' }
         }
       });
       continue;

package/dist/connectors/adapters/cursor/skills/overlord-mission/SKILL.md

@@ -10,6 +10,9 @@ description: Cursor adapter for the shared Overlord mission workflow.
 - Agent identifier: `cursor` for `ovld protocol create` and `ovld protocol prompt`.
 - Native commands: `/attach`, `/connect`, `/load`, `/create`, `/prompt`, `/discuss-objective`, `/add-objectives`, `/record-work`.
 - Follow-up capture: the installed `beforeSubmitPrompt` hook records ordinary post-delivery user messages. Do not manually publish `user_follow_up` unless the hook is unavailable.
+- Permission capture: installed `beforeShellExecution` and `beforeMCPExecution` hooks publish permission activity through `ovld protocol` without overriding Cursor's own decision.
+- Edit capture: the installed `postToolUse` hook records Cursor file and shell effects for exact delivery attribution.
+- Stop hook: the installed `stop` hook may auto-submit one pending-delivery reminder but does not deliver for you.
 - MCP bridge: the installed `overlord` MCP server exposes the hosted-compatible `overlord_*` mission tool catalog backed by `ovld protocol`.
 - Authentication: use shared `ovld auth` credentials, Overlord-launched environment variables, or `Overlord_USER_TOKEN` / `OVLD_USER_TOKEN`.
 

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/connectors/docs/05-connectors-and-agent-plugins.md

@@ -99,6 +99,9 @@ Requirements:
 
 - Install local Cursor plugin/rules/commands.
 - Add `beforeSubmitPrompt` hook to record follow-ups.
+- Map `beforeShellExecution` and `beforeMCPExecution` onto the canonical observational `PermissionRequest` hook without overriding Cursor's permission decision.
+- Add `postToolUse` edit capture for file tools and shell-mediated changes.
+- Add a bounded `stop` hook for pending-delivery reminders.
 - Add permission allow rules for protocol commands.
 - Launch with model flag where supported.
 - No thinking/effort flag required initially.

package/dist/connectors/docs/testing.md

@@ -27,10 +27,10 @@ For each connector's `conformance-manifest.yaml`
   `componentType: connector`, valid `componentKey`, required `connector` block with
   `agentIdentifier` + `capabilities`.
 - Every `capabilities` value is in `approvedConnectorCapabilities`
-  (`followUpHook`, `permissionHook`, `stopHook`, `nativeResume`, `modelFlag`,
+  (`followUpHook`, `permissionHook`, `stopHook`, `editHook`, `nativeResume`, `modelFlag`,
   `effortFlag`, `contextFilePrompt`, `permissionRules`, `slashCommands`).
 - Every `hookTypes` value is in `approvedHookTypes`
-  (`UserPromptSubmit`, `PermissionRequest`, `Stop`).
+  (`UserPromptSubmit`, `PermissionRequest`, `PostToolUse`, `Stop`).
 - `contractVersion` is a known contract version.
 - `agentIdentifier` is a documented or namespaced connector identifier (open vocab).
 

package/dist/contract/conformance-manifest.schema.yaml

@@ -80,6 +80,7 @@ properties:
             - followUpHook
             - permissionHook
             - stopHook
+            - editHook
             - nativeResume
             - modelFlag
             - effortFlag
@@ -95,6 +96,7 @@ properties:
           enum:
             - UserPromptSubmit
             - PermissionRequest
+            - PostToolUse
             - Stop
         uniqueItems: true
       managedFiles:

package/dist/index.js

@@ -1,3 +1,5 @@
+import { createRequire } from 'node:module';
+const require = createRequire(import.meta.url);
 // Overlord CLI bundle — generated by cli/scripts/build.mjs. Do not edit.
 var __create = Object.create;
 var __defProp = Object.defineProperty;
@@ -2421,18 +2423,56 @@ function configureCursorHarness({
   };
   const hookRoot = hooks.hooks;
   const hookEntries = hookRoot && typeof hookRoot === "object" && !Array.isArray(hookRoot) ? hookRoot : {};
-  const beforeSubmit = Array.isArray(hookEntries.beforeSubmitPrompt) ? [...hookEntries.beforeSubmitPrompt] : [];
-  const alreadyInstalled = beforeSubmit.some((entry) => {
-    if (!entry || typeof entry !== "object") return false;
-    const command = entry.command;
-    return typeof command === "string" && command.includes("overlord-user-prompt-submit");
-  });
-  if (!alreadyInstalled) {
-    beforeSubmit.push({ command: CURSOR_HOOK_COMMAND });
-    hookEntries.beforeSubmitPrompt = beforeSubmit;
+  const mergeHook = ({
+    event,
+    command,
+    marker,
+    extra = {}
+  }) => {
+    const entries = Array.isArray(hookEntries[event]) ? [...hookEntries[event]] : [];
+    const alreadyInstalled = entries.some((entry) => {
+      if (!entry || typeof entry !== "object") return false;
+      const installedCommand = entry.command;
+      return typeof installedCommand === "string" && installedCommand.includes(marker);
+    });
+    if (alreadyInstalled) return false;
+    entries.push({ command, ...extra });
+    hookEntries[event] = entries;
+    return true;
+  };
+  const installedHookEvents = [
+    mergeHook({
+      event: "beforeSubmitPrompt",
+      command: CURSOR_HOOK_COMMANDS.beforeSubmitPrompt,
+      marker: "overlord-user-prompt-submit"
+    }) && "beforeSubmitPrompt",
+    mergeHook({
+      event: "beforeShellExecution",
+      command: CURSOR_HOOK_COMMANDS.beforePermission,
+      marker: "overlord-permission-request"
+    }) && "beforeShellExecution",
+    mergeHook({
+      event: "beforeMCPExecution",
+      command: CURSOR_HOOK_COMMANDS.beforePermission,
+      marker: "overlord-permission-request"
+    }) && "beforeMCPExecution",
+    mergeHook({
+      event: "postToolUse",
+      command: CURSOR_HOOK_COMMANDS.postToolUse,
+      marker: "overlord-post-tool-use",
+      extra: { matcher: "Shell|Write|Edit|MultiEdit|NotebookEdit" }
+    }) && "postToolUse",
+    mergeHook({
+      event: "stop",
+      command: CURSOR_HOOK_COMMANDS.stop,
+      marker: "overlord-stop",
+      extra: { loop_limit: 1 }
+    }) && "stop"
+  ].filter((event) => Boolean(event));
+  if (installedHookEvents.length > 0) {
     hooks.hooks = hookEntries;
     if (dryRun) {
-      warnings.push(`Would merge beforeSubmitPrompt hook into ${hooksPath}.`);
+      warnings.push(`Would merge ${installedHookEvents.join(", ")} hooks into ${hooksPath}.`);
     } else {
       mkdirSync3(cursorDir, { recursive: true });
       writeFileSync3(hooksPath, `${JSON.stringify(hooks, null, 2)}
@@ -2863,7 +2903,7 @@ function inspectConnector({
     problems
   };
 }
-var CURSOR_HOOK_COMMAND, CURSOR_PROTOCOL_PERMISSION, CODEX_PLUGIN_KEY, CODEX_RULES_START, CODEX_RULES_END, CLAUDE_MARKETPLACE_NAME, CLAUDE_PLUGIN_KEY;
+var CURSOR_HOOK_COMMANDS, CURSOR_PROTOCOL_PERMISSION, CODEX_PLUGIN_KEY, CODEX_RULES_START, CODEX_RULES_END, CLAUDE_MARKETPLACE_NAME, CLAUDE_PLUGIN_KEY;
 var init_connectors = __esm({
   "src/connectors.ts"() {
     "use strict";
@@ -2871,7 +2911,12 @@ var init_connectors = __esm({
     init_config();
     init_connector_core_render();
     init_errors();
-    CURSOR_HOOK_COMMAND = "plugins/local/overlord/hooks/overlord-user-prompt-submit.sh";
+    CURSOR_HOOK_COMMANDS = {
+      beforeSubmitPrompt: "plugins/local/overlord/hooks/overlord-user-prompt-submit.sh",
+      beforePermission: "plugins/local/overlord/hooks/overlord-permission-request.sh",
+      postToolUse: "plugins/local/overlord/hooks/overlord-post-tool-use.sh",
+      stop: "plugins/local/overlord/hooks/overlord-stop.sh"
+    };
     CURSOR_PROTOCOL_PERMISSION = "Shell(ovld protocol:*)";
     CODEX_PLUGIN_KEY = "overlord@overlord-local";
     CODEX_RULES_START = "# overlord:permissions:start";
@@ -13820,6 +13865,7 @@ async function loadMissionContext({
     "",
     "## Instructions",
     "Use the Overlord skill. Follow the required protocol workflow.",
+    EXECUTION_DIRECTIVE,
     "",
     "## Objectives",
     ...objectives.map((objective, index) => {
@@ -13938,7 +13984,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 +13992,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 +14058,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 +14070,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.";
   }
 });
 
@@ -15485,7 +15532,7 @@ function recordTouchedFromPayload({
     missionId = resolved.missionId;
     ambiguous = resolved.ambiguous;
   }
-  if (toolName === "Bash") {
+  if (toolName === "Bash" || toolName === "Shell") {
     const { addedCount } = recordBashObservedChanges({ workingDirectory, missionId });
     return { recorded: true, missionId, ambiguous, files: addedCount };
   }
@@ -16616,7 +16663,17 @@ async function runProtocolCommand({
   if (subcommand === "deliver" && missionId) {
     clearCachedSessionKey({ missionId, workingDirectory });
     removeActiveSession({ workingDirectory, missionId });
-    const connectorInstallsEditHook = existsSync22(path26.join(os5.homedir(), ".claude"));
+    const connectorInstallsEditHook = existsSync22(path26.join(os5.homedir(), ".claude")) || existsSync22(
+      path26.join(
+        os5.homedir(),
+        ".cursor",
+        "plugins",
+        "local",
+        "overlord",
+        "hooks",
+        "overlord-post-tool-use.sh"
+      )
+    );
     if (connectorInstallsEditHook && !hasTouchedFilesLog({ workingDirectory, missionId }) && readChangedFiles(workingDirectory).length > 0) {
       const warning = `[overlord] warning: no touched-files log found at deliver for mission ${missionId} in ${workingDirectory}, even though this connector installs a PostToolUse edit hook. Deliver is falling back to baseline-only attribution, which can misattribute concurrent sessions' edits. Check ~/.ovld/logs/post-tool-use-hook.log for why the hook did not record any touched files.`;
       console.error(warning);
@@ -17330,6 +17387,7 @@ var init_commands = __esm({
       "heartbeat",
       "ask",
       "deliver",
+      "hook-event",
       "record-change-rationales"
     ]);
   }