archer-wizard 0.2.0 → 0.2.2

package/src/wizard/injector.ts

@@ -6,16 +6,32 @@ import { logSuccess, logError, logAction } from '../lib/ascii.js';
 import { getConfigKey } from './detector.js';
 import type { AgentInfo, InjectionResult, McpServerEntry } from '../types/index.js';
 
-// ─── Archer MCP Entry ───────────────────────────────────────
+// ─── Archer MCP Entry (agent-aware) ─────────────────────────
 
-function buildArcherEntry(supabaseUrl: string, serviceRoleKey: string): McpServerEntry {
+function buildArcherEntry(
+  agentName: string,
+  supabaseUrl: string,
+  serviceRoleKey: string,
+): McpServerEntry {
+  const envVars = {
+    SUPABASE_URL: supabaseUrl,
+    SUPABASE_SERVICE_ROLE_KEY: serviceRoleKey,
+  };
+
+  // opencode uses { type, command[], environment }
+  if (agentName === 'opencode') {
+    return {
+      type: 'local',
+      command: ['npx', '-y', 'archer-wizard@latest', '--mcp'],
+      environment: envVars,
+    };
+  }
+
+  // cursor, claude-code, windsurf, antigravity use { command, args, env }
   return {
     command: 'npx',
     args: ['-y', 'archer-wizard@latest', '--mcp'],
-    env: {
-      SUPABASE_URL: supabaseUrl,
-      SUPABASE_SERVICE_ROLE_KEY: serviceRoleKey,
-    },
+    env: envVars,
   };
 }
 
@@ -51,7 +67,7 @@ function injectIntoAgent(
   try {
     const configKey = getConfigKey(agent.name);
     const config = readConfig(agent.configPath);
-    const archerEntry = buildArcherEntry(supabaseUrl, serviceRoleKey);
+    const archerEntry = buildArcherEntry(agent.name, supabaseUrl, serviceRoleKey);
 
     // Ensure the config key object exists
     if (!config[configKey] || typeof config[configKey] !== 'object') {

package/src/wizard/rules.ts

@@ -9,53 +9,75 @@ import type { AgentInfo } from '../types/index.js';
 const RULE_CONTENT = `
 # Archer — Event Intelligence for AI Agents
 
-Archer is the event intelligence layer for AI agents. It connects to your data sources (Supabase, GitHub, Stripe, Linear, etc.), watches for conditions you define in plain english, and fires your AI agent the moment those conditions are true, with full context already loaded.
+Archer is the universal event intelligence layer for AI agents. It watches your data sources in real time, detects changes the moment they happen, and delivers full context to your webhook — so your agent can react instantly, without polling.
 
-## Available Tool: archer.watch
+## Available MCP Tools
 
-You can watch real-time events from data sources using the \`archer.watch\` MCP tool.
+### archer_watch
+Create a persistent real-time watch on a data source. Watches survive agent session restarts.
 
-### When to Use Archer
+**Parameters:**
+- **table** *(required)* — name of the table or resource to watch
+- **event** — type of change: \`INSERT\`, \`UPDATE\`, \`DELETE\`, or \`*\` (all). Default: \`*\`
+- **filter** — optional filter expression, e.g. \`"status=eq.active"\` or \`"amount=gt.1000"\`
+- **webhookUrl** — URL to receive a POST with full event payload when a match fires
 
-Use Archer whenever you need to:
-- Monitor database changes (inserts, updates, deletes)
-- Watch for new user signups
-- React to events in external services
-- Automate responses to data changes
-- Set up real-time notifications
+### archer_unwatch
+Remove an active watch by its ID. Stops listening and cleans up.
 
-### Parameters
+**Parameters:**
+- **watchId** *(required)* — the watch ID returned by \`archer_watch\`
 
-- **source**: data source (currently \`"supabase"\`)
-- **event**: one of \`"auth.signup"\`, \`"table.insert"\`, \`"table.update"\`, \`"table.delete"\`
-- **table**: the table name (required for table events)
-- **condition**: optional filter like \`"email ends with @gmail.com"\`
-- **webhookUrl**: URL to receive POST notifications when events match
+### archer_watches
+List all active watches — their IDs, tables, events, filters, and webhook URLs.
 
-### Examples
+## When to Use Archer
 
-1. Watch for new user signups:
+Use Archer any time the user wants to:
+- **Monitor data changes** — new rows, updates, deletions in any table
+- **React to events** — trigger automations when conditions are met
+- **Set up alerts** — notify on signups, new orders, status changes, threshold breaches
+- **Build event-driven workflows** — chain watches with webhooks for real-time pipelines
+- **Track activity** — audit logs, user actions, system events
+
+## Examples
+
+1. Watch for new rows in a table:
+   \`\`\`
+   archer_watch({ table: "users", event: "INSERT", webhookUrl: "https://hooks.example.com/new-users" })
+   \`\`\`
+
+2. Watch for updates with a filter:
    \`\`\`
-   archer.watch({ source: "supabase", event: "auth.signup", webhookUrl: "https://hooks.example.com/signups" })
+   archer_watch({ table: "orders", event: "UPDATE", filter: "status=eq.shipped", webhookUrl: "https://hooks.example.com/shipped" })
    \`\`\`
 
-2. Watch for inserts to the orders table:
+3. Watch all changes on a table:
    \`\`\`
-   archer.watch({ source: "supabase", event: "table.insert", table: "orders", webhookUrl: "https://hooks.example.com/orders" })
+   archer_watch({ table: "payments", webhookUrl: "https://hooks.example.com/payments" })
    \`\`\`
 
-3. Watch with a condition:
+4. List active watches:
    \`\`\`
-   archer.watch({ source: "supabase", event: "table.insert", table: "users", condition: "email ends with @company.com", webhookUrl: "https://hooks.example.com/vip" })
+   archer_watches()
    \`\`\`
 
-### Best Practices
+5. Stop a watch:
+   \`\`\`
+   archer_unwatch({ watchId: "abc-123" })
+   \`\`\`
+
+## Best Practices
+
+- Add filters to reduce noise — only fire on events that matter
+- Use descriptive webhook URLs that map to specific actions
+- Chain multiple watches for complex event-driven workflows
+- Use \`archer_watches\` to inspect and manage active watchers
+- Clean up watches you no longer need with \`archer_unwatch\`
 
-- Use descriptive webhook URLs that indicate the action to take
-- Add conditions to filter events and reduce noise
-- Combine with your existing workflows for maximum impact
+## Trigger Words
 
-When the user asks to "watch", "monitor", "notify", or "fire" something, use Archer.
+When the user says **"watch"**, **"monitor"**, **"notify me"**, **"alert me"**, **"track"**, **"listen for"**, or **"fire when"** — use Archer.
 `.trim();
 
 // ─── Archer Block Markers ───────────────────────────────────

package/src/wizard/scanner.ts

@@ -2,7 +2,6 @@ import fs from 'node:fs';
 import path from 'node:path';
 import * as clack from '@clack/prompts';
 import { z } from 'zod';
-import { logSuccess, logError, maskCredential } from '../lib/ascii.js';
 import type { ScanResult, Framework } from '../types/index.js';
 
 // Helper to search for keys in files
@@ -236,28 +235,6 @@ export async function scanProject(cwd: string): Promise<ScanResult> {
 
   const { framework, hasSupabaseInstalled } = detectFramework(cwd);
 
-  // Log found credentials
-  if (supabaseUrl) {
-    logSuccess(`SUPABASE_URL = ${maskCredential(supabaseUrl)}`);
-  } else {
-    logError('missing SUPABASE_URL');
-  }
-
-  if (serviceRoleKey) {
-    logSuccess(`SUPABASE_SERVICE_ROLE_KEY = ${maskCredential(serviceRoleKey)}`);
-  } else {
-    logError('missing SUPABASE_SERVICE_ROLE_KEY');
-  }
-
-  if (anonKey) {
-    logSuccess(`SUPABASE_ANON_KEY = ${maskCredential(anonKey)}`);
-  }
-
-  if (foundInFile) {
-    logSuccess(`found credentials in ${foundInFile}`);
-  } else if (codebaseResults.size > 0) {
-    logSuccess(`found credentials in codebase`);
-  }
 
   return {
     supabaseUrl,