@hailer/mcp 1.1.12 → 1.1.13

package/.opencode/commands/swarm.md

@@ -1,210 +0,0 @@
----
-description: Orchestrator-driven parallel swarm for large-scale tasks
-argument-hint: "description of what to do across many items"
-allowed-tools: Task, Bash, Read, Glob
----
-
-# Swarm
-
-Orchestrator-driven parallel execution: analyze the task, discover work items, pick agents, split into chunks, dispatch workers, aggregate results.
-
-**Goal:** $ARGUMENTS
-
-## Protocol
-
-### Step 1: Analyze the Task
-
-Read `$ARGUMENTS` and determine:
-
-- **What needs to be done?** (review, edit, check, migrate, update, clean up)
-- **What are the work items?** (files, activities, workflows, agents, skills, configs)
-- **What scope?** (explicit path/glob from user, or infer from task description)
-
-If the scope is unclear, use Glob or Bash to discover items:
-
-```
-# Files
-Glob("src/**/*.ts")
-Glob(".claude/agents/*.md")
-Glob("workspace/*/fields.ts")
-
-# Activities (use Kenji to count/list)
-Task(subagent_type="agent-kenji-data-reader", prompt="Count and list activity IDs for [workflow]")
-```
-
-If fewer than 5 items are discovered, **abort swarm** and suggest running a regular squad or single agent instead. Swarm is for scale.
-
-### Step 2: Pick Agent(s)
-
-Based on the task type, select the right agent(s):
-
-| Task Type | Agent | Examples |
-|-----------|-------|---------|
-| Code review, security audit | **Svetlana** | "review for bugs", "security check", "find vulnerabilities" |
-| Dead code, unused imports, type errors | **Lars** | "find dead code", "check types", "unused imports" |
-| Small edits, string replacements, rule additions | **Simple Writer** | "add header to each file", "replace X with Y", "update rule" |
-| Code cleanup, simplification | **Code Simplifier** | "clean up", "simplify", "refactor for clarity" |
-| Config audit, structure validation | **Bjorn** | "check config", "validate structure", "audit settings" |
-| Data state checks, field validation | **Kenji** | "check all activities", "verify field values", "find missing data" |
-| Query patterns, data analysis | **Viktor** | "analyze patterns", "find anomalies across workflows" |
-| Activity updates, bulk mutations | **Dmitri** | "update all activities", "move to phase", "set field values" |
-
-**Multi-agent swarms:** If the task spans multiple domains, assign different agent types to different items. For example, "clean up the project" might use Lars for `.ts` files, Bjorn for config files, and Code Simplifier for app components.
-
-### Step 3: Calculate Workers
-
-```
-items_count = total discovered items
-items_per_worker = 10 (default)
-max_workers = 5
-
-worker_count = min(ceil(items_count / items_per_worker), max_workers)
-```
-
-Split items into `worker_count` chunks. Try to keep chunks roughly equal size.
-
-For multi-agent swarms, group items by agent type first, then chunk within each type.
-
-### Step 4: Dispatch Workers
-
-Launch all workers in parallel using multiple Task tool calls in a single message. All workers run in background (`run_in_background: true`).
-
-Each worker gets:
-
-```
-Task(subagent_type="[selected-agent]",
-  run_in_background: true,
-  prompt="SWARM WORKER [N] of [TOTAL]
-
-TASK: [User's description from $ARGUMENTS]
-
-YOUR ITEMS ([count]):
-- [item 1]
-- [item 2]
-- [item 3]
-...
-
-Process each item and report results in this format:
-
-RESULTS:
-- [item]: [status] - [details]
-- [item]: [status] - [details]
-
-SUMMARY:
-- Processed: [count]
-- Passed: [count]
-- Issues found: [count]
-- Failed: [count]")
-```
-
-Tell the user:
-```
-Launched [worker_count] workers across [items_count] items.
-Running in background - what else do you want to work on?
-```
-
-### Step 5: Collect Results
-
-When workers complete (check via Read on output files or TaskOutput), aggregate all results.
-
-If any worker failed or timed out:
-- Report which items were in the failed worker's batch
-- Offer to retry just those items
-
-### Step 6: Report
-
-```markdown
-## Swarm Report
-
-### Task
-[User's description]
-
-### Execution
-- **Items:** [total count]
-- **Workers:** [worker count] x [agent type(s)]
-- **Duration:** [time from dispatch to last worker completion]
-
----
-
-### Results by Worker
-
-#### Worker 1 ([agent type]) - [X items]
-- [item]: [status] - [details]
-- [item]: [status] - [details]
-...
-
-#### Worker 2 ([agent type]) - [X items]
-...
-
----
-
-### Aggregate Summary
-
-| Status | Count |
-|--------|-------|
-| Passed / Clean | X |
-| Issues Found | X |
-| Failed / Error | X |
-
-### Issues Found
-[Grouped and deduplicated list of all issues across all workers]
-
-1. **[item]**: [issue description]
-2. **[item]**: [issue description]
-...
-
-### Failed Items
-[If any workers failed, list their items for retry]
-
-### Next Steps
-- [Suggested follow-up based on results]
-- [If issues found: suggest /hotfix-squad or Simple Writer to fix]
-- [If edits made: suggest /review-squad to verify]
-```
-
-## Options
-
-| Flag | Effect |
-|------|--------|
-| `--workers=N` | Override worker count (default: auto-calculated, max 5) |
-| `--dry-run` | Show what would be dispatched without actually running |
-| `--no-bg` | Run workers in foreground (wait for all to complete) |
-
-## Examples
-
-```
-# Review all source files for security
-/swarm "review all TypeScript files in src/ for security vulnerabilities"
-→ Discovers 47 .ts files, spawns 5 Svetlana workers
-
-# Bulk edit agent files
-/swarm "add a '## Version History' section to every agent file"
-→ Discovers 27 agent .md files, spawns 3 Simple Writer workers
-
-# Validate workspace configs
-/swarm "check all workflow field definitions for missing descriptions"
-→ Discovers 12 fields.ts files, spawns 2 Kenji workers
-
-# Multi-agent cleanup
-/swarm "clean up the entire apps/ directory"
-→ Discovers 34 files: 20 .tsx → Code Simplifier, 8 .ts → Lars, 6 configs → Bjorn
-→ Spawns 5 workers across 3 agent types
-
-# Data validation
-/swarm "verify all Customer activities have a valid email field"
-→ Kenji counts 200 customers, spawns 5 Kenji workers (40 each)
-
-# Dry run to preview
-/swarm "update all skills to use consistent headers" --dry-run
-→ Shows: "Would dispatch 4 Simple Writer workers across 32 skill files"
-```
-
-## Notes
-
-- Minimum 5 items to trigger swarm (below that, use a regular agent)
-- Default max 5 workers to avoid overwhelming the system
-- Workers run in background by default so user can keep working
-- Multi-agent swarms naturally emerge from the orchestrator's routing logic
-- For write operations (Dmitri, Simple Writer), consider running --dry-run first
-- Swarm vs Squad: Swarm is raw parallel execution without quality gates. Workers operate independently. Squads have convergence, synthesis, and loops. Use swarm for bulk independent items, squads for coordinated workflows.
-- Swarm + squad can combine: `/swarm "review src/"` finds issues, then user can run `/hotfix-squad` on results. This is a manual handoff - user confirms.

package/.opencode/commands/tool-builder.md

@@ -1,39 +0,0 @@
----
-description: Activate tool-builder mode to implement a new MCP tool
----
-
-# Tool Builder Mode
-
-Loading `tool-builder` skill for MCP tool patterns...
-
-**What tool should I build?**
-
-Please provide:
-
-- **Tool Name**: `tool_name` (snake_case)
-- **Purpose**: What does it do?
-- **API Endpoint**: `v3.endpoint.method`
-- **Request Format**: `[arg1, arg2]`
-- **Response Format**: What the API returns
-- **Target File**: Which file in `src/mcp/tools/`?
-- **Tool Group**: READ | WRITE | PLAYGROUND
-
----
-
-**Example:**
-```
-Tool Name: list_insights
-Purpose: List all insights in workspace
-API Endpoint: v3.insight.list
-Request: [workspaceId]
-Response: { insights: [{_id, name, query, sources}] }
-Target File: insight.ts
-Tool Group: PLAYGROUND
-```
-
-I'll:
-1. Load tool-builder skill
-2. Read existing patterns in target file
-3. Implement the tool
-4. Register in src/app.ts
-5. Report what was created

package/.opencode/commands/ws-pull.md

@@ -1,44 +0,0 @@
----
-description: Pull workspace configuration from Hailer (READ-ONLY)
----
-
-Pull the current workspace configuration from Hailer and save it locally.
-
-**What this does:**
-- Downloads workflows, insights, teams, groups, and phases from Hailer workspace
-- Saves configuration as JSON files to the `WORKSPACE_CONFIG_PATH` directory
-- READ-ONLY operation - does not modify anything on Hailer
-- Safe to run anytime
-
-**Requirements:**
-- Must have `WORKSPACE_CONFIG_PATH` set in `.env.local`
-- Hailer credentials must be configured
-
-**Instructions for Claude:**
-
-1. Read `.env.local` file to get `WORKSPACE_CONFIG_PATH`
-2. Run: `cd "$WORKSPACE_CONFIG_PATH" && npm run pull`
-3. **AUTOMATICALLY read the generated files to load context:**
-   - Read `workspace/enums.ts` (complete file - contains ALL field and phase IDs)
-   - List `workspace/` directory to see all workflow folders
-   - Read 1-2 example workflow configs (main.ts, fields.ts, phases.ts) to understand structure
-4. Provide summary of what workflows were pulled and confirm context is loaded
-
-**What gets downloaded:**
-- `workspace/enums.ts` - Type-safe field and phase ID enums for ALL workflows
-- `workspace/workflows.ts` - Main workflows export
-- `workspace/insights.ts` - SQL insight definitions
-- `workspace/teams.ts` - Team structures
-- `workspace/groups.ts` - User groups
-- `workspace/<workflow_name>/` - Individual workflow configs (main.ts, fields.ts, phases.ts)
-
-**Why automatic reading matters:**
-- Loads all field/phase IDs into conversation context immediately
-- Enables local-first strategy without manual file reads
-- Saves 75% of API calls and hundreds of tokens on subsequent operations
-- You'll know the workspace structure instantly
-
-**Common use cases:**
-- Backup current workspace configuration
-- Review workflow structures locally
-- Prepare for making configuration changes

package/.opencode/opencode.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "https://opencode.ai/config.json",
-  "permission": {
-    "bash": {
-      "*": "ask",
-      "rm -rf *": "deny",
-      "rm -r *": "deny"
-    },
-    "doom_loop": "ask",
-    "read": {
-      "*": "allow",
-      "*.env": "deny",
-      "*.env.*": "deny",
-      "*.env.example": "allow"
-    },
-    "edit": "ask",
-    "external_directory": "ask",
-    "webfetch": "ask",
-    "websearch": "ask"
-  },
-  "mcp": {
-    "hailer": {
-      "type": "remote",
-      "url": "http://localhost:3030/api/mcp?apiKey=unique-api-key-for-this-agent",
-      "enabled": true
-    }
-  }
-}

package/SESSION-HANDOFF.md

@@ -1,68 +0,0 @@
-# Session Handoff
-
-**Last Updated:** 2026-03-04
-
-## What Was Done
-
-### System Prompt — Full End-to-End Wiring
-Wired `systemPrompt` field from Agent Directory through the entire bot pipeline:
-
-- **`src/bot-config/constants.ts`** — added `FIELD_KEY_SYSTEM_PROMPT`
-- **`src/bot-config/context.ts`** — `BotSchema.fields.systemPrompt`, `BotCredentials.systemPrompt`, schema discovery, `extractCredentials()`
-- **`src/bot-config/webhooks.ts`** — extract systemPrompt in `extractCredentialsFromActivity()`
-- **`src/bot-config/loader.ts`** — `BotConfigFile` types + `saveBotConfig()` includes systemPrompt
-- **`src/bot/bot-config.ts`** — `BotConfig.systemPrompt`, reads from `orchestrator.systemPrompt`
-- **`src/bot/bot-manager.ts`** — `BotUpdateEntry.systemPrompt`, passes to Bot; smart restart logic: if only systemPrompt changed (credentials same) → `bot.updateSystemPrompt()` without restart
-- **`src/bot/bot.ts`** — `_systemPrompt` instance field (hot-swappable), `updateSystemPrompt()` public method, `buildSystemPrompt()` uses custom prompt + always appends `<bot-identity>` + `<workspace-context>`
-- **`src/commands/seed-config.ts`** — `extractSystemPromptFromActivity()`, wired into orchestrator + specialist output
-- **`src/mcp/webhook-handler.ts`** — `BotEntry.systemPrompt`, `WorkspaceConfig.orchestrator.systemPrompt`, extracts from webhook payload
-
-### System Prompt Design
-- Custom prompt from AI Hub used as full body; `{wsName}`, `{userId}`, `{botName}` substituted at runtime
-- `<bot-identity>` and `<workspace-context>` always appended by bot — never stored
-- Workspace-isolated: each `Bot` instance has own `_systemPrompt`, `BotManager.bots` Map keyed by workspaceId
-- Phase change → full restart picks up new prompt from config file
-- Field edit → webhook fires (with delay) → `handleBotConfigWebhook()` → `updateSystemPrompt()` (no restart)
-
-## Current Work
-
-### Uncommitted — All System Prompt Changes
-10 files modified, compiles clean (`tsc --noEmit` passes). Not yet committed or pushed.
-
-## Next Steps
-
-1. **Commit the system prompt wiring** — all 10 files are ready
-2. **Test end-to-end**: edit prompt in AI Hub → wait for webhook → verify bot uses new prompt
-3. **Cloudflare** — user mentioned needing this (for remote MCP / public webhook URL). See `docs/prd-remote-mcp-server.md` and `docs/prd-remote-mcp-connector.md`
-4. **`activityId` passthrough** (optional improvement) — pass orchestrator's `activityId` into Bot so it can subscribe to `activities.updated` socket signal for instant prompt updates (vs waiting for webhook)
-
-## Key Decisions
-
-- **Hot-swap without restart**: Only credentials change triggers bot restart; systemPrompt-only changes apply live via `updateSystemPrompt()`
-- **Workspace isolation**: Guaranteed by `Map<workspaceId, Bot>` — webhook `cid` field routes to correct bot instance
-- **Webhook-driven updates**: Phase change → webhook (requires public URL). Field-only changes → webhook fires with delay. Socket `activities.updated` would be instant but requires `activityId` passthrough (not yet done)
-- **Prompt structure**: Custom prompt replaces the rules section; `<bot-identity>` + `<workspace-context>` always runtime-injected
-
-## Files Modified (uncommitted)
-
-- `src/bot-config/constants.ts` — FIELD_KEY_SYSTEM_PROMPT
-- `src/bot-config/context.ts` — BotSchema, BotCredentials, discovery, extractCredentials
-- `src/bot-config/loader.ts` — BotConfigFile types + saveBotConfig
-- `src/bot-config/webhooks.ts` — extractCredentialsFromActivity
-- `src/bot/bot-config.ts` — BotConfig + loadBotConfigs
-- `src/bot/bot-manager.ts` — BotUpdateEntry, smart restart, updateSystemPrompt call
-- `src/bot/bot.ts` — _systemPrompt field, updateSystemPrompt(), buildSystemPrompt(), email/password getters
-- `src/commands/seed-config.ts` — extractSystemPromptFromActivity + wired into output
-- `src/mcp/webhook-handler.ts` — BotEntry, WorkspaceConfig types + extraction
-
-## Context to Preserve
-
-- Agent Directory workflow ID: `69885261c432a499a35313b6`
-- Deployed phase: `8fa543c69749ab4e8f9e3967`, Retired phase: `df66a80fe7cfde1c3b928038`
-- AI Hub app: `695e3665701ef8e3824beebe`, marketplace targetId: `698351e8dda756e689368b60`
-- `systemPrompt` field key must be exactly `systemPrompt` (camelCase) — field type: textarea
-- **seed-config.ts is an independent copy** of field extraction — NOT shared with context.ts. Always update both when adding new Agent Directory fields
-- **Two bot-config readers**: `src/bot-config/loader.ts` (BotContext/webhook path) AND `src/bot/bot-config.ts` (BotManager startup path) — both need updating
-- **webhook-handler.ts has its own local types** (BotEntry, WorkspaceConfig) — update independently
-- Webhook fires on phase changes; field edits may have delay before webhook triggers
-- `app-edit-guard --agent-on` does NOT propagate to subagents — do ai-hub edits directly

package/inbox/2026-03-04-bot-config-patterns.md

@@ -1,24 +0,0 @@
-# Bot Config Field Wiring Patterns
-
-**Date:** 2026-03-04
-**Context:** Adding systemPrompt field to Agent Directory pipeline
-
-## Key Gotchas
-
-### seed-config.ts is an independent copy
-`src/commands/seed-config.ts` has its own field extraction logic completely separate from `src/bot-config/context.ts`. When adding a new Agent Directory field, you MUST update BOTH files — they don't share code.
-
-### Two separate bot-config readers
-- `src/bot-config/loader.ts` — BotContext system, used by webhook/signal path
-- `src/bot/bot-config.ts` — simple flat reader, used by BotManager on startup
-
-Both read from `.bot-config/*.json` but in different ways. Both need updating when adding new fields.
-
-### webhook-handler.ts has its own local types
-`BotEntry` and `WorkspaceConfig` are defined locally inside `webhook-handler.ts`, not imported from anywhere. Must update them independently when adding fields.
-
-### Webhook fires on phase changes only (with delay)
-Field edits (e.g. systemPrompt) trigger the webhook but with a delay — Hailer batches/debounces. Phase changes are more immediate. For truly instant field-change detection, subscribe to the `activities.updated` socket signal inside the Bot (requires knowing the bot's own `activityId`).
-
-### Hot-swap system prompts without restart
-Pattern for live-updatable config in Bot: store as a separate instance field (`_systemPrompt`) distinct from `this.config`. Expose `updateSystemPrompt(prompt)` public method. BotManager can call it without restarting the bot — only restart when credentials actually change.

package/scripts/postinstall.cjs

@@ -1,64 +0,0 @@
-#!/usr/bin/env node
-/**
- * postinstall: Copies .claude/ (agents, skills, hooks) to the project root.
- * Runs automatically after `npm install @hailer/mcp`.
- * Skips when installing in the hailer-mcp repo itself (development).
- */
-const fs = require('fs');
-const path = require('path');
-
-// Find the project root by walking up from node_modules/@hailer/mcp/
-function findProjectRoot() {
-  let dir = __dirname;
-  // Walk up until we find a package.json that isn't ours
-  for (let i = 0; i < 10; i++) {
-    dir = path.dirname(dir);
-    const pkgPath = path.join(dir, 'package.json');
-    if (fs.existsSync(pkgPath)) {
-      try {
-        const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf8'));
-        // Skip if this is our own package.json
-        if (pkg.name === '@hailer/mcp') continue;
-        return dir;
-      } catch { continue; }
-    }
-  }
-  return null;
-}
-
-function copyDir(src, dest) {
-  if (!fs.existsSync(src)) return;
-  fs.mkdirSync(dest, { recursive: true });
-
-  for (const entry of fs.readdirSync(src, { withFileTypes: true })) {
-    const srcPath = path.join(src, entry.name);
-    const destPath = path.join(dest, entry.name);
-
-    if (entry.isDirectory()) {
-      copyDir(srcPath, destPath);
-    } else {
-      // Don't overwrite user's local settings
-      if (entry.name === 'settings.local.json' && fs.existsSync(destPath)) continue;
-      fs.copyFileSync(srcPath, destPath);
-    }
-  }
-}
-
-const projectRoot = findProjectRoot();
-
-// Skip if we can't find a project root or if running in dev (our own repo)
-if (!projectRoot) {
-  console.log('@hailer/mcp: skipping agent install (no project root found)');
-  process.exit(0);
-}
-
-const src = path.join(__dirname, '..', '.claude');
-const dest = path.join(projectRoot, '.claude');
-
-if (!fs.existsSync(src)) {
-  console.log('@hailer/mcp: no .claude/ directory in package, skipping');
-  process.exit(0);
-}
-
-copyDir(src, dest);
-console.log(`@hailer/mcp: agents installed to ${dest}`);

package/scripts/test-hal-tools.ts

@@ -1,154 +0,0 @@
-#!/usr/bin/env npx ts-node
-/**
- * HAL Tools Test - Simple version
- * Just calls each tool and shows the result. No magic.
- */
-
-import * as dotenv from 'dotenv';
-import * as path from 'path';
-
-dotenv.config({ path: path.join(__dirname, '..', '.env.local') });
-
-const MCP_URL = process.env.MCP_SERVER_URL || 'http://localhost:3030/api/mcp';
-
-async function call(apiKey: string, tool: string, args: Record<string, unknown> = {}) {
-  console.log(`\n>>> ${tool}`);
-  console.log(`    args: ${JSON.stringify(args)}`);
-
-  const res = await fetch(`${MCP_URL}?apiKey=${apiKey}`, {
-    method: 'POST',
-    headers: { 'Content-Type': 'application/json' },
-    body: JSON.stringify({
-      jsonrpc: '2.0',
-      id: '1',
-      method: 'tools/call',
-      params: { name: tool, arguments: args },
-    }),
-  });
-
-  const text = await res.text();
-  for (const line of text.split('\n')) {
-    if (line.startsWith('data: ')) {
-      const data = JSON.parse(line.substring(6));
-      if (data.error) {
-        console.log(`<<< ERROR: ${data.error.message}`);
-        return { error: true, data: null };
-      }
-      const content = data.result?.content?.[0]?.text || '';
-      // Show first 500 chars
-      console.log(`<<< ${content.substring(0, 500)}${content.length > 500 ? '...' : ''}`);
-      return { error: false, content };
-    }
-  }
-  console.log('<<< NO RESPONSE');
-  return { error: true, data: null };
-}
-
-async function main() {
-  const apiKey = process.env.MCP_CLIENT_API_KEY;
-  if (!apiKey) {
-    console.error('Set MCP_CLIENT_API_KEY in .env.local');
-    process.exit(1);
-  }
-
-  console.log('=== HAL TOOLS TEST ===\n');
-
-  // Get a workflow to work with
-  const wf = await call(apiKey, 'list_workflows_minimal', {});
-  const wfMatch = wf.content?.match(/`([a-f0-9]{24})`/);
-  const workflowId = wfMatch?.[1];
-  console.log(`\n[Using workflowId: ${workflowId}]`);
-
-  if (!workflowId) {
-    console.log('No workflow found, stopping');
-    process.exit(1);
-  }
-
-  // Get phase
-  const ph = await call(apiKey, 'list_workflow_phases', { workflowId });
-  const phMatch = ph.content?.match(/`([a-f0-9]{24})`/);
-  const phaseId = phMatch?.[1];
-  console.log(`\n[Using phaseId: ${phaseId}]`);
-
-  // Schema
-  await call(apiKey, 'get_workflow_schema', { workflowId, phaseId });
-
-  // List activities
-  await call(apiKey, 'list_activities', { workflowId, phaseId, fields: '[]' });
-
-  // Count
-  await call(apiKey, 'count_activities', { workflowId });
-
-  // Create activity
-  const created = await call(apiKey, 'create_activity', {
-    workflowId,
-    name: `TEST_${Date.now()}`
-  });
-  const actMatch = created.content?.match(/\*\*ID\*\*:\s*([a-f0-9]{24})/);
-  const activityId = actMatch?.[1];
-  console.log(`\n[Created activityId: ${activityId}]`);
-
-  if (activityId) {
-    // Show it
-    await call(apiKey, 'show_activity_by_id', { activityId });
-
-    // Update it
-    await call(apiKey, 'update_activity', { activityId, name: `UPDATED_${Date.now()}` });
-
-    // Delete it (this tool doesn't exist yet)
-    await call(apiKey, 'delete_activity', { activityId });
-  }
-
-  // Insights
-  await call(apiKey, 'list_insights', {});
-
-  const sources = [{
-    name: 'src',
-    workflowId,
-    fields: [{ meta: 'name', name: 'Name', as: 'name' }]
-  }];
-
-  await call(apiKey, 'preview_insight', { sources, query: 'SELECT * FROM src LIMIT 3' });
-
-  const ins = await call(apiKey, 'create_insight', {
-    name: `TEST_${Date.now()}`,
-    sources,
-    query: 'SELECT * FROM src LIMIT 3'
-  });
-  const insMatch = ins.content?.match(/`([a-f0-9]{24})`/);
-  const insightId = insMatch?.[1];
-
-  if (insightId) {
-    await call(apiKey, 'get_insight_data', { insightId });
-    await call(apiKey, 'remove_insight', { insightId });
-  }
-
-  // Discussions
-  await call(apiKey, 'list_my_discussions', {});
-
-  if (activityId) {
-    await call(apiKey, 'join_discussion', { activityId });
-    // Get discussion from activity
-    const act = await call(apiKey, 'show_activity_by_id', { activityId });
-    const discMatch = act.content?.match(/discussion.*?([a-f0-9]{24})/i);
-    const discussionId = discMatch?.[1];
-
-    if (discussionId) {
-      await call(apiKey, 'fetch_discussion_messages', { discussionId });
-      await call(apiKey, 'add_discussion_message', { discussionId, content: 'TEST' });
-      await call(apiKey, 'get_activity_from_discussion', { discussionId });
-      await call(apiKey, 'leave_discussion', { discussionId });
-    }
-  }
-
-  // Other
-  await call(apiKey, 'list_workflows', {});
-  await call(apiKey, 'list_apps', {});
-  await call(apiKey, 'list_templates', {});
-  await call(apiKey, 'get_workspace_balance', {});
-  await call(apiKey, 'search_workspace_users', { query: 'test' });
-
-  console.log('\n=== DONE ===');
-}
-
-main().catch(console.error);