@idapt/cli 1.12.0 → 1.14.0

package/dist/index.d.cts

@@ -178,6 +178,25 @@ interface V1CommandSpec extends V1CommandDocFields {
     readonly workspaceScope?: "scope" | "target";
     /** Long-running → goes through the async-operation layer. */
     readonly async: boolean;
+    /**
+     * Client polling parameters for `async` verbs whose operations outlive the
+     * executor's defaults (120 × 1500 ms ≈ 3 min). The SDK/CLI auto-poller
+     * (`awaitOperation`) reads these off the generated binding — e.g. video
+     * generation ships `{ intervalMs: 5000, maxAttempts: 240 }` (a 20-min
+     * ceiling). Omit for seconds-long verbs; per-call options still win.
+     */
+    readonly pollHint?: {
+        readonly intervalMs: number;
+        readonly maxAttempts: number;
+    };
+    /**
+     * Async verbs that ALWAYS answer with the operation handle, even for a
+     * foreground in-chat tool call. The dispatcher's catalog-REST seam reads
+     * this to never block-poll the verb inside the agent loop (a minutes-long
+     * render would pin the run job); the model reconciles via `operation get`.
+     * SDK/CLI callers are unaffected — their `wait` semantics still apply.
+     */
+    readonly handleOnly?: boolean;
     /** Tier-1 one-line decision hint (≤200 chars). */
     readonly summary: string;
     /**
@@ -366,6 +385,21 @@ interface ExecuteOptions {
      * {@link executeCommand} seam (in-chat dispatcher / MCP) never sets it.
      */
     readonly defaultWorkspaceRef?: string;
+    /**
+     * CLI ambient acting AGENT (resourceId | name) from `idapt agent use` or a
+     * per-call `--agent`. Injected as `agent_id` on `chat create` ONLY (that verb
+     * binds the acting agent; blanket `agent_id` injection would mis-scope
+     * `chat send`'s `sender_agent_id`, agent-CRUD filters, etc.), and only on the
+     * CLI-string path. An explicit `--agent-id`/positional still wins.
+     */
+    readonly defaultAgentRef?: string;
+    /**
+     * The selected agent's Memory box resourceId (from `idapt agent use`). Injected
+     * as the `:id` of `memory` verbs that address a box, when the call didn't name
+     * one — the client-side twin of the in-run dispatcher's box auto-injection, so
+     * `idapt memory …` reads/writes the selected agent's Memory.
+     */
+    readonly defaultAgentMemoryBoxId?: string;
 }
 interface ExecuteResult {
     readonly ok: boolean;

package/dist/index.d.ts

@@ -178,6 +178,25 @@ interface V1CommandSpec extends V1CommandDocFields {
     readonly workspaceScope?: "scope" | "target";
     /** Long-running → goes through the async-operation layer. */
     readonly async: boolean;
+    /**
+     * Client polling parameters for `async` verbs whose operations outlive the
+     * executor's defaults (120 × 1500 ms ≈ 3 min). The SDK/CLI auto-poller
+     * (`awaitOperation`) reads these off the generated binding — e.g. video
+     * generation ships `{ intervalMs: 5000, maxAttempts: 240 }` (a 20-min
+     * ceiling). Omit for seconds-long verbs; per-call options still win.
+     */
+    readonly pollHint?: {
+        readonly intervalMs: number;
+        readonly maxAttempts: number;
+    };
+    /**
+     * Async verbs that ALWAYS answer with the operation handle, even for a
+     * foreground in-chat tool call. The dispatcher's catalog-REST seam reads
+     * this to never block-poll the verb inside the agent loop (a minutes-long
+     * render would pin the run job); the model reconciles via `operation get`.
+     * SDK/CLI callers are unaffected — their `wait` semantics still apply.
+     */
+    readonly handleOnly?: boolean;
     /** Tier-1 one-line decision hint (≤200 chars). */
     readonly summary: string;
     /**
@@ -366,6 +385,21 @@ interface ExecuteOptions {
      * {@link executeCommand} seam (in-chat dispatcher / MCP) never sets it.
      */
     readonly defaultWorkspaceRef?: string;
+    /**
+     * CLI ambient acting AGENT (resourceId | name) from `idapt agent use` or a
+     * per-call `--agent`. Injected as `agent_id` on `chat create` ONLY (that verb
+     * binds the acting agent; blanket `agent_id` injection would mis-scope
+     * `chat send`'s `sender_agent_id`, agent-CRUD filters, etc.), and only on the
+     * CLI-string path. An explicit `--agent-id`/positional still wins.
+     */
+    readonly defaultAgentRef?: string;
+    /**
+     * The selected agent's Memory box resourceId (from `idapt agent use`). Injected
+     * as the `:id` of `memory` verbs that address a box, when the call didn't name
+     * one — the client-side twin of the in-run dispatcher's box auto-injection, so
+     * `idapt memory …` reads/writes the selected agent's Memory.
+     */
+    readonly defaultAgentMemoryBoxId?: string;
 }
 interface ExecuteResult {
     readonly ok: boolean;

package/dist/index.js

@@ -1,3 +1,3 @@
-export { VERB_OVERRIDES, autoMode, commandsForResource, createFetchTransport, execute, executeCommand, findCommand, getResourcePlaybook, listCommands, listResources, mapArgsToV1, parseInvocation, reconcileToV1, render, renderHelp, renderInstructions, resolveCommand, toSnakeKey } from './chunk-GISKSK4V.js';
+export { VERB_OVERRIDES, autoMode, commandsForResource, createFetchTransport, execute, executeCommand, findCommand, getResourcePlaybook, listCommands, listResources, mapArgsToV1, parseInvocation, reconcileToV1, render, renderHelp, renderInstructions, resolveCommand, toSnakeKey } from './chunk-OE6HNBY2.js';
 //# sourceMappingURL=index.js.map
 //# sourceMappingURL=index.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@idapt/cli",
-  "version": "1.12.0",
+  "version": "1.14.0",
   "description": "The idapt CLI — the `idapt <resource> <verb>` grammar, command→REST translation, help/instructions, output formatting, SOTA auth (OAuth 2.1 + PKCE / device-code / API-key) and self-update, over the public v1 API. One implementation shared by the in-chat dispatcher, MCP, and the `idapt` CLI binary.",
   "license": "Apache-2.0",
   "homepage": "https://idapt.app/cli",