@integrity-labs/agt-cli 0.28.1111 → 0.28.1113

package/dist/bin/agt.js

@@ -40,12 +40,12 @@ import {
   success,
   table,
   warn
-} from "../chunk-2UHVPGB3.js";
+} from "../chunk-TXNVB3DN.js";
 import {
   getProjectDir,
   isSessionResumeDisabled,
   readDirectChatSessionState
-} from "../chunk-4PTXGOVO.js";
+} from "../chunk-JX7ZXCNZ.js";
 import {
   AnchorSessionClient,
   CHANNEL_REGISTRY,
@@ -79,7 +79,7 @@ import {
   serializeManifestForSlackCli,
   sessionFileExists,
   sessionTranscriptDir
-} from "../chunk-TZM6YVE7.js";
+} from "../chunk-OBZB6MUE.js";
 import "../chunk-OCMJ5E6J.js";
 import "../chunk-XWVM4KPK.js";
 import "../chunk-EL5MWGGH.js";
@@ -5474,7 +5474,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync11, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.28.1111" : "dev";
+var cliVersion = true ? "0.28.1113" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -6734,7 +6734,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.1111" : "dev";
+var cliVersion2 = true ? "0.28.1113" : "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-4PTXGOVO.js → chunk-JX7ZXCNZ.js}

@@ -24,7 +24,7 @@ import {
   rotateDailySession,
   sessionFileExists,
   todayLocalIso
-} from "./chunk-TZM6YVE7.js";
+} from "./chunk-OBZB6MUE.js";
 import {
   classifyUnanswerablePane,
   findUsageLimitResetHint,
@@ -6113,4 +6113,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-4PTXGOVO.js.map
+//# sourceMappingURL=chunk-JX7ZXCNZ.js.map

package/dist/{chunk-TZM6YVE7.js → chunk-OBZB6MUE.js}

@@ -2049,6 +2049,34 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://help.kajabi.com/articles/api-integrations/connect-kajabi-to-claude-or-chatgpt",
     beta: true
   },
+  {
+    id: "otter",
+    name: "Otter.ai",
+    category: "knowledge",
+    description: "Read Otter.ai meetings: search recordings by date, attendee or topic, and read summaries, action items and full speaker-attributed transcripts.",
+    // CS-2029: same remote streamable-HTTP MCP + OAuth pattern as Granola/Kajabi.
+    // Otter's server implements the MCP discovery chain (RFC 9728 protected-
+    // resource metadata at mcp.otter.ai → RFC 8414 AS metadata at otter.ai →
+    // RFC 7591 registration); 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://otter.ai/oauth/register
+    // → OAUTH_OTTER_CLIENT_ID, --scope 'profile:read conversations:read').
+    // Consent is brokered by the webapp through the shared
+    // /integrations/oauth/authorize → /callback path, and the access_token
+    // reaches the host via the generic remote-oauth-proxy
+    // (OAUTH_PROVIDERS.otter.mcpUrl). Read-only by construction: Otter
+    // advertises no write scope.
+    supported_auth_types: ["oauth2"],
+    capabilities: [
+      { id: "otter:read", name: "Read Meetings & Transcripts", description: "Find recorded meetings by date, attendee, topic or title, and read their summaries, action items, outlines and full transcripts (otter_get_user_info, otter_search, otter_fetch)", access: "read" }
+    ],
+    // Otter's own Help Center article for the MCP server (CodeRabbit, #6906). It
+    // exists even though help.otter.ai answers 403 to non-browser clients; the
+    // help-centre API confirmed it (title "Otter MCP Server"). The MCP endpoint
+    // itself is a JSON-RPC URL, not a page (Obi Wan 8305072d5414).
+    docs_url: "https://help.otter.ai/hc/en-us/articles/35287607569687-Otter-MCP-Server",
+    beta: true
+  },
   {
     id: "anchor-browser",
     name: "Anchor Browser",
@@ -7575,14 +7603,37 @@ var FLAG_REGISTRY = [
   },
   {
     key: "platform-maintenance-mode",
-    description: 'Platform-wide maintenance mode (ENG-6506): when on, every agent across every team/org auto-replies to admitted human inbound with a "we are offline for maintenance" notice instead of dispatching to the agent \u2014 for whole-platform downtime such as DB upgrades. Read host-side per inbound from the flags cache (no MCP restart). Boolean gate; ships dark \u2014 when off, channels behave exactly as today. (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',
-    flagType: "boolean",
-    // Declared safe value is `false` (normal operation). Fail-safe direction: a
-    // flag-DB read error or absent flag map must never silence the fleet on its
-    // own — agents stay responsive unless an operator deliberately flips this on
-    // from the admin Feature Flags page. No envVar: net-new control, no
-    // pre-flags env gate to migrate.
-    defaultValue: false,
+    description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',
+    flagType: "enum",
+    allowedValues: ["off", "tools-offline", "fleet-offline"],
+    // Declared safe value is `off` (normal operation). Fail-safe direction: a
+    // flag-DB read error or absent flag map must never silence the fleet OR take
+    // its write tools away on its own — agents stay fully functional unless an
+    // operator deliberately sets a mode from the admin Feature Flags page. No
+    // envVar: net-new control, no pre-flags env gate to migrate.
+    //
+    // ENG-11436 widened this from a boolean rather than adding a second flag, so
+    // there is ONE operator control whose modes are mutually exclusive by type
+    // instead of two similar booleans with four combinations.
+    //
+    // The host resolver GRANDFATHERS a boolean-shaped cache value
+    // (true -> fleet-offline, false -> off), and the DIRECTION it protects is
+    // narrower than an earlier version of this comment claimed (Obi Wan
+    // `e3f0d2c154b9` on #6903). It said "an older manager still writing a boolean
+    // must not make a central flip a silent no-op". That situation cannot arise:
+    // once this registry change deploys, normalizeFlagValue only ever yields one
+    // of the three strings, feature-flags-host.ts writes the heartbeat map
+    // verbatim, so no manager writes a boolean again. What grandfathering
+    // actually covers is a NEW MCP reading a STALE PRE-DEPLOY cache that still
+    // holds one.
+    //
+    // The direction that DOES happen is not handled and cannot be: an OLD MCP
+    // reads the new string with resolveHostBooleanFlag, gets undefined, and keeps
+    // dispatching. That is a real regression against ENG-6506 until the fleet
+    // converges, and it is why the runbook makes convergence a deploy-order
+    // PRECONDITION rather than offering a boolean fallback — there is none, since
+    // an enum flag rejects `{value: true}` with a 400.
+    defaultValue: "off",
     // Flipping this takes the ENTIRE fleet offline to end users; a mis-flip is a
     // platform-wide availability incident, so mutations require explicit
     // confirmation (the admin flip-reach modal).
@@ -11702,6 +11753,51 @@ var OAUTH_PROVIDERS = {
       }
     ]
   },
+  "otter": {
+    // CS-2029: Otter.ai's official MCP — remote streamable-HTTP at
+    // https://mcp.otter.ai/mcp. Same Granola/Kajabi shape: OAuth 2.0
+    // authorization-code with PKCE (S256) and a public client
+    // (token_endpoint_auth_method 'none') issued via Dynamic Client
+    // Registration (RFC 7591). Values below are taken verbatim from the
+    // metadata, not inferred:
+    //   - https://mcp.otter.ai/.well-known/oauth-protected-resource names the
+    //     AS as https://otter.ai/ and advertises scopes profile:read,
+    //     conversations:read;
+    //   - https://otter.ai/.well-known/oauth-authorization-server gives
+    //     authorize /oauth2/authorize, token /oauth/token, revoke
+    //     /oauth/revoke_token, register /oauth/register, PKCE S256, `none`,
+    //     and the refresh_token grant.
+    // NOTE the authorize path is /oauth2/authorize while token/revoke live
+    // under /oauth/ — that is Otter's own split, do not "normalise" it.
+    // The prod client was registered 2026-10-10 against /oauth/register with
+    // scope 'profile:read conversations:read' and BOTH API callbacks,
+    // https://api.augmented.team/... and https://api.ninjafy.com/integrations/oauth/callback,
+    // because redirect_uri follows API_PUBLIC_URL and the ENG-11060 flip makes
+    // the ninjafy name canonical; Otter returns no RFC 7592 handle, so a redirect
+    // cannot be added later without a new client and a re-consent per connection.
+    // OAUTH_OTTER_CLIENT_ID is set from its output (docs/runbooks/otter-dogfood.md). Otter advertises ONLY
+    // read scopes, so this integration is read-only by construction: there is
+    // no write scope to request even by mistake.
+    definitionId: "otter",
+    authorizeUrl: "https://otter.ai/oauth2/authorize",
+    tokenUrl: "https://otter.ai/oauth/token",
+    revokeUrl: "https://otter.ai/oauth/revoke_token",
+    defaultScopes: ["profile:read", "conversations:read"],
+    supportsRefresh: true,
+    extraAuthorizeParams: {},
+    clientAuthMethod: "body",
+    pkce: "S256",
+    publicClient: true,
+    mcpUrl: "https://mcp.otter.ai/mcp",
+    // Curated surface (matches the catalog seed's defined_scopes[].tools).
+    // These are the server's three tools, all read-only. The names are
+    // Otter's own, quoted from the tools' descriptions ("use `otter_search`
+    // first", "call otter_get_user_info() first"), not Composio's wrapped
+    // OTTER_AI_MCP_* slugs. An allowlisted name the server does not advertise
+    // is logged and SKIPPED by the proxy, so confirm against the first live
+    // tools/list after a real consent (runbook Step 3).
+    toolAllowlist: ["otter_get_user_info", "otter_search", "otter_fetch"]
+  },
   "notion-cli": {
     // Notion's public OAuth app. Tokens are workspace-scoped and long-lived —
     // Notion does not issue refresh_tokens, so `supportsRefresh: false` and
@@ -16603,4 +16699,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-TZM6YVE7.js.map
+//# sourceMappingURL=chunk-OBZB6MUE.js.map