@botbotgo/agent-harness 0.0.445 → 0.0.447

package/dist/package-version.d.ts

@@ -1,2 +1,2 @@
-export declare const AGENT_HARNESS_VERSION = "0.0.445";
+export declare const AGENT_HARNESS_VERSION = "0.0.447";
 export declare const AGENT_HARNESS_RELEASE_DATE = "2026-05-04";

package/dist/package-version.js

@@ -1,2 +1,2 @@
-export const AGENT_HARNESS_VERSION = "0.0.445";
+export const AGENT_HARNESS_VERSION = "0.0.447";
 export const AGENT_HARNESS_RELEASE_DATE = "2026-05-04";

package/dist/resources/prompts/runtime/required-execution-continuation.md

@@ -0,0 +1,8 @@
+The runtime has already observed planning state, tool state, or delegated execution state for this request. Continue from that state instead of restarting the task, broadening the scope, or asking the user to choose the next step.
+
+Use the current todo board, prior tool results, and available configured tools to choose one terminally useful action:
+- If a todo board is incomplete and existing evidence is enough, update the remaining todo items to completed, blocked, or failed as appropriate, then provide the final answer grounded in the observed evidence.
+- If more evidence is required and an available non-planning tool can get it, call that concrete tool next. Do not call write_todos or read_todos again before the evidence tool returns.
+- If no available tool can resolve the remaining work, update the todo board to blocked or failed and return a blocker report with the evidence already gathered.
+
+Never print a tool-call JSON object, function call, or tool name as prose when you intend to use a tool. Actually call the tool. Ask a blocking clarification question only after the available runtime evidence and configured tools are genuinely insufficient to continue.

package/dist/runtime/adapter/flow/invocation-flow.js

@@ -8,10 +8,10 @@ import { UPSTREAM_REQUEST_CONFIG_KEY, UPSTREAM_SESSION_CONFIG_KEY } from "../ups
 import { appendToolRecoveryInstruction, extractVisibleOutput, tryParseJson } from "../../parsing/output-parsing.js";
 import { salvageJsonToolCalls } from "../../parsing/output-tool-args.js";
 import { isEmptyFinalAiMessageError } from "../resilience.js";
-import { AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION, EXECUTION_WITH_TOOL_EVIDENCE_RETRY_INSTRUCTION, WRITE_TODOS_REQUIRED_PLAN_INSTRUCTION, } from "../../prompts/runtime-prompts.js";
+import { EXECUTION_WITH_TOOL_EVIDENCE_RETRY_INSTRUCTION, REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION, WRITE_TODOS_REQUIRED_PLAN_INSTRUCTION, } from "../../prompts/runtime-prompts.js";
 const CLOSE_REQUIRED_PLAN_RECOVERY_INSTRUCTION = [
     "The current required todo board still has unfinished work.",
-    "Do not broaden the investigation, restart planning, or ask the user what to do next.",
+    "Do not broaden the task, restart planning, or ask the user what to do next.",
     "Use the existing tool evidence already available in this run.",
     "Your next action must be write_todos: update every remaining pending or in_progress item to completed if evidence was gathered, or failed if it cannot be completed with the available tools.",
     "After that write_todos call, provide the final answer required by the agent response format.",
@@ -381,7 +381,7 @@ export async function executeRequestInvocation(options) {
             ? result.messages
             : undefined;
         const recoveryBase = messages ? { messages } : request;
-        const recoveredRequest = appendToolRecoveryInstruction(recoveryBase, AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION);
+        const recoveredRequest = appendToolRecoveryInstruction(recoveryBase, REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION);
         const recoveredInvocation = await invokeOnce(recoveredRequest);
         result = recoveredInvocation.result;
         executedToolResults.splice(0, executedToolResults.length, ...recoveredInvocation.executedToolResults);

package/dist/runtime/adapter/flow/stream-runtime.js

@@ -16,7 +16,7 @@ export class ExecutionReconciliationError extends Error {
 }
 const CLOSE_REQUIRED_PLAN_RECOVERY_INSTRUCTION = [
     "The current required todo board still has unfinished work.",
-    "Do not broaden the investigation, restart planning, or ask the user what to do next.",
+    "Do not broaden the task, restart planning, or ask the user what to do next.",
     "Use the existing tool evidence already available in this run.",
     "Your next action must be write_todos: update every remaining pending or in_progress item to completed if evidence was gathered, or failed if it cannot be completed with the available tools.",
     "After that write_todos call, provide the final answer required by the agent response format.",

package/dist/runtime/adapter/invocation-result.js

@@ -284,7 +284,7 @@ function extractDeterministicToolFailureReport(executedToolResults) {
     return [
         "Status: failed",
         "Summary:",
-        "- The investigation could not proceed because required tools failed before any concrete evidence was gathered.",
+        "- The request could not proceed because required tools failed before any concrete evidence was gathered.",
         "Likely Causes:",
         "- none",
         "Blockers:",

package/dist/runtime/adapter/local-tool-invocation.js

@@ -8,7 +8,7 @@ import { toolRequiresRuntimeApproval } from "./tool/tool-hitl.js";
 import { validateToolGatewayInput } from "../harness/tool-gateway/index.js";
 import { appendToolRecoveryInstruction, extractVisibleOutput, resolveMissingPlanRecoveryInstruction, resolveExecutionWithoutToolEvidenceTextInstruction, resolveToolCallRecoveryInstruction, sanitizeVisibleText, STRICT_TOOL_JSON_INSTRUCTION, } from "../parsing/output-parsing.js";
 import { salvageJsonToolCalls } from "../parsing/output-tool-args.js";
-import { AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION } from "../prompts/runtime-prompts.js";
+import { REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION } from "../prompts/runtime-prompts.js";
 const TOOL_FOLLOW_UP_INSTRUCTION = "One or more tool results are already available in this conversation. Answer the user's current request directly from the existing context and tool results. Do not ask the user to repeat inputs that are already present above.";
 const DEFAULT_MAX_TOOL_ITERATIONS = 10_000;
 const MAX_REPEATED_RECOVERY_WITHOUT_PROGRESS = 2;
@@ -188,7 +188,7 @@ function latestToolErrorRecoveryInstruction(executedToolResults) {
         return null;
     }
     const message = typeof latest.output === "string" ? latest.output : JSON.stringify(latest.output);
-    return resolveToolCallRecoveryInstruction(new Error(message)) ?? AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION;
+    return resolveToolCallRecoveryInstruction(new Error(message)) ?? REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION;
 }
 function terminalToolErrorRecoveryInstruction(terminalText) {
     return resolveToolCallRecoveryInstruction(new Error(terminalText));
@@ -386,7 +386,7 @@ export async function runLocalToolInvocationLoop({ binding, request, primaryTool
                     requiresPlan: requiresPlanEvidence(binding),
                 })
                 : shouldEnforceIncompletePlan
-                    ? AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION
+                    ? REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION
                     : null);
             if (requiresPlanEvidence(binding)
                 && !hasPlanStateEvidence(executedToolResults, externalPlanEvidence)
@@ -477,7 +477,7 @@ export async function runLocalToolInvocationLoop({ binding, request, primaryTool
                     executedToolResults,
                 });
             }
-            activeRequest = appendToolRecoveryInstruction(activeRequest, AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION);
+            activeRequest = appendToolRecoveryInstruction(activeRequest, REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION);
             pendingResult = undefined;
             continue;
         }

package/dist/runtime/parsing/output-recovery.js

@@ -1,4 +1,4 @@
-import { AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION, EXECUTION_WITH_TOOL_EVIDENCE_RETRY_INSTRUCTION, INTERNAL_RUNTIME_SPILL_PATH_INSTRUCTION, STRICT_TOOL_JSON_INSTRUCTION, WORKSPACE_RELATIVE_PATH_INSTRUCTION, WRITE_TODOS_DESCRIPTIVE_CONTENT_INSTRUCTION, WRITE_TODOS_FULL_ENTRY_INSTRUCTION, WRITE_TODOS_NON_EMPTY_INITIAL_LIST_INSTRUCTION, WRITE_TODOS_REQUIRED_PLAN_INSTRUCTION, } from "../prompts/runtime-prompts.js";
+import { EXECUTION_WITH_TOOL_EVIDENCE_RETRY_INSTRUCTION, INTERNAL_RUNTIME_SPILL_PATH_INSTRUCTION, REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION, STRICT_TOOL_JSON_INSTRUCTION, WORKSPACE_RELATIVE_PATH_INSTRUCTION, WRITE_TODOS_DESCRIPTIVE_CONTENT_INSTRUCTION, WRITE_TODOS_FULL_ENTRY_INSTRUCTION, WRITE_TODOS_NON_EMPTY_INITIAL_LIST_INSTRUCTION, WRITE_TODOS_REQUIRED_PLAN_INSTRUCTION, } from "../prompts/runtime-prompts.js";
 import { wrapNormalizedMessage, readTextContent } from "./output-content.js";
 import { salvageJsonToolCalls } from "./output-tool-args.js";
 function collectRequestMessages(request) {
@@ -153,7 +153,7 @@ export function resolveExecutionWithoutToolEvidenceTextInstruction(request, assi
         return null;
     }
     return hasExecutionEvidence
-        ? AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION
+        ? REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION
         : EXECUTION_WITH_TOOL_EVIDENCE_RETRY_INSTRUCTION;
 }
 export function resolveToolCallRecoveryInstruction(error) {

package/dist/runtime/prompts/runtime-prompts.d.ts

@@ -10,7 +10,7 @@ export declare const WRITE_TODOS_DESCRIPTIVE_CONTENT_INSTRUCTION: string;
 export declare const WRITE_TODOS_REQUIRED_PLAN_INSTRUCTION: string;
 export declare const EXECUTION_WITH_TOOL_EVIDENCE_INSTRUCTION: string;
 export declare const EXECUTION_WITH_TOOL_EVIDENCE_RETRY_INSTRUCTION: string;
-export declare const AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION: string;
+export declare const REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION: string;
 export declare const DELEGATED_TASK_FAILURE_RECOVERY_INSTRUCTION: string;
 export declare const DELEGATION_ONLY_RECOVERY_INSTRUCTION: string;
 export declare const INTERNAL_RUNTIME_SPILL_PATH_INSTRUCTION: string;

package/dist/runtime/prompts/runtime-prompts.js

@@ -13,7 +13,7 @@ export const WRITE_TODOS_DESCRIPTIVE_CONTENT_INSTRUCTION = readRuntimePrompt("wr
 export const WRITE_TODOS_REQUIRED_PLAN_INSTRUCTION = readRuntimePrompt("write-todos-required-plan");
 export const EXECUTION_WITH_TOOL_EVIDENCE_INSTRUCTION = readRuntimePrompt("execution-with-tool-evidence");
 export const EXECUTION_WITH_TOOL_EVIDENCE_RETRY_INSTRUCTION = readRuntimePrompt("execution-with-tool-evidence-retry");
-export const AUTONOMOUS_INVESTIGATION_RECOVERY_INSTRUCTION = readRuntimePrompt("autonomous-investigation-recovery");
+export const REQUIRED_EXECUTION_CONTINUATION_INSTRUCTION = readRuntimePrompt("required-execution-continuation");
 export const DELEGATED_TASK_FAILURE_RECOVERY_INSTRUCTION = readRuntimePrompt("delegated-task-failure-recovery");
 export const DELEGATION_ONLY_RECOVERY_INSTRUCTION = readRuntimePrompt("delegation-only-recovery");
 export const INTERNAL_RUNTIME_SPILL_PATH_INSTRUCTION = readRuntimePrompt("internal-runtime-spill-path");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@botbotgo/agent-harness",
-  "version": "0.0.445",
+  "version": "0.0.447",
   "description": "Workspace runtime for multi-agent applications",
   "license": "MIT",
   "type": "module",

package/dist/resources/prompts/runtime/autonomous-investigation-recovery.md

@@ -1,10 +0,0 @@
-Do not stop at a plan or ask the user to choose the next obvious diagnostic step when the request is for deep investigation, root-cause analysis, or step-by-step execution. Do not ask for more background, scope, logs, or environment details until you have first exhausted the context and tools already available in this runtime.
-
-If no concrete execution has happened yet, start from the current workspace, shell, and attached runtime/tool context by default, then continue the investigation yourself with the next concrete tool call. If the user explicitly asked for a plan, or if the task is clearly non-trivial and multi-step, call write_todos first with concrete investigation/execution steps before any other tool call or final answer.
-
-If a todo board already exists, do not restart planning and do not repeat the same clarification request. Use the current todo board and prior tool results to choose one of these terminally useful actions:
-- If more evidence is genuinely needed and an available tool can get it, make the next concrete tool call.
-- If the existing evidence is enough to answer, update the todo board to completed or blocked as appropriate, then provide the final answer grounded in the tool results.
-- If the available tools cannot resolve the remaining work, update the todo board to blocked or failed and provide a blocker report with the evidence.
-
-Never print a tool-call JSON object, function call, or tool name as prose when you intend to use a tool. Actually call the tool. Ask a blocking clarification question only after the available evidence is genuinely insufficient to continue.