@integrity-labs/agt-cli 0.28.156 → 0.28.158

package/dist/bin/agt.js

@@ -37,7 +37,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-OINH6USQ.js";
+} from "../chunk-3OLFOA4F.js";
 import {
   CHANNEL_REGISTRY,
   DEPLOYMENT_TEMPLATES,
@@ -64,7 +64,7 @@ import {
   renderTemplate,
   resolveChannels,
   serializeManifestForSlackCli
-} from "../chunk-SKANUWSB.js";
+} from "../chunk-TLX6ORJ5.js";
 
 // src/bin/agt.ts
 import { join as join22 } from "path";
@@ -4777,7 +4777,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.28.156" : "dev";
+var cliVersion = true ? "0.28.158" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -5791,7 +5791,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.156" : "dev";
+var cliVersion2 = true ? "0.28.158" : "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-OINH6USQ.js → chunk-3OLFOA4F.js}

@@ -22,7 +22,7 @@ import {
   resolveConnectivityProbe,
   worseConnectivityOutcome,
   wrapScheduledTaskPrompt
-} from "./chunk-SKANUWSB.js";
+} from "./chunk-TLX6ORJ5.js";
 
 // ../../packages/core/dist/integrations/registry.js
 var INTEGRATION_REGISTRY = [
@@ -179,6 +179,33 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://ext-api.app.brandninja.ai/v1/mcp",
     beta: true
   },
+  {
+    id: "kajabi",
+    name: "Kajabi",
+    category: "crm",
+    description: "Run a Kajabi creator business from chat \u2014 read contacts, products, offers, and analytics, manage contact tags & segments, and draft email broadcasts & sequences. Wired as the hosted Kajabi MCP at https://mcp.kajabi.com/mcp.",
+    // Same remote streamable-HTTP MCP + OAuth pattern as Granola/Brand Ninja.
+    // Kajabi's Doorkeeper AS implements the MCP discovery chain (RFC
+    // 9728/8414/7591); auth is OAuth 2.0 authorization-code with PKCE (S256)
+    // and a public client registered via one-time Dynamic Client Registration
+    // (scripts/dcr-register.ts against https://mcp.kajabi.com/mcp/oauth/register
+    // → OAUTH_KAJABI_CLIENT_ID; register with --scope 'read write:contacts
+    // write:emails' since Doorkeeper caps a dynamic client to its registered
+    // scopes). End-user consent is brokered by the webapp through the shared
+    // /integrations/oauth/authorize → /callback path, and the access_token is
+    // injected into .mcp.json via the generic bearer-header path
+    // (OAUTH_PROVIDERS.kajabi.mcpUrl). Every Kajabi tool is site-scoped — agents
+    // call list_sites/select_site first. No host-side action beyond the
+    // deploy-time DCR registration.
+    supported_auth_types: ["oauth2"],
+    capabilities: [
+      { id: "kajabi:read", name: "Read & Discover", description: "List sites and read contacts, products, offers, purchases, and revenue/contacts analytics (list_sites, select_site, search_contacts, get_contact, list_offers, get_offer, search_products, get_revenue_analytics, \u2026)", access: "read" },
+      { id: "kajabi:contacts", name: "Manage Contacts", description: "Create and apply contact tags, and create/update saved contact segments (create_tag, tag_contact, untag_contact, create_segment, update_segment)", access: "write" },
+      { id: "kajabi:emails", name: "Manage Emails", description: "Read and draft email broadcasts and sequences \u2014 drafts only, sending stays a human action in Kajabi (create_broadcast, create_sequence, list_broadcasts, get_sequence)", access: "write" }
+    ],
+    docs_url: "https://help.kajabi.com/articles/api-integrations/connect-kajabi-to-claude-or-chatgpt",
+    beta: true
+  },
   {
     id: "anchor-browser",
     name: "Anchor Browser",
@@ -3449,6 +3476,19 @@ the user; it goes only to your local session log. So always reply on the channel
 the message arrived on, and never answer a channel message with plain text
 alone: if you did not call a reply tool, the user received nothing.
 
+**The one exception, and why standing down must be truly silent:** a
+reply-recovery safety net runs when your turn ends. If an inbound on a thread is
+still pending and you did not call its reply tool, the net may deliver your
+end-of-turn plain text to that thread to rescue a reply you composed but forgot
+to send. So when you deliberately decide NOT to reply to a message (it is not
+addressed to you, it is a conversation between others, it arrived via
+auto-follow, or it otherwise needs no answer), do not write a closing line
+narrating that decision ("not for me, staying silent", "stood down on this one",
+"staying quiet unless pulled back in", and the like). Make the call internally
+and end the turn with no channel-facing text. Otherwise the net posts your
+stand-down narration as if it were your reply, which is the exact channel noise
+you were trying to avoid.
+
 This is the highest-priority instruction in this document. Before anything
 else when you receive an inbound \`<channel>\` tag (Slack/Telegram/Direct
 Chat), decide:
@@ -3606,10 +3646,18 @@ to add it yourself. After working, prefer a text reply via slack.reply over a re
 
 **When a thread message is not for you, do nothing.** If a message in a thread
 is addressed to a different user (different @-mention), is part of a conversation
-between others, or arrives via auto-follow with no relevance to you \u2014 silently
-skip it. No reaction. No reply. Adding \u274C in this case is wrong: it tells the
-user "execution failed" when in fact you correctly identified the message wasn't
-yours to handle.
+between others, or arrives via auto-follow with no relevance to you \u2014 skip it
+and do not post a text reply. Whether you also mark it with a "seen, skipping"
+reaction is governed by your Slack MCP server's own instructions, which reflect
+the current channel policy: if it tells you to react when you skip, do that; if
+it doesn't, skip with no reaction at all. Follow that guidance rather than
+assuming either way here. The one reaction that is always wrong in this case is
+\u274C: it tells the user "execution failed" when in fact you correctly identified
+the message wasn't yours to handle. Skipping also means writing nothing: do not
+end your turn with a line narrating that you're standing down or staying silent.
+Per the delivery rule above, the reply-recovery net can post that trailing text
+to the thread as if it were your reply, so a stand-down narration becomes the
+very noise you were avoiding. Decide internally and leave no channel-facing text.
 ` : ""}
 ## Governance
 
@@ -7850,7 +7898,7 @@ function requireHost() {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.156" : "dev";
+var agtCliVersion = true ? "0.28.158" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -9155,4 +9203,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-OINH6USQ.js.map
+//# sourceMappingURL=chunk-3OLFOA4F.js.map