@electric-ax/agents 0.4.8 → 0.4.9

package/dist/entrypoint.js

@@ -5,7 +5,6 @@ import pino from "pino";
 import { fileURLToPath } from "node:url";
 import { appendPathToUrl, completeWithLowCostModel, createEntityRegistry, createPullWakeRunner, createRuntimeHandler, createSkillTools, createSkillsRegistry, db, detectAvailableProviders, readCodexAccessToken, registerToolProvider, unregisterToolProvider } from "@electric-ax/agents-runtime";
 import { braveSearchTool, createBashTool, createEditTool, createEventSourceTools, createFetchUrlTool, createReadFileTool, createSendTool, createWriteTool, fetchUrlTool } from "@electric-ax/agents-runtime/tools";
-import { eq, not, queryOnce } from "@durable-streams/state";
 import { z } from "zod";
 import { createHash } from "node:crypto";
 import fs$1 from "node:fs/promises";
@@ -652,9 +651,9 @@ function createHortonDocsSupport(workingDirectory, opts = {}) {
 		},
 		createSearchTool() {
 			return {
-				name: `search_durable_agents_docs`,
-				label: `Search Durable Agents Docs`,
-				description: `Run a hybrid BM25 plus vector search over the local Durable Agents documentation index.`,
+				name: `search_electric_agents_docs`,
+				label: `Search Electric Agents Docs`,
+				description: `Run a hybrid BM25 plus vector search over the local Electric Agents documentation index.`,
 				parameters: Type.Object({
 					query: Type.String({ description: `The docs question or search query to run.` }),
 					limit: Type.Optional(Type.Number({
@@ -1002,10 +1001,10 @@ async function generateTitle(userMessage, llmCall, onFallback) {
 	}
 }
 function buildHortonSystemPrompt(workingDirectory, opts = {}) {
-	const docsTools = opts.hasDocsSupport ? `\n- search_durable_agents_docs: hybrid search over the built-in Durable Agents docs index` : ``;
+	const docsTools = opts.hasDocsSupport ? `\n- search_electric_agents_docs: hybrid search over the built-in Electric Agents docs index` : ``;
 	const eventSourceTools = opts.hasEventSourceTools ? `\n- list_event_sources: list external webhook/event feeds you can subscribe to, including available buckets and parameters\n- subscribe_event_source: subscribe yourself to one of those feeds or buckets so matching future events wake you\n- list_event_source_subscriptions: list your active event source subscriptions\n- unsubscribe_event_source: remove one of your event source subscriptions by id` : ``;
 	const skillsTools = opts.hasSkills ? `\n- use_skill: load a skill (knowledge, instructions, or a tutorial) into your context to help with the user's request\n- remove_skill: unload a skill from context when you're done with it` : ``;
-	const docsGuidance = opts.hasDocsSupport ? `\n- For ANY question about Electric Agents, Durable Agents, or this framework, ALWAYS use search_durable_agents_docs FIRST. Do not use web_search or fetch_url for Electric Agents topics unless the docs search returns no useful results.\n- The search tool returns chunk content directly — you do not need to read the source files.\n- Use repo read/bash tools only for non-doc files or when you need to inspect exact implementation code in the workspace.` : ``;
+	const docsGuidance = opts.hasDocsSupport ? `\n- For ANY question about Electric Agents or this framework, ALWAYS use search_electric_agents_docs FIRST. Do not use web_search or fetch_url for Electric Agents topics unless the docs search returns no useful results.\n- The search tool returns chunk content directly — you do not need to read the source files.\n- Use repo read/bash tools only for non-doc files or when you need to inspect exact implementation code in the workspace.` : ``;
 	const skillsGuidance = opts.hasSkills ? `\n# Skills\nYou have access to skills — specialized knowledge and guided workflows you can load on demand. Your context includes a skills catalog listing what's available. When the user's request matches a skill's description or keywords, load it with use_skill.
 
 Some skills are user-invocable — the user can trigger them with a slash command like \`/quickstart\`. When you see a message starting with \`/\` followed by a skill name, load that skill immediately with use_skill. Pass any text after the skill name as args.
@@ -1024,7 +1023,7 @@ Do NOT load a skill and then ignore its instructions. The skill is there because
 When a user is new or asks how to get started with Electric Agents, **don't assume a single path**. Present the options and let them choose:
 
 - **Learn the concepts first** → Explain what Electric Agents is, answer questions, point to docs.
-  Use search_durable_agents_docs to look up answers. Only load the quickstart skill if the user explicitly asks for a hands-on guided tutorial.
+  Use search_electric_agents_docs to look up answers. Only load the quickstart skill if the user explicitly asks for a hands-on guided tutorial.
 
 - **Hands-on guided tutorial** → Load the quickstart skill (or tell them to type \`/quickstart\`).
   This is a step-by-step build that takes them from zero to a running app.
@@ -1034,11 +1033,11 @@ When a user is new or asks how to get started with Electric Agents, **don't assu
   This sets up project structure and orients them in the codebase.
 
 - **Have a specific question?** → Answer it directly.
-  Use search_durable_agents_docs first, then fall back to fetch_url or general knowledge if needed.
+  Use search_electric_agents_docs first, then fall back to fetch_url or general knowledge if needed.
 
 Don't force onboarding. If someone just wants to chat or code, let them. When in doubt, ask what they'd like to do rather than picking a path for them.`;
 	const docsUrlGuidance = opts.docsUrl ? `\n# Electric Agents documentation
-- ${opts.hasDocsSupport ? `If search_durable_agents_docs is available, use it first (faster, hybrid search).` : `Use fetch_url to look up documentation pages.`}
+- ${opts.hasDocsSupport ? `If search_electric_agents_docs is available, use it first (faster, hybrid search).` : `Use fetch_url to look up documentation pages.`}
 - The Electric Agents docs site is at ${opts.docsUrl}
 - The docs site covers: Usage (entity definition, handlers, tools, state, spawning, coordination, waking, shared state, client integration, app setup), Reference (handler context, entity definitions, configurations, tools, state proxies, wake events, registries), Entities (Horton, Worker), and Patterns (Manager-Worker, Pipeline, Map-Reduce, Dispatcher, Blackboard, Reactive Observers).
 - For general coding questions unrelated to Electric Agents, use web_search or your own knowledge.` : ``;
@@ -1124,11 +1123,14 @@ function payloadToTitleText(payload) {
 	return String(payload);
 }
 async function extractFirstUserMessage(ctx) {
-	const firstMessage = await queryOnce((q) => q.from({ inbox: ctx.db.collections.inbox }).where(({ inbox }) => not(eq(inbox.from, `system`))).orderBy(({ inbox }) => inbox._seq, `asc`).findOne());
+	const firstMessage = ctx.db.collections.inbox.toArray.filter((message) => message.from !== `system`).sort((left, right) => messageSeq(left) - messageSeq(right))[0];
 	if (!firstMessage) return null;
 	const text = payloadToTitleText(firstMessage.payload);
 	return text.length > 0 ? text : null;
 }
+function messageSeq(message) {
+	return typeof message._seq === `number` ? message._seq : -1;
+}
 function readAgentsMd(workingDirectory) {
 	const agentsMdPath = path.join(workingDirectory, `AGENTS.md`);
 	try {
@@ -1290,15 +1292,7 @@ function registerHorton(registry, options) {
 		creationSchema: hortonCreationSchema,
 		handler: assistantHandler
 	});
-	const typeNames = [`horton`];
-	if (streamFn) {
-		registry.define(`chat`, {
-			description: `Compatibility alias for the built-in assistant type.`,
-			handler: assistantHandler
-		});
-		typeNames.push(`chat`);
-	}
-	return typeNames;
+	return [`horton`];
 }
 
 //#endregion

package/dist/index.cjs

@@ -29,7 +29,6 @@ const __electric_ax_agents_runtime = __toESM(require("@electric-ax/agents-runtim
 const __electric_ax_agents_runtime_tools = __toESM(require("@electric-ax/agents-runtime/tools"));
 const node_fs = __toESM(require("node:fs"));
 const pino = __toESM(require("pino"));
-const __durable_streams_state = __toESM(require("@durable-streams/state"));
 const zod = __toESM(require("zod"));
 const node_crypto = __toESM(require("node:crypto"));
 const node_fs_promises = __toESM(require("node:fs/promises"));
@@ -676,9 +675,9 @@ function createHortonDocsSupport(workingDirectory, opts = {}) {
 		},
 		createSearchTool() {
 			return {
-				name: `search_durable_agents_docs`,
-				label: `Search Durable Agents Docs`,
-				description: `Run a hybrid BM25 plus vector search over the local Durable Agents documentation index.`,
+				name: `search_electric_agents_docs`,
+				label: `Search Electric Agents Docs`,
+				description: `Run a hybrid BM25 plus vector search over the local Electric Agents documentation index.`,
 				parameters: __sinclair_typebox.Type.Object({
 					query: __sinclair_typebox.Type.String({ description: `The docs question or search query to run.` }),
 					limit: __sinclair_typebox.Type.Optional(__sinclair_typebox.Type.Number({
@@ -1027,10 +1026,10 @@ async function generateTitle(userMessage, llmCall, onFallback) {
 	}
 }
 function buildHortonSystemPrompt(workingDirectory, opts = {}) {
-	const docsTools = opts.hasDocsSupport ? `\n- search_durable_agents_docs: hybrid search over the built-in Durable Agents docs index` : ``;
+	const docsTools = opts.hasDocsSupport ? `\n- search_electric_agents_docs: hybrid search over the built-in Electric Agents docs index` : ``;
 	const eventSourceTools = opts.hasEventSourceTools ? `\n- list_event_sources: list external webhook/event feeds you can subscribe to, including available buckets and parameters\n- subscribe_event_source: subscribe yourself to one of those feeds or buckets so matching future events wake you\n- list_event_source_subscriptions: list your active event source subscriptions\n- unsubscribe_event_source: remove one of your event source subscriptions by id` : ``;
 	const skillsTools = opts.hasSkills ? `\n- use_skill: load a skill (knowledge, instructions, or a tutorial) into your context to help with the user's request\n- remove_skill: unload a skill from context when you're done with it` : ``;
-	const docsGuidance = opts.hasDocsSupport ? `\n- For ANY question about Electric Agents, Durable Agents, or this framework, ALWAYS use search_durable_agents_docs FIRST. Do not use web_search or fetch_url for Electric Agents topics unless the docs search returns no useful results.\n- The search tool returns chunk content directly — you do not need to read the source files.\n- Use repo read/bash tools only for non-doc files or when you need to inspect exact implementation code in the workspace.` : ``;
+	const docsGuidance = opts.hasDocsSupport ? `\n- For ANY question about Electric Agents or this framework, ALWAYS use search_electric_agents_docs FIRST. Do not use web_search or fetch_url for Electric Agents topics unless the docs search returns no useful results.\n- The search tool returns chunk content directly — you do not need to read the source files.\n- Use repo read/bash tools only for non-doc files or when you need to inspect exact implementation code in the workspace.` : ``;
 	const skillsGuidance = opts.hasSkills ? `\n# Skills\nYou have access to skills — specialized knowledge and guided workflows you can load on demand. Your context includes a skills catalog listing what's available. When the user's request matches a skill's description or keywords, load it with use_skill.
 
 Some skills are user-invocable — the user can trigger them with a slash command like \`/quickstart\`. When you see a message starting with \`/\` followed by a skill name, load that skill immediately with use_skill. Pass any text after the skill name as args.
@@ -1049,7 +1048,7 @@ Do NOT load a skill and then ignore its instructions. The skill is there because
 When a user is new or asks how to get started with Electric Agents, **don't assume a single path**. Present the options and let them choose:
 
 - **Learn the concepts first** → Explain what Electric Agents is, answer questions, point to docs.
-  Use search_durable_agents_docs to look up answers. Only load the quickstart skill if the user explicitly asks for a hands-on guided tutorial.
+  Use search_electric_agents_docs to look up answers. Only load the quickstart skill if the user explicitly asks for a hands-on guided tutorial.
 
 - **Hands-on guided tutorial** → Load the quickstart skill (or tell them to type \`/quickstart\`).
   This is a step-by-step build that takes them from zero to a running app.
@@ -1059,11 +1058,11 @@ When a user is new or asks how to get started with Electric Agents, **don't assu
   This sets up project structure and orients them in the codebase.
 
 - **Have a specific question?** → Answer it directly.
-  Use search_durable_agents_docs first, then fall back to fetch_url or general knowledge if needed.
+  Use search_electric_agents_docs first, then fall back to fetch_url or general knowledge if needed.
 
 Don't force onboarding. If someone just wants to chat or code, let them. When in doubt, ask what they'd like to do rather than picking a path for them.`;
 	const docsUrlGuidance = opts.docsUrl ? `\n# Electric Agents documentation
-- ${opts.hasDocsSupport ? `If search_durable_agents_docs is available, use it first (faster, hybrid search).` : `Use fetch_url to look up documentation pages.`}
+- ${opts.hasDocsSupport ? `If search_electric_agents_docs is available, use it first (faster, hybrid search).` : `Use fetch_url to look up documentation pages.`}
 - The Electric Agents docs site is at ${opts.docsUrl}
 - The docs site covers: Usage (entity definition, handlers, tools, state, spawning, coordination, waking, shared state, client integration, app setup), Reference (handler context, entity definitions, configurations, tools, state proxies, wake events, registries), Entities (Horton, Worker), and Patterns (Manager-Worker, Pipeline, Map-Reduce, Dispatcher, Blackboard, Reactive Observers).
 - For general coding questions unrelated to Electric Agents, use web_search or your own knowledge.` : ``;
@@ -1149,11 +1148,14 @@ function payloadToTitleText(payload) {
 	return String(payload);
 }
 async function extractFirstUserMessage(ctx) {
-	const firstMessage = await (0, __durable_streams_state.queryOnce)((q) => q.from({ inbox: ctx.db.collections.inbox }).where(({ inbox }) => (0, __durable_streams_state.not)((0, __durable_streams_state.eq)(inbox.from, `system`))).orderBy(({ inbox }) => inbox._seq, `asc`).findOne());
+	const firstMessage = ctx.db.collections.inbox.toArray.filter((message) => message.from !== `system`).sort((left, right) => messageSeq(left) - messageSeq(right))[0];
 	if (!firstMessage) return null;
 	const text = payloadToTitleText(firstMessage.payload);
 	return text.length > 0 ? text : null;
 }
+function messageSeq(message) {
+	return typeof message._seq === `number` ? message._seq : -1;
+}
 function readAgentsMd(workingDirectory) {
 	const agentsMdPath = node_path.default.join(workingDirectory, `AGENTS.md`);
 	try {
@@ -1315,15 +1317,7 @@ function registerHorton(registry, options) {
 		creationSchema: hortonCreationSchema,
 		handler: assistantHandler
 	});
-	const typeNames = [`horton`];
-	if (streamFn) {
-		registry.define(`chat`, {
-			description: `Compatibility alias for the built-in assistant type.`,
-			handler: assistantHandler
-		});
-		typeNames.push(`chat`);
-	}
-	return typeNames;
+	return [`horton`];
 }
 
 //#endregion

package/dist/index.d.ts

@@ -1,9 +1,9 @@
 import { AgentConfig, AgentTool, AvailableProvider, DispatchPolicy, EntityRegistry, HandlerContext, HeadersProvider, ProcessWakeConfig, PullWakeRunnerConfig, RuntimeHandler, SkillsRegistry, WakeEvent } from "@electric-ax/agents-runtime";
 import { braveSearchTool } from "@electric-ax/agents-runtime/tools";
-import { ChangeEvent } from "@durable-streams/state";
 import { ListedEntry as McpListedEntry, McpConfig, McpServerConfig, McpServerConfig as McpServerConfig$1, Registry, Registry as McpRegistry, RegistrySnapshot, RegistrySubscriber } from "@electric-ax/agents-mcp";
 import { AgentTool as AgentTool$1, StreamFn } from "@mariozechner/pi-agent-core";
 import { IncomingMessage, ServerResponse } from "node:http";
+import { ChangeEvent } from "@durable-streams/state";
 
 //#region src/bootstrap.d.ts
 declare const DEFAULT_BUILTIN_AGENT_HANDLER_PATH = "/_electric/builtin-agent-handler";

package/dist/index.js

@@ -5,7 +5,6 @@ import { appendPathToUrl, completeWithLowCostModel, createEntityRegistry, create
 import { braveSearchTool, braveSearchTool as braveSearchTool$1, createBashTool, createEditTool, createEventSourceTools, createFetchUrlTool, createReadFileTool, createSendTool, createWriteTool, fetchUrlTool } from "@electric-ax/agents-runtime/tools";
 import fs from "node:fs";
 import pino from "pino";
-import { eq, not, queryOnce } from "@durable-streams/state";
 import { z } from "zod";
 import { createHash } from "node:crypto";
 import fs$1 from "node:fs/promises";
@@ -652,9 +651,9 @@ function createHortonDocsSupport(workingDirectory, opts = {}) {
 		},
 		createSearchTool() {
 			return {
-				name: `search_durable_agents_docs`,
-				label: `Search Durable Agents Docs`,
-				description: `Run a hybrid BM25 plus vector search over the local Durable Agents documentation index.`,
+				name: `search_electric_agents_docs`,
+				label: `Search Electric Agents Docs`,
+				description: `Run a hybrid BM25 plus vector search over the local Electric Agents documentation index.`,
 				parameters: Type.Object({
 					query: Type.String({ description: `The docs question or search query to run.` }),
 					limit: Type.Optional(Type.Number({
@@ -1003,10 +1002,10 @@ async function generateTitle(userMessage, llmCall, onFallback) {
 	}
 }
 function buildHortonSystemPrompt(workingDirectory, opts = {}) {
-	const docsTools = opts.hasDocsSupport ? `\n- search_durable_agents_docs: hybrid search over the built-in Durable Agents docs index` : ``;
+	const docsTools = opts.hasDocsSupport ? `\n- search_electric_agents_docs: hybrid search over the built-in Electric Agents docs index` : ``;
 	const eventSourceTools = opts.hasEventSourceTools ? `\n- list_event_sources: list external webhook/event feeds you can subscribe to, including available buckets and parameters\n- subscribe_event_source: subscribe yourself to one of those feeds or buckets so matching future events wake you\n- list_event_source_subscriptions: list your active event source subscriptions\n- unsubscribe_event_source: remove one of your event source subscriptions by id` : ``;
 	const skillsTools = opts.hasSkills ? `\n- use_skill: load a skill (knowledge, instructions, or a tutorial) into your context to help with the user's request\n- remove_skill: unload a skill from context when you're done with it` : ``;
-	const docsGuidance = opts.hasDocsSupport ? `\n- For ANY question about Electric Agents, Durable Agents, or this framework, ALWAYS use search_durable_agents_docs FIRST. Do not use web_search or fetch_url for Electric Agents topics unless the docs search returns no useful results.\n- The search tool returns chunk content directly — you do not need to read the source files.\n- Use repo read/bash tools only for non-doc files or when you need to inspect exact implementation code in the workspace.` : ``;
+	const docsGuidance = opts.hasDocsSupport ? `\n- For ANY question about Electric Agents or this framework, ALWAYS use search_electric_agents_docs FIRST. Do not use web_search or fetch_url for Electric Agents topics unless the docs search returns no useful results.\n- The search tool returns chunk content directly — you do not need to read the source files.\n- Use repo read/bash tools only for non-doc files or when you need to inspect exact implementation code in the workspace.` : ``;
 	const skillsGuidance = opts.hasSkills ? `\n# Skills\nYou have access to skills — specialized knowledge and guided workflows you can load on demand. Your context includes a skills catalog listing what's available. When the user's request matches a skill's description or keywords, load it with use_skill.
 
 Some skills are user-invocable — the user can trigger them with a slash command like \`/quickstart\`. When you see a message starting with \`/\` followed by a skill name, load that skill immediately with use_skill. Pass any text after the skill name as args.
@@ -1025,7 +1024,7 @@ Do NOT load a skill and then ignore its instructions. The skill is there because
 When a user is new or asks how to get started with Electric Agents, **don't assume a single path**. Present the options and let them choose:
 
 - **Learn the concepts first** → Explain what Electric Agents is, answer questions, point to docs.
-  Use search_durable_agents_docs to look up answers. Only load the quickstart skill if the user explicitly asks for a hands-on guided tutorial.
+  Use search_electric_agents_docs to look up answers. Only load the quickstart skill if the user explicitly asks for a hands-on guided tutorial.
 
 - **Hands-on guided tutorial** → Load the quickstart skill (or tell them to type \`/quickstart\`).
   This is a step-by-step build that takes them from zero to a running app.
@@ -1035,11 +1034,11 @@ When a user is new or asks how to get started with Electric Agents, **don't assu
   This sets up project structure and orients them in the codebase.
 
 - **Have a specific question?** → Answer it directly.
-  Use search_durable_agents_docs first, then fall back to fetch_url or general knowledge if needed.
+  Use search_electric_agents_docs first, then fall back to fetch_url or general knowledge if needed.
 
 Don't force onboarding. If someone just wants to chat or code, let them. When in doubt, ask what they'd like to do rather than picking a path for them.`;
 	const docsUrlGuidance = opts.docsUrl ? `\n# Electric Agents documentation
-- ${opts.hasDocsSupport ? `If search_durable_agents_docs is available, use it first (faster, hybrid search).` : `Use fetch_url to look up documentation pages.`}
+- ${opts.hasDocsSupport ? `If search_electric_agents_docs is available, use it first (faster, hybrid search).` : `Use fetch_url to look up documentation pages.`}
 - The Electric Agents docs site is at ${opts.docsUrl}
 - The docs site covers: Usage (entity definition, handlers, tools, state, spawning, coordination, waking, shared state, client integration, app setup), Reference (handler context, entity definitions, configurations, tools, state proxies, wake events, registries), Entities (Horton, Worker), and Patterns (Manager-Worker, Pipeline, Map-Reduce, Dispatcher, Blackboard, Reactive Observers).
 - For general coding questions unrelated to Electric Agents, use web_search or your own knowledge.` : ``;
@@ -1125,11 +1124,14 @@ function payloadToTitleText(payload) {
 	return String(payload);
 }
 async function extractFirstUserMessage(ctx) {
-	const firstMessage = await queryOnce((q) => q.from({ inbox: ctx.db.collections.inbox }).where(({ inbox }) => not(eq(inbox.from, `system`))).orderBy(({ inbox }) => inbox._seq, `asc`).findOne());
+	const firstMessage = ctx.db.collections.inbox.toArray.filter((message) => message.from !== `system`).sort((left, right) => messageSeq(left) - messageSeq(right))[0];
 	if (!firstMessage) return null;
 	const text = payloadToTitleText(firstMessage.payload);
 	return text.length > 0 ? text : null;
 }
+function messageSeq(message) {
+	return typeof message._seq === `number` ? message._seq : -1;
+}
 function readAgentsMd(workingDirectory) {
 	const agentsMdPath = path.join(workingDirectory, `AGENTS.md`);
 	try {
@@ -1291,15 +1293,7 @@ function registerHorton(registry, options) {
 		creationSchema: hortonCreationSchema,
 		handler: assistantHandler
 	});
-	const typeNames = [`horton`];
-	if (streamFn) {
-		registry.define(`chat`, {
-			description: `Compatibility alias for the built-in assistant type.`,
-			handler: assistantHandler
-		});
-		typeNames.push(`chat`);
-	}
-	return typeNames;
+	return [`horton`];
 }
 
 //#endregion

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@electric-ax/agents",
-  "version": "0.4.8",
+  "version": "0.4.9",
   "description": "Built-in Electric Agents runtimes such as Horton and worker",
   "repository": {
     "type": "git",
@@ -49,7 +49,7 @@
     "sqlite-vec": "^0.1.9",
     "zod": "^4.3.6",
     "@electric-ax/agents-mcp": "0.2.2",
-    "@electric-ax/agents-runtime": "0.3.4"
+    "@electric-ax/agents-runtime": "0.3.5"
   },
   "devDependencies": {
     "@types/better-sqlite3": "^7.6.13",
@@ -58,7 +58,7 @@
     "cross-env": "^10.1.0",
     "tsdown": "^0.9.0",
     "tsx": "^4.19.0",
-    "typescript": "^5.0.0",
+    "typescript": "^5.9.3",
     "vitest": "^4.1.0"
   },
   "files": [

package/skills/quickstart.md

@@ -100,7 +100,7 @@ IMPORTANT: Never write files until the user explicitly confirms. "Ask to write"
 
 - **Continue building** — add an HTTP API route and a React frontend to this app so users can interact with the analyzer from the browser.
 - **Start a new app** — use the `agents-chat-starter` template for a full multi-agent chat app with rooms, agent spawning, and a Slack-style UI. Load the init skill or tell them to type `/init`.
-- **Explore the docs** — read about other coordination patterns (blackboard, pipeline, map-reduce), dive into the API reference, or learn about shared state, context assembly, and other advanced features. Use `search_durable_agents_docs` to look things up.
+- **Explore the docs** — read about other coordination patterns (blackboard, pipeline, map-reduce), dive into the API reference, or learn about shared state, context assembly, and other advanced features. Use `search_electric_agents_docs` to look things up.
 
 Wait for the user to choose. Only proceed to Step 4 if they want to continue building.
 
@@ -116,7 +116,7 @@ Wait for the user to choose. Only proceed to Step 4 if they want to continue bui
 - `server.ts` is at the working directory root. Entity files go in `entities/`.
 - Worker spawn args MUST include `tools` array (at least one tool, e.g. `tools: ["bash"]`).
 - Use `edit` tool for small changes (like updating server.ts). Use `write` for full entity file updates.
-- If the user asks a question about Electric Agents concepts, APIs, or patterns between steps, use the `search_durable_agents_docs` tool to look up the answer in the built-in documentation before guessing or searching the web.
+- If the user asks a question about Electric Agents concepts, APIs, or patterns between steps, use the `search_electric_agents_docs` tool to look up the answer in the built-in documentation before guessing or searching the web.
 
 ---