@botbuddy/cli 1.28.0 → 1.29.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@botbuddy/cli",
-  "version": "1.28.0",
+  "version": "1.29.0",
   "description": "BotBuddy — Swarm coordination CLI for multi-agent workflows",
   "type": "module",
   "bin": {

package/src/commands.mjs

@@ -612,6 +612,9 @@ export function mcpHelp(log = console.log) {
                     ${cyan("botbuddy login")} owner/client credential), store it in the
                     Keychain under ${dim("BOTBUDDY_MCP_KEY")} (or --env <NAME>), and print
                     the .mcp.json / .codex/config.toml snippets that reference it.
+                    A bb_mcp_ key is tenant-sealed: on a machine serving more than
+                    one tenant, mint each tenant under a distinct --env <NAME> var
+                    and commit that repo's matching .botbuddy-agent.json mcp_env.
                     Refuses an occupied Keychain slot unless --force (revoke the
                     old key first — --force leaves it live server-side).
   revoke <agent_id> [--tenant <slug>] [--env <NAME>]

package/src/setup-block.mjs

@@ -65,6 +65,7 @@ export const SETUP_BLOCK = `SETUP — the connectivity ladder (install → conne
   3. bb mcp setup                           tier 2 · MCP key (bb_mcp_, tenant-bound) → Keychain + .mcp.json ($BOTBUDDY_MCP_KEY)
                                             (Keychainless host: the key is printed ONCE — store + export + edit .mcp.json yourself)
                                             the repo's pre-committed .botbuddy-agent.json binds tenant + mcp_env
+                                            multi-tenant machine: mint each tenant under a distinct --env <NAME> var (they collide otherwise)
   4. register_agent (over MCP)              tier 3 · session token (bb_agent_, per-session, 8 h)
   5. export BOTBUDDY_AGENT_KEY=<session_token>   and   BOTBUDDY_SESSION_ID=<session_id>
   6. bb wait                                needs the tier-3 token; bb run/test also accept $BOTBUDDY_SESSION_ID,