@integrity-labs/agt-cli 0.27.50 → 0.27.51

package/dist/bin/agt.js

@@ -27,7 +27,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-RMYQBP26.js";
+} from "../chunk-Y4KVZGPE.js";
 import {
   CHANNEL_REGISTRY,
   DEPLOYMENT_TEMPLATES,
@@ -4710,7 +4710,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync10, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.27.50" : "dev";
+var cliVersion = true ? "0.27.51" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -5488,7 +5488,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.27.50" : "dev";
+var cliVersion2 = true ? "0.27.51" : "dev";
 var program = new Command();
 program.name("agt").description("Augmented CLI \u2014 agent provisioning and management").version(cliVersion2).option("--json", "Emit machine-readable JSON output (suppress spinners and colors)").option("--skip-update-check", "Skip the automatic update check on startup");
 program.hook("preAction", async (thisCommand, actionCommand) => {

package/dist/{chunk-RMYQBP26.js → chunk-Y4KVZGPE.js}

@@ -3096,6 +3096,31 @@ If the work turns out to be unexpectedly slow after you started inline,
 finish the current sub-step, then dispatch the rest. Don't apologise for
 mid-task switching \u2014 operators care about responsiveness, not consistency.
 
+## Background dispatch for non-channel work
+
+For background tool work that **isn't** a channel reply \u2014 multi-step data
+pulls, CRM enrichments, research workflows, cross-MCP orchestration \u2014 use
+\`subagent_type: general-purpose\` (Anthropic's built-in). It inherits the
+full MCP tool surface from this session and reliably binds every
+\`mcp__*\` server you have available.
+
+**Why not \`augmented-worker\` for now:** there is an upstream Claude Code
+bug ([anthropics/claude-code#64909](https://github.com/anthropics/claude-code/issues/64909))
+where sub-agents with an explicit \`tools:\` allowlist get an empty MCP
+tool registry \u2014 every \`mcp__*\` call returns "No such tool available."
+\`general-purpose\` uses \`tools: *\` (inherit-all) and escapes the bug.
+Once Anthropic ships the fix, \`augmented-worker\` becomes preferred again
+(restricted tool surface for safety + working MCP binding); the dispatch
+recommendation here will flip back automatically.
+
+The channel-message triage above is **not** changed by this note \u2014 slow
+channel replies still dispatch via \`channel-message-handler\` per
+\xA7 FIRST ACTION. Be aware that \`channel-message-handler\` shares the
+explicit-allowlist shape and so is subject to the same upstream bug; if
+you observe a dispatched channel reply silently failing to land,
+acknowledge the original message inline yourself and surface the gap
+rather than attempting another sub-agent dispatch.
+
 ${activeTasksSection}${personalitySection}## Identity
 
 - Code Name: ${frontmatter.code_name}
@@ -4552,7 +4577,7 @@ If a capability seems missing, **check first** \u2014 run the CLI, list tools (\
 `;
   return `---
 name: augmented-worker
-description: General-purpose background worker for multi-step tool tasks the parent doesn't want to inline (data pulls, multi-API workflows, CRM enrichments, research that needs MCP tools). Has explicit access to every \`mcp__*\` server the parent has wired. Use this \u2014 not \`general-purpose\` and not the read-only researcher/reviewer subagents from other plugins \u2014 whenever the work requires calling MCP tools (e.g. \`mcp__granola__*\`, \`mcp__composio_attio__*\`, \`mcp__slack-channel__*\`, \`mcp__augmented__*\`). Many community subagents declare restrictive \`tools:\` allowlists that exclude MCP tools, so dispatching to them will silently produce "No such tool available." failures and force unsafe fallback paths (reading raw secrets from \`.mcp.json\`, bypassing the Credential Access Control guardrail).
+description: Background worker for multi-step tool tasks the parent doesn't want to inline (data pulls, multi-API workflows, CRM enrichments, research that needs MCP tools). Carries an explicit \`mcp__*\` wildcard allowlist for every server the parent has wired. **Until [anthropics/claude-code#64909](https://github.com/anthropics/claude-code/issues/64909) ships an upstream fix, prefer \`subagent_type: general-purpose\` for MCP-tool dispatch** \u2014 the bug is in Claude Code's sub-agent dispatch path: sub-agents with an explicit \`tools:\` allowlist get an empty MCP tool registry (every \`mcp__*\` call returns "No such tool available."), while \`general-purpose\` (\`tools: *\` inherit-all) correctly binds the full MCP surface. This subagent's allowlist is correct and will work the moment Anthropic lands the fix; until then it is retained for the eventual structural fix and the rare case where you specifically need a restricted tool surface AND can accept the MCP gap. See [[ENG-5938]] for the workaround tracker.
 background: true
 tools: ${tools}
 ---
@@ -7122,4 +7147,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-RMYQBP26.js.map
+//# sourceMappingURL=chunk-Y4KVZGPE.js.map