@leanandmean/coding-agent 0.74.1-scramjet.6 → 0.74.1-scramjet.7

package/dist/core/agent-session.d.ts

@@ -16,7 +16,7 @@ import type { Agent, AgentEvent, AgentMessage, AgentState, AgentTool, ThinkingLe
 import type { ImageContent, Model, TextContent } from "@leanandmean/ai";
 import { type BashResult } from "./bash-executor.js";
 import { type CompactionResult } from "./compaction/index.js";
-import { type ContextUsage, type DeliverAs, type DispatchUserInputOptions, type ExtensionCommandContextActions, type ExtensionErrorListener, ExtensionRunner, type ExtensionUIContext, type InputSource, type ReplacedSessionContext, type SendMessageDeliverAs, type SessionStartEvent, type ShutdownHandler, type ToolDefinition, type ToolInfo } from "./extensions/index.js";
+import { type ContextUsage, type DeliverAs, type DispatchUserInputOptions, type ExtensionCommandContextActions, type ExtensionErrorListener, ExtensionRunner, type ExtensionUIContext, type InputSource, type InvokeHarnessToolOptions, type ReplacedSessionContext, type SendMessageDeliverAs, type SessionStartEvent, type ShutdownHandler, type ToolDefinition, type ToolInfo } from "./extensions/index.js";
 import type { CustomMessage } from "./messages.js";
 import type { ModelRegistry } from "./model-registry.js";
 import { type PromptTemplate } from "./prompt-templates.js";
@@ -285,6 +285,19 @@ export declare class AgentSession {
      * Changes take effect on the next agent turn.
      */
     setActiveToolsByName(toolNames: string[]): void;
+    /**
+     * Execute a registered tool as a harness-originated call (not requested by the model).
+     *
+     * Resolves the wrapped tool from the full registry — including `"harness-only"` tools that are
+     * never provider-visible — so its `execute` still receives the extension context and its
+     * `tool_call`/`tool_result` hooks still fire. Delegates to {@link Agent.runHarnessTool}, which
+     * runs the call through the real prepare/execute/finalize pipeline: identical live
+     * `tool_execution_*`/message events, persisted session entries, and extension hooks, but no
+     * run/turn framing. The idle-vs-mid-run branch lives in `runHarnessTool` (keyed on the agent's
+     * active run, which tracks `isStreaming`): idle calls execute immediately, mid-run calls queue
+     * and drain before the next intra-run LLM call.
+     */
+    invokeHarnessTool(name: string, args: unknown, options?: InvokeHarnessToolOptions): Promise<void>;
     /** Whether compaction or branch summarization is currently running */
     get isCompacting(): boolean;
     /** All messages including custom types like BashExecutionMessage */