@integrity-labs/agt-cli 0.28.157 → 0.28.159

package/dist/bin/agt.js

@@ -37,7 +37,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-6VSS55A2.js";
+} from "../chunk-PGW3CTYR.js";
 import {
   CHANNEL_REGISTRY,
   DEPLOYMENT_TEMPLATES,
@@ -64,7 +64,7 @@ import {
   renderTemplate,
   resolveChannels,
   serializeManifestForSlackCli
-} from "../chunk-TLX6ORJ5.js";
+} from "../chunk-SAAK2IP4.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.157" : "dev";
+var cliVersion = true ? "0.28.159" : "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.157" : "dev";
+var cliVersion2 = true ? "0.28.159" : "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-6VSS55A2.js → chunk-PGW3CTYR.js}

@@ -22,7 +22,7 @@ import {
   resolveConnectivityProbe,
   worseConnectivityOutcome,
   wrapScheduledTaskPrompt
-} from "./chunk-TLX6ORJ5.js";
+} from "./chunk-SAAK2IP4.js";
 
 // ../../packages/core/dist/integrations/registry.js
 var INTEGRATION_REGISTRY = [
@@ -240,6 +240,32 @@ var INTEGRATION_REGISTRY = [
       envDefaults: { ANCHOR_BROWSER_SESSION_ID: "" }
     }
   },
+  {
+    id: "deck",
+    name: "Deck",
+    category: "workspace-productivity",
+    description: "Computer-use agents that operate any software through real interfaces (no API required) and return schema-validated results. Higher-level alternative to Anchor Browser: Deck owns the auth lifecycle (encrypted credential vault, login, MFA, CAPTCHA) and provisions isolated desktop sessions on demand.",
+    // Deck is REST-only (base https://api.deck.co/v2, Bearer `sk_live_` account
+    // key) — it ships NO MCP server, so unlike anchor-browser there is no
+    // `remoteMcp`/`nativeMcp` drop-in. Per-agent isolation is modelled on
+    // Deck's first-class resources: the control plane holds one account key
+    // (stored per-row as the `api_key` credential, same shape as anchor) and
+    // provisions one Deck agent (`agt_`) + vault credential (`cred_`) per
+    // Augmented agent via POST /:id/provision-deck. Those ids land in
+    // `agent_integrations.config` (deck_agent_id / deck_credential_id), so
+    // revocation + audit happen at the per-agent Deck-resource level without a
+    // distinct API key per agent (Deck exposes no key-minting admin API).
+    // The agent-facing tool surface is a follow-up (Deck has no MCP), so this
+    // entry is catalog + provisioning only for now.
+    supported_auth_types: ["api_key"],
+    capabilities: [
+      { id: "deck:provision", name: "Provision Agent Access", description: "Provision a per-agent Deck agent and vault credential under the account key (create_agent, create_credential)", access: "admin" },
+      { id: "deck:run", name: "Run Tasks", description: "Submit tasks to the agent and read schema-validated structured results (run_task, get_task_run)", access: "write" },
+      { id: "deck:observe", name: "Observe Sessions", description: "Read isolated session state, screenshots, and agent-reasoning artifacts (get_session)", access: "read" }
+    ],
+    docs_url: "https://docs.deck.co/",
+    beta: true
+  },
   {
     id: "postiz",
     name: "Postiz",
@@ -3646,14 +3672,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. "Silently skip" means write nothing too: 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.
+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
 
@@ -7894,7 +7924,7 @@ function requireHost() {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.157" : "dev";
+var agtCliVersion = true ? "0.28.159" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -9199,4 +9229,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-6VSS55A2.js.map
+//# sourceMappingURL=chunk-PGW3CTYR.js.map