@phnx-labs/agents-cli 1.20.48 → 1.20.49

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## Unreleased
 
+## 1.20.49
+
+- **`agents run --mode plan` no longer hard-fails on agents without a read-only mode (antigravity, cursor, kiro, …).** Those agents have no plan flag, so an explicit or default `--mode plan` used to abort with `does not support 'plan' mode` — breaking multi-agent scripts that pass a uniform plan flag, and diverging from `agents teams add` (default mode `edit`). `resolveMode` now degrades unsupported `plan` to the agent's safest native mode (`capabilities.modes[0]`, typically `edit`), matching the existing `auto` → `edit` degrade. The CLI prints a yellow warning when the user explicitly asked for plan (gray for the implicit default) so the elevation is never silent. `skip` still hard-fails when unsupported. Source: `apps/cli/src/lib/exec.ts`, `apps/cli/src/commands/exec.ts`.
+- **`agents cloud cancel` now actually cancels paused runs.** `RushProvider.cancel()` issued `DELETE /api/v1/cloud-runs/{id}`, which the backend doesn't implement — it 404s — so `agents cloud cancel` (and the Factory Floor's cancel affordance) silently failed on any run that wasn't actively running: `queued`, `needs_review`, and `input_required` runs stayed stuck (e.g. a 14-day-old input-required run lingering in the Floor's "NEEDS YOU" bucket forever). Switched to the cancel action endpoint `POST /api/v1/cloud-runs/{id}/cancel`, which the backend implements and which cancels paused runs too. Verified live against `api.prix.dev` (the POST returned `{"ok":true,"status":"cancelled"}` and the stuck run transitioned `needs_review` → `cancelled`). Source: `apps/cli/src/lib/cloud/rush.ts`.
+
 ## 1.20.48
 
 - **Menu-bar helper: a RECENT TICKETS section shows the issues you filed via the quick-issue bar, each clickable to open in Linear.** The completion notification is transient, so the tickets the `Cmd-Shift-O` bar creates now also persist to a small local ledger (`~/.agents/.history/menubar/recent-tickets.json`, newest-first, deduped by id, capped at 10) that the menu-bar dropdown surfaces below RECENT sessions — click a row to open the ticket. The dispatch records the id + note + Linear URL on a successful create; the section renders nothing when the ledger is empty. Source: `apps/cli/menubar/Sources/MenubarHelper/{RecentTickets,StatusItemController,AgentsCLI,IssueSelfTest}.swift`.

package/dist/commands/exec.js

@@ -570,7 +570,7 @@ export function registerRunCommand(program) {
             });
             process.exit(resumeExit);
         }
-        const [{ buildExecCommand, parseExecEnv, execAgent, runWithFallback, normalizeMode, resolveMode, defaultModeFor, headlessPlanStallCommand, nativeResume, resolveInteractive }, { ALL_AGENT_IDS }, { profileExists, resolveProfileForRun }, { readAndResolveBundleEnv, describeBundle, assertRemoteBundleFlagsUnsupported }, { splitBundleRef, resolveSshTarget, remoteResolveEnv }, { getConfiguredRunStrategy, normalizeRunStrategy, resolveRunVersion, rotationFailoverChain, shouldArmRotationFailover, RUN_STRATEGIES }, { getGlobalDefault, getVersionHomePath, resolveVersion, resolveVersionAlias, ensureAgentRunnable }, { buildDiscoveredPlugin, loadPluginManifest, syncPluginToVersion }, { parseWorkflowFrontmatter, resolveWorkflowRef, resolveAllowedSubagents, pruneStaleWorkflowSubagents }, { resolveRunDefaults }, { getMcpServersByName, buildWorkflowMcpConfig }, { supports },] = await Promise.all([
+        const [{ buildExecCommand, parseExecEnv, execAgent, runWithFallback, normalizeMode, resolveMode, headlessPlanStallCommand, nativeResume, resolveInteractive }, { ALL_AGENT_IDS }, { profileExists, resolveProfileForRun }, { readAndResolveBundleEnv, describeBundle, assertRemoteBundleFlagsUnsupported }, { splitBundleRef, resolveSshTarget, remoteResolveEnv }, { getConfiguredRunStrategy, normalizeRunStrategy, resolveRunVersion, rotationFailoverChain, shouldArmRotationFailover, RUN_STRATEGIES }, { getGlobalDefault, getVersionHomePath, resolveVersion, resolveVersionAlias, ensureAgentRunnable }, { buildDiscoveredPlugin, loadPluginManifest, syncPluginToVersion }, { parseWorkflowFrontmatter, resolveWorkflowRef, resolveAllowedSubagents, pruneStaleWorkflowSubagents }, { resolveRunDefaults }, { getMcpServersByName, buildWorkflowMcpConfig }, { supports },] = await Promise.all([
             import('../lib/exec.js'),
             import('../lib/agents.js'),
             import('../lib/profiles.js'),
@@ -1017,28 +1017,38 @@ export function registerRunCommand(program) {
             console.error(chalk.red(`Invalid mode: ${mode}. Use plan, edit, auto, or skip ('full' accepted as alias for skip).`));
             process.exit(1);
         }
-        // When the user did not pass --mode explicitly, the default is the
-        // generic 'plan'. Some agents (antigravity: edit/skip only, grok in some
-        // configurations) do not support plan. For implicit defaults, degrade
-        // silently to the agent's first listed mode rather than throwing — the
-        // user did not ask for read-only, they asked for "just run it." An
-        // explicit --mode plan still throws (see resolveMode), because silently
-        // elevating an explicit read-only request to edit is unsafe.
+        // Default CLI mode is the generic 'plan'. Agents without a read-only
+        // mode (antigravity, cursor, kiro, …) degrade via resolveMode to their
+        // safest native mode (modes[0], typically edit). That covers both the
+        // implicit default and an explicit `--mode plan`, so multi-agent
+        // scripts can pass a uniform plan flag without per-agent branching.
+        // Elevation is never silent: we warn on stderr (yellow when the user
+        // explicitly asked for plan; gray for the implicit default / auto).
+        // `skip` still hard-fails when unsupported — pretending we bypassed
+        // permissions would be unsafe.
         const modeIsDefault = modeSource === 'default';
+        const requestedMode = normalizeMode(mode);
+        let resolvedMode;
         try {
-            resolveMode(agent, normalizeMode(mode));
+            resolvedMode = resolveMode(agent, requestedMode);
         }
         catch (err) {
-            if (modeIsDefault && !modeFromRunDefault) {
-                mode = defaultModeFor(agent);
-                if (!options.quiet) {
-                    process.stderr.write(chalk.gray(`[agents] ${agent} has no '${options.mode}' mode; using '${mode}'\n`));
+            console.error(chalk.red(err.message));
+            process.exit(1);
+        }
+        if (resolvedMode !== requestedMode) {
+            mode = resolvedMode;
+            if (!options.quiet) {
+                if (requestedMode === 'plan' && !modeIsDefault) {
+                    process.stderr.write(chalk.yellow(`[agents] ${agent} has no read-only 'plan' mode; using '${mode}' (writable) instead. Pass --mode ${mode} to silence this.\n`));
+                }
+                else {
+                    process.stderr.write(chalk.gray(`[agents] ${agent} has no '${requestedMode}' mode; using '${mode}'\n`));
                 }
             }
-            else {
-                console.error(chalk.red(err.message));
-                process.exit(1);
-            }
+        }
+        else {
+            mode = resolvedMode;
         }
         // Fail fast on the headless-plan stall footgun: a slash command run
         // headless under the implicit default 'plan' mode hangs forever at

package/dist/lib/cloud/rush.js

@@ -525,7 +525,11 @@ export class RushCloudProvider {
     }
     async cancel(taskId) {
         const token = readToken();
-        const res = await api('DELETE', `/api/v1/cloud-runs/${encodeURIComponent(taskId)}`, token);
+        // The cancel ACTION endpoint (POST .../cancel) is what the backend implements;
+        // it works on paused runs too (queued / needs_review / input_required). A bare
+        // DELETE on the run 404s, so `agents cloud cancel` silently failed on anything
+        // that wasn't actively running.
+        const res = await api('POST', `/api/v1/cloud-runs/${encodeURIComponent(taskId)}/cancel`, token);
         if (!res.ok) {
             throw new Error(`Failed to cancel task (${res.status}).`);
         }

package/dist/lib/exec.d.ts

@@ -40,10 +40,16 @@ export declare function headlessPlanStallCommand(args: {
  *
  * - `auto` on an agent without auto support silently degrades to `edit`
  *   (every agent supports edit-like behavior as its default).
+ * - `plan` on an agent without a read-only mode degrades to the agent's
+ *   safest native mode (`capabilities.modes[0]`, typically `edit`). Agents
+ *   like antigravity/cursor/kiro have no plan flag; hard-failing made
+ *   multi-agent scripts (`--mode plan` for everyone) unusable and diverged
+ *   from `agents teams add`, which already defaults to `edit`. Callers that
+ *   care (the `agents run` CLI) must surface a warning when requested ≠
+ *   resolved so the elevation is not silent.
  * - `skip` on an agent without skip support throws with a clear message
  *   naming the agent's supported modes. No silent fallback — the user
  *   explicitly asked to bypass permissions; pretending we did is unsafe.
- * - `plan` on an agent without plan support throws the same way.
  */
 export declare function resolveMode(agent: AgentId, requested: Mode): Mode;
 /**
@@ -54,10 +60,8 @@ export declare function resolveMode(agent: AgentId, requested: Mode): Mode;
  * supports." Agents that include `plan` list it first; agents like
  * antigravity that have no read-only mode list `edit` first.
  *
- * Use this when the user did not pass `--mode` explicitly. When the user
- * *did* pass `--mode plan` and the agent doesn't support it, call
- * `resolveMode` instead so the user sees a loud error rather than a silent
- * elevation from read-only to writable.
+ * Prefer this over a hard-coded `'plan'` when the agent is known. `resolveMode`
+ * also maps an unsupported `'plan'` request onto this same value.
  */
 export declare function defaultModeFor(agent: AgentId): Mode;
 /** Reasoning effort levels passed to agents that support them. 'auto' defers to the agent's default. */

package/dist/lib/exec.js

@@ -75,10 +75,16 @@ export function headlessPlanStallCommand(args) {
  *
  * - `auto` on an agent without auto support silently degrades to `edit`
  *   (every agent supports edit-like behavior as its default).
+ * - `plan` on an agent without a read-only mode degrades to the agent's
+ *   safest native mode (`capabilities.modes[0]`, typically `edit`). Agents
+ *   like antigravity/cursor/kiro have no plan flag; hard-failing made
+ *   multi-agent scripts (`--mode plan` for everyone) unusable and diverged
+ *   from `agents teams add`, which already defaults to `edit`. Callers that
+ *   care (the `agents run` CLI) must surface a warning when requested ≠
+ *   resolved so the elevation is not silent.
  * - `skip` on an agent without skip support throws with a clear message
  *   naming the agent's supported modes. No silent fallback — the user
  *   explicitly asked to bypass permissions; pretending we did is unsafe.
- * - `plan` on an agent without plan support throws the same way.
  */
 export function resolveMode(agent, requested) {
     const supported = AGENTS[agent].capabilities.modes;
@@ -89,6 +95,12 @@ export function resolveMode(agent, requested) {
         // at least 'edit' in its modes table, since that's the default behavior).
         return 'edit';
     }
+    if (requested === 'plan') {
+        // No read-only mode on this agent. modes[0] is the declared safest mode
+        // (edit for antigravity/cursor/kiro/…). Prefer that over hard-fail so
+        // uniform multi-agent `--mode plan` dispatches still run.
+        return supported[0];
+    }
     throw new Error(`${agent} does not support '${requested}' mode. Supported modes: ${supported.join(', ')}.`);
 }
 /**
@@ -99,10 +111,8 @@ export function resolveMode(agent, requested) {
  * supports." Agents that include `plan` list it first; agents like
  * antigravity that have no read-only mode list `edit` first.
  *
- * Use this when the user did not pass `--mode` explicitly. When the user
- * *did* pass `--mode plan` and the agent doesn't support it, call
- * `resolveMode` instead so the user sees a loud error rather than a silent
- * elevation from read-only to writable.
+ * Prefer this over a hard-coded `'plan'` when the agent is known. `resolveMode`
+ * also maps an unsupported `'plan'` request onto this same value.
  */
 export function defaultModeFor(agent) {
     return AGENTS[agent].capabilities.modes[0];
@@ -541,7 +551,8 @@ export function buildExecCommand(options) {
     }
     // Resolve the requested mode against the agent's capability table.
     // - `auto` on an agent without auto support → silently degrades to `edit`
-    // - `skip`/`plan` on an unsupported agent → throws a clear error
+    // - `plan` on an agent without a read-only mode → degrades to modes[0]
+    // - `skip` on an unsupported agent → throws a clear error
     // After resolveMode, the chosen mode is guaranteed to be in template.modeFlags.
     const resolvedMode = resolveMode(options.agent, normalizeMode(options.mode));
     const modeFlags = template.modeFlags[resolvedMode];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@phnx-labs/agents-cli",
-  "version": "1.20.48",
+  "version": "1.20.49",
   "description": "One CLI for all your AI coding agents - versions, config, cloud dispatch, sessions, and teams (now with first-class Grok Build CLI support)",
   "type": "module",
   "main": "dist/index.js",