@agentconnect.md/daemon 1.0.0-rc.313 → 1.0.0-rc.315

package/dist/{acp-host-DEjB1yFS.js → acp-host-4pA0zUPK.js}

@@ -361,7 +361,7 @@ const COLLABORATION_TOOLS = [
 	},
 	{
 		name: "messageAgent",
-		description: "Wake another AI agent by delivering a message into its session, so it picks the work up in its own turn. Use `toAgentId` from listChannelAgents. The message is delivered asynchronously — this does NOT return the peer's reply; the peer answers in the channel/thread (and can message you back). Omit `channel`/`thread` to target the same thread this conversation is in. Your identity as the caller is attached automatically — you cannot message yourself, and the target may be configured to reject calls from you (then `delivered` is false with a `reason`). When you are REPLYING to an agent that messaged you (you set `toAgentId` to that same agent), your reply automatically carries the correlation back to it — you do NOT need to pass `correlationId`; the daemon threads it for you so orchestration results are matched. Pass `correlationId` only to override this default (advanced/manual use).",
+		description: "Wake another AI agent by delivering a message into its session, so it picks the work up in its own turn. Use `toAgentId` from listChannelAgents. The message is delivered asynchronously — this does NOT return the peer's reply; the peer answers in the channel/thread (and can message you back). Omit `channel`/`thread` to target the same thread this conversation is in. Your identity as the caller is attached automatically — you cannot message yourself, and the target may be configured to reject calls from you (then `delivered` is false with a `reason`). When you are REPLYING to an agent that messaged you (you set `toAgentId` to that same agent), your reply automatically carries the correlation back to it — you do NOT need to pass `correlationId`; the daemon threads it for you so orchestration results are matched. Pass `correlationId` only to override this default (advanced/manual use). IMPORTANT — be quiet about the mechanics: do NOT post a separate chat message announcing that you sent it or restating \"delivered: true\"; the delivery is handled and already visible. After calling this tool, stay silent and end your turn unless you have something substantive for the human (a genuine blocker, or the peer’s actual reply once it arrives). Keep any necessary status to one short line.",
 		inputSchema: obj({
 			toAgentId: {
 				type: "string",
@@ -430,7 +430,7 @@ const COLLABORATION_TOOLS = [
 		} }, ["orchestrationId"])
 	}
 ];
-[...new Set([
+const ALL_TOOL_NAMES = [...new Set([
 	...SLACK_TOOLS,
 	...TELEGRAM_TOOLS,
 	...MEMORY_TOOLS,
@@ -10138,6 +10138,6 @@ var AcpHost = class {
 	}
 };
 //#endregion
-export { resolveRuntimes as C, cachedRuntimeVersions as S, resolveInMemoryDir as _, prepareWorkspace as a, toolsForIntegrations as b, sessionGitEnv as c, memoryKindOf as d, memoryProviderFor as f, listMemory as g, MemoryTooLargeError as h, prefetchWorkspace as i, simpleGit as l, MemoryPathError as m, turnFailureReason as n, initGitInjection as o, MemoryConflictError as p, installedRuntimes as r, probeGitVersion as s, AcpHost as t, createMemoryProvider as u, writeMemoryFile as v, cachedRuntimeNames as x, MEMORY_TOOL_NAMES as y };
+export { cachedRuntimeVersions as C, cachedRuntimeNames as S, resolveInMemoryDir as _, prepareWorkspace as a, MEMORY_TOOL_NAMES as b, sessionGitEnv as c, memoryKindOf as d, memoryProviderFor as f, listMemory as g, MemoryTooLargeError as h, prefetchWorkspace as i, simpleGit as l, MemoryPathError as m, turnFailureReason as n, initGitInjection as o, MemoryConflictError as p, installedRuntimes as r, probeGitVersion as s, AcpHost as t, createMemoryProvider as u, writeMemoryFile as v, resolveRuntimes as w, toolsForIntegrations as x, ALL_TOOL_NAMES as y };
 
-//# sourceMappingURL=acp-host-DEjB1yFS.js.map
+//# sourceMappingURL=acp-host-4pA0zUPK.js.map