@cognipeer/agent-sdk 0.9.5 → 0.9.7

package/README.md

@@ -1,6 +1,6 @@
 # @cognipeer/agent-sdk
 
-[![npm](https://img.shields.io/npm/v/@cognipeer/agent-sdk?color=success)](https://npmjs.com/package/@cognipeer/agent-sdk) [Docs Website](https://cognipeer.github.io/agent-sdk/) 
+[![npm](https://img.shields.io/npm/v/@cognipeer/agent-sdk?color=success)](https://npmjs.com/package/@cognipeer/agent-sdk) [Docs Website](https://docs.cognipeer.com/agent-sdk/) 
 
 Lightweight, message-first agent runtime that keeps tool calls transparent, supports provider-native reasoning plus post-tool reflection, automatically summarizes long histories, and ships with planning, multi-agent handoffs, and structured tracing.
 
@@ -50,7 +50,7 @@ Highlights:
 |------|-------------|
 | `src/` | Source for the published package (TypeScript, bundled via tsup). |
 | `examples/` | End-to-end scripts demonstrating tools, planning, summarization, multi-agent, MCP, structured output, and vision input. |
-| `docs/` | VitePress documentation site served at [cognipeer.github.io/agent-sdk](https://cognipeer.github.io/agent-sdk/). |
+| `docs/` | VitePress documentation site served at [docs.cognipeer.com/agent-sdk](https://docs.cognipeer.com/agent-sdk/). |
 | `dist/` | Build output (generated). Contains ESM, CommonJS, and TypeScript definitions. |
 | `logs/` | Generated trace sessions when `tracing.enabled: true`. Safe to delete. |
 
@@ -464,7 +464,7 @@ npm publish --access public
 
 ## Documentation
 
-- Live site: https://cognipeer.github.io/agent-sdk/
+- Live site: https://docs.cognipeer.com/agent-sdk/
 - Key guides within this repo:
   - `docs/getting-started/`
   - `docs/core-concepts/`

package/dist/index.cjs

@@ -647,7 +647,7 @@ function fromLangchainModel(lcModel) {
 var DEFAULT_TODO_LIST_PROMPT = `Planning tools are available when they materially improve execution.
 
 Rules:
-1) Use "manage_todo_list" for multi-step work, delegation, recovery after a failed attempt, or when the user explicitly asks for a plan.
+1) Use "manage_plan" for multi-step work, delegation, recovery after a failed attempt, or when the user explicitly asks for a plan.
 2) Do NOT create a plan for direct Q&A, simple recall from existing context, or a single straightforward tool lookup unless the user asks for one.
 3) If a task is multi-step and no valid plan exists yet, create one before substantial execution.
 4) Use operation="write" only to create or fully replace the entire plan. After a plan exists, default to operation="update" for progress, evidence, status, owner changes, blockers, or reprioritization.
@@ -2763,6 +2763,7 @@ function coerceObject(def, value, depth) {
 // src/smart/toolResponses.ts
 var CONTROL_PLANE_TOOL_NAMES = [
   "response",
+  "manage_plan",
   "manage_todo_list",
   "get_tool_response",
   "ask_user_question",
@@ -3020,7 +3021,7 @@ function describeField(field, depth = 0) {
 }
 
 // src/smart/runtimeConfig.ts
-var DEFAULT_CRITICAL_TOOLS = ["response", "manage_todo_list", "get_tool_response"];
+var DEFAULT_CRITICAL_TOOLS = ["response", "manage_plan", "manage_todo_list", "get_tool_response"];
 var BASE_DEFAULTS = {
   limits: { maxToolCalls: 20, maxParallelTools: 5, maxContextTokens: 96e3, maxTotalOutputTokens: 0, maxCostUsd: 0, maxWallClockMs: 0 },
   summarization: {
@@ -7558,10 +7559,10 @@ function hasToolResponseRecoveryReference(messages, executionId) {
     return executionId ? content.includes(executionId) : true;
   });
 }
-function createManageTodoTool(stateRef) {
+function createPlanTool(stateRef, toolName, description) {
   const manageTodo = createTool({
-    name: "manage_todo_list",
-    description: "Manage a structured todo list to track progress and plan tasks throughout your coding session.\n\nOperations:\n- read: return the current plan\n- write: replace the full plan with a complete ordered todoList\n- update: patch existing todo items by id without resending the whole plan\n\nRules:\n- Use write only when creating or fully rewriting the plan\n- After a plan exists, prefer update for status, evidence, or owner changes\n- Update payloads should contain only the changed items\n- When using update, pass expectedVersion to avoid overwriting a newer plan\n- Keep ids unique; write operations must keep ids sequential starting from 1\n- Keep at most ONE item in-progress at a time\n- If update fails due to version mismatch, read the latest plan and retry",
+    name: toolName,
+    description,
     schema: zod.z.object({
       operation: zod.z.enum(["write", "read", "update"]),
       expectedVersion: zod.z.number().int().min(0).optional(),
@@ -7574,7 +7575,7 @@ function createManageTodoTool(stateRef) {
         const version = stateRef.planVersion || 1;
         const adherenceScore = stateRef.adherenceScore || 0;
         const planData = {
-          source: "manage_todo_list",
+          source: toolName,
           operation,
           version,
           adherenceScore,
@@ -7585,7 +7586,7 @@ function createManageTodoTool(stateRef) {
         recordTraceEvent(traceSession, {
           type: "plan",
           label: `Plan ${operation}`,
-          actor: { scope: "agent", name: "manage_todo_list", role: "planner" },
+          actor: { scope: "agent", name: toolName, role: "planner" },
           sections: [
             {
               kind: "summary",
@@ -7724,6 +7725,14 @@ function createManageTodoTool(stateRef) {
   manageTodo._stateRef = stateRef;
   return manageTodo;
 }
+var MANAGE_PLAN_DESCRIPTION = "Manage a structured execution plan to track progress and sequence steps throughout your run.\n\nOperations:\n- read: return the current plan\n- write: replace the full plan with a complete ordered set of steps (pass as `todoList`)\n- update: patch existing plan steps by id without resending the whole plan\n\nRules:\n- Use write only when creating or fully rewriting the plan\n- After a plan exists, prefer update for status, evidence, or owner changes\n- Update payloads should contain only the changed items\n- When using update, pass expectedVersion to avoid overwriting a newer plan\n- Keep ids unique; write operations must keep ids sequential starting from 1\n- Keep at most ONE item in-progress at a time\n- If update fails due to version mismatch, read the latest plan and retry";
+var LEGACY_MANAGE_TODO_LIST_DESCRIPTION = "DEPRECATED \u2014 identical to, and shares state with, `manage_plan`. Kept only so a run already in flight (or a caller still on the old name) keeps working; prefer `manage_plan` for anything new.\n\n" + MANAGE_PLAN_DESCRIPTION;
+function createManageTodoTool(stateRef) {
+  return createPlanTool(stateRef, "manage_plan", MANAGE_PLAN_DESCRIPTION);
+}
+function createManageTodoListAliasTool(stateRef) {
+  return createPlanTool(stateRef, "manage_todo_list", LEGACY_MANAGE_TODO_LIST_DESCRIPTION);
+}
 function createGetToolResponseTool(stateRef) {
   const getTool = createTool({
     name: "get_tool_response",
@@ -7765,6 +7774,7 @@ function createContextTools(stateRef, opts) {
   const tools = [];
   if (opts?.planningEnabled) {
     tools.push(createManageTodoTool(stateRef));
+    tools.push(createManageTodoListAliasTool(stateRef));
   }
   if (opts?.includeGetToolResponse ?? true) {
     tools.push(createGetToolResponseTool(stateRef));
@@ -11859,6 +11869,7 @@ exports.createDelegateTool = createDelegateTool;
 exports.createGetToolResponseTool = createGetToolResponseTool;
 exports.createGuardrail = createGuardrail;
 exports.createJsonGuardrail = createJsonGuardrail;
+exports.createManageTodoListAliasTool = createManageTodoListAliasTool;
 exports.createManageTodoTool = createManageTodoTool;
 exports.createOpenSkillTool = createOpenSkillTool;
 exports.createParallelTool = createParallelTool;