@weavetab/mcp 2.5.0-beta.2 → 2.5.0-beta.5

package/docs/cli/cli-commands.md

@@ -14,10 +14,14 @@ slug: cli-commands
 | Command | Description |
 |---|---|
 | `weavetab` | Start the MCP server (stdio mode — default for MCP clients). When run in a TTY without arguments, launches the interactive UI menu. |
-| `weavetab config` | Launch the 5-phase interactive configuration wizard. |
+| `weavetab --ws [--port N]` | Start the WebSocket daemon on `127.0.0.1` (default port `3000`). |
+| `weavetab --version` | Print version and exit. |
+| `weavetab config` | Launch the 6-phase interactive configuration wizard. |
 | `weavetab view` | Display the current active configuration report. Press **[R]** to view raw JSON, **[Q]** to quit. |
 | `weavetab reset` | Purge browser profiles, lockfiles, mutexes, session registries, and kill orphan browser processes. Accepts `--yes`/`-y` to skip confirmation prompts. |
 | `weavetab reload-ext` | Send a reload signal to the Weavetab browser extension via CDP `Runtime.evaluate`. |
+| `weavetab plugin <add\|browse\|search\|list\|remove\|verify>` | Manage plugins — see `weavetab plugin --help`. |
+| `weavetab skills [options]` | Install or update AI agent skills (passthrough to `@weavetab/skills`). |
 | `weavetab help` / `--help` | Show full CLI help message with all commands, flags, and environment variables. |
 
 ## Secrets Management
@@ -39,6 +43,8 @@ When run without arguments in a TTY terminal, Weavetab opens an interactive keyb
 |---|---|
 | `[C]` | Launch the configuration wizard |
 | `[V]` | View current active configuration |
+| `[P]` | List installed Weavetab plugins |
 | `[R]` | Purge browser profiles and lockfiles |
 | `[H]` | Show help information |
+| `[G]` / `[N]` / `[W]` | Open GitHub / npm / website links |
 | `[Q]` | Exit Weavetab |

package/docs/cli/cli-flags.md

@@ -1,6 +1,6 @@
 ---
 title: "Flags"
-description: "Global flags accepted by the server."
+description: "Global flags accepted by the CLI."
 product: mcp
 section: cli
 icon: Flag
@@ -9,12 +9,20 @@ slug: cli-flags
 
 # Flags
 
+Only these flags are parsed by the CLI (`MCP/src/index.ts`). Anything else is ignored.
+
 | Flag | Type | Description |
 |---|---|---|
-| `--version` | boolean | Print CLI version and exit |
 | `--help` / `-h` | boolean | Show help message and exit |
-| `--ws` | boolean | Start server in WebSocket mode instead of stdio |
-| `--port <port>` | number | Port for WebSocket server (default `3000`) |
-| `--headless` | boolean | Run browser in headless mode |
-| `--role <role>` | enum | Override RBAC role (`admin`, `operator`, `viewer`, `automation`) |
-| `--yes` / `-y` | boolean | Skip confirmation prompt when running `weavetab reset` |
+| `help` | command | Show help message and exit |
+| `--version` / `-v` | boolean | Print version and exit |
+| `--ws` | boolean | Start the WebSocket daemon instead of stdio |
+| `--port <port>` / `--port=<port>` | number | Port for the WebSocket daemon (default `3000`) |
+| `--yes` / `-y` | boolean | Skip confirmation prompt when running `weavetab reset` / `reload` |
+| `--official` / `-O` | boolean | Prefer the official `@weavetab/plugin-<name>` candidate (`plugin add`) |
+| `--community` / `-C` | boolean | Prefer the community package candidate (`plugin add`) |
+| `--refresh` | boolean | Invalidate and refresh the verified plugin cache (`plugin`) |
+| `--project` | boolean | Project-scoped secrets file (`secrets init --project`) |
+
+Notes:
+- There are no `--headless` / `--role` CLI flags. Browser headless mode and RBAC role come from `~/.weavetab/config.json` (`weavetab config` / `weavetab view`). The wizard offers `admin` / `operator` / `viewer` / `automation`.

package/docs/cli/cli-scripting.md

@@ -18,8 +18,11 @@ weavetab reset --yes
 # List stored secrets
 weavetab secrets list
 
-# Start the MCP server in WebSocket mode for custom scripts
-weavetab --ws --port 3000 --headless &
+# List installed plugins
+weavetab plugin list
+
+# Start the MCP server in WebSocket daemon mode for custom scripts
+weavetab --ws --port 3000 &
 ```
 
 ## CI/CD Pipeline
@@ -28,5 +31,5 @@ weavetab --ws --port 3000 --headless &
 # In GitHub Actions or Docker CI
 npm install -g @weavetab/mcp
 weavetab reset --yes
-weavetab --ws --port 3000 --headless &
+weavetab --ws --port 3000 &
 ```

package/docs/configuration/config-locations.md

@@ -1,6 +1,6 @@
 ---
 title: "Locations & Merge"
-description: "Three-tier merge: local → global → built-in defaults."
+description: "Two-tier merge: global config → built-in defaults."
 product: mcp
 section: configuration
 icon: FolderTree
@@ -11,9 +11,8 @@ slug: config-locations
 
 ## Priority Tiers
 
-1. **Local (Project-scoped)** — `./.weavetab/config.json` (takes top priority)
-2. **Global** — `~/.weavetab/config.json`
-3. **Built-in defaults** — defined in `DEFAULT_CONFIG`
+1. **Global** — `~/.weavetab/config.json` (the only config file Weavetab reads)
+2. **Built-in defaults** — defined in `DEFAULT_CONFIG`
 
 ## Live Reload
 

package/docs/configuration/env-variables.md

@@ -9,11 +9,11 @@ slug: env-variables
 
 # Environment Variables
 
+Only these two are read at runtime (`MCP/src/config/loader.ts`). Everything else
+(browser path, role, headless, dev mode) lives in `~/.weavetab/config.json`
+— run `weavetab config` to change it.
+
 | Variable | Description |
 |---|---|
-| `CHROME_PATH` | Absolute path to Chromium/Chrome binary |
-| `WEAVETAB_CONFIG` | Path to a custom config file |
-| `WEAVETAB_ROLE` | Override RBAC role at runtime (`admin`, `operator`, `viewer`, `automation`) |
-| `WEAVETAB_DEV` | Set to `1` to enable verbose CDP dev logging |
 | `WT_AGENT_ID` | Override the auto-generated agent UUID |
 | `WT_PROXY_URL` | Set outbound HTTP/SOCKS proxy server URL |

package/docs/configuration/folders.md

@@ -1,54 +1,55 @@
----
-title: "Folder Hierarchy"
-description: ".weavetab, .weavetab-system, and ~/.weavetab directory structure."
-product: mcp
-section: configuration
-icon: FolderOpen
-slug: folders
----
-
-# Workspace & System Directories
-
-Weavetab strictly partitions project-scoped output, global configurations, and system-level intelligence data into dedicated directory structures.
-
-## 1. Project-Scoped Directory: `./.weavetab/`
-
-Created in your current working directory to store project-scoped settings and mission output:
-
-```
-./.weavetab/
-├── config.json          # Project-specific config overrides
-├── secrets.json         # Project-scoped credentials for Blind Injection
-├── pdfs/                # Exported PDF documents
-├── screenshots/         # Full-page and clipped PNG/JPEG screenshots
-├── downloads/           # Downloaded files during automated sessions
-├── designs/             # Extracted design tokens and Tailwind themes
-└── logs/                # Human-readable logs and JSONL audit trails
-```
-
-## 2. System Intelligence Directory: `~/.weavetab-system/`
-
-Global system directory holding cross-session learning and process locks:
-
-```
-~/.weavetab-system/
-├── memory/                    # Per-domain frontend framework & strategy profiles
-├── sessions/
-│   └── context.json           # Rolling 50-action trail for loop detection
-├── apps/                      # Dedicated user profiles for Electron apps
-├── locks/                     # Process lockfiles (PID + TCP port validation)
-└── knowledge/                 # Domain-specific markdown knowledge hints
-```
-
-## 3. Global User Directory: `~/.weavetab/`
-
-Global user directory storing default configurations and global secrets:
-
-```
-~/.weavetab/
-├── config.json          # Global default configuration
-├── secrets.json         # Global secrets for Blind Injection
-├── policy.json          # Domain whitelist / blacklist rules
-├── plugins/             # Isolated storage directories for installed plugins
-└── profile/             # Dedicated default Chromium browser profile
-```
+---
+title: "Folder Hierarchy"
+description: ".weavetab, .weavetab-system, and ~/.weavetab directory structure."
+product: mcp
+section: configuration
+icon: FolderOpen
+slug: folders
+---
+
+# Workspace & System Directories
+
+Weavetab strictly partitions project-scoped output, global configurations, and system-level intelligence data into dedicated directory structures.
+
+## 1. Project-Scoped Directory: `./.weavetab/`
+
+Created in your current working directory to store project-scoped settings and mission output:
+
+```
+./.weavetab/
+├── config.json          # Project-specific config overrides
+├── secrets.json         # Project-scoped credentials for Blind Injection
+├── pdfs/                # Exported PDF documents
+├── screenshots/         # Full-page and clipped PNG/JPEG screenshots
+├── downloads/           # Downloaded files during automated sessions
+├── designs/             # Extracted design tokens and Tailwind themes
+└── logs/                # Human-readable logs and JSONL audit trails
+```
+
+## 2. System Intelligence Directory: `~/.weavetab-system/`
+
+Global system directory holding cross-session learning and process locks:
+
+```
+~/.weavetab-system/
+├── memory/                    # Per-domain frontend framework & strategy profiles (selector cache)
+│   └── sites/                 # Persistent site profiles: workflows, quirks & reliability scores
+├── sessions/
+│   └── context.json           # Rolling 50-action trail for loop detection
+├── apps/                      # Dedicated user profiles for Electron apps
+├── locks/                     # Process lockfiles (PID + TCP port validation)
+└── knowledge/                 # Domain-specific markdown knowledge hints
+```
+
+## 3. Global User Directory: `~/.weavetab/`
+
+Global user directory storing default configurations and global secrets:
+
+```
+~/.weavetab/
+├── config.json          # Global default configuration
+├── secrets.json         # Global secrets for Blind Injection
+├── policy.json          # Domain whitelist / blacklist rules
+├── plugins/             # Isolated storage directories for installed plugins
+└── profile/             # Dedicated default Chromium browser profile
+```

package/docs/desktop-automation/electron-apps.md

@@ -1,162 +1,214 @@
----
-title: "Desktop & Electron Apps"
-description: "Native Layer 0 automation for VS Code, Discord, Figma, Slack, and any Electron app."
-product: mcp
-section: desktop-automation
-badge: new
-icon: AppWindow
-slug: electron-apps
----
-
-# Desktop & Electron Application Automation
-
-Weavetab is a **universal Layer 0 agent runtime**. In addition to standard Chromium web browsing, Weavetab gives AI agents direct, native CDP control over **any desktop Electron application** — including Discord, VS Code, Figma, Slack, Obsidian, Postman, Notion, Spotify, and custom internal tools.
-
-## How It Works
-
-Because modern desktop applications are built on the Chromium/Electron framework, Weavetab can communicate with them directly over CDP WebSocket without requiring separate drivers or UI automation bridges.
-
-```text
-AI Agent (MCP) ──► withSecurity()
-                     ├── (Default) ─────────► CDP:9222 ──► Google Chrome / Chromium
-                     ├── (app: "discord") ──► CDP:9223 ──► Discord Desktop
-                     ├── (app: "figma")   ──► CDP:9224 ──► Figma Desktop
-                     └── (app: "vscode")  ──► CDP:9225 ──► VS Code Desktop
-```
-
-### Dual-Port Concurrency & Multi-Target Sessions
-- **Concurrent Execution**: Web browser sessions and Electron desktop app sessions run side-by-side on independent CDP ports (e.g. port `9222` for Chrome, `9223` for Discord, `9224` for Figma).
-- **Zero Session Clobbering**: Switching between a browser tab and a desktop app does not close, disconnect, or reload either target.
-- **Unified Tool Interface**: Pass `"app": "<appName>"` to any Weavetab tool to target that desktop application. Omit `app` to target the active web browser.
-
----
-
-## Interactive App Configurator & Agent Generator
-
-Use the interactive configurator below to customize your desktop applications. Select presets or add custom apps, toggle between executable path strings, remote debug ports, or advanced objects, and copy the ready-to-use JSON or an automated setup prompt for your AI coding agent:
-
-```electron-configurator
-```
-
----
-
-## 1. Configuring Desktop Apps in `config.json`
-
-Add an `"electron"` object to your local `./.weavetab/config.json` or global `~/.weavetab/config.json`:
-
-```json
-{
-  "electron": {
-    "discord": "C:\\Users\\username\\AppData\\Local\\Discord\\app-1.0.9175\\Discord.exe",
-    "vscode": 9222,
-    "figma": {
-      "path": "C:\\Users\\username\\AppData\\Local\\Figma\\Figma.exe",
-      "port": 9224,
-      "url": "https://www.figma.com",
-      "args": ["--enable-features=WebRTCPipeWireCapturer"]
-    },
-    "slack": "/Applications/Slack.app/Contents/MacOS/Slack",
-    "obsidian": "/usr/bin/obsidian"
-  }
-}
-```
-
-### Configuration Formats Supported
-
-| Format | Example | Description |
-|---|---|---|
-| **Executable Path String** | `"discord": "C:\\path\\to\\Discord.exe"` | Automatically launches the binary on an isolated port and dedicated profile. |
-| **Port Number** | `"vscode": 9222` | Attaches directly to an already-running instance started with `--remote-debugging-port=9222`. |
-| **Full Configuration Object** | `"figma": { "path": "...", "port": 9224, "url": "..." }` | Custom control over binary path, debug port, initial launch URL, custom profile directory, and startup CLI args. |
-
----
-
-## 2. Security & Profile Isolation
-
-Weavetab enforces enterprise-grade sandbox separation for all desktop applications:
-
-1. **Dedicated User Profiles**: Automated sessions are assigned isolated data profiles under `~/.weavetab-system/apps/<appName>/`.
-2. **Real AppData Protection**: Weavetab strictly enforces `assertNotRealElectronProfile` — attempting to target your primary OS user data directories (`%APPDATA%`, `~/Library/Application Support`, or `~/.config`) is blocked to protect your personal logins and local databases from accidental automation corruption.
-3. **Lock & Mutex Isolation**: Dedicated lockfiles (`~/.weavetab-system/locks/<appName>.lock`) ensure concurrent agent operations never conflict.
-
----
-
-## 3. Supported Desktop Schemes & Protocols
-
-Weavetab automatically allows and whitelist-bypasses desktop internal protocols:
-- `app://` (Electron internal resources)
-- `vscode-webview://` / `vscode-file://` (VS Code extensions and webviews)
-- `discord://` / `slack://` (Deep-links)
-- `devtools://` / `chrome://` / `about:`
-- `file:///` (Local files)
-
----
-
-## 4. How Agents Interact with Desktop Apps
-
-To target an Electron application, simply pass the `app` argument to any Weavetab tool:
-
-### A. Inspect Desktop DOM Tree
-```json
-{
-  "name": "browser_map",
-  "arguments": {
-    "app": "discord",
-    "scope": "main_content"
-  }
-}
-```
-
-### B. Click & Type in Desktop Apps
-```json
-{
-  "name": "browser_click",
-  "arguments": {
-    "ref": "w:42",
-    "app": "discord"
-  }
-}
-```
-
-```json
-{
-  "name": "browser_type",
-  "arguments": {
-    "ref": "w:45",
-    "text": "Automated build passed successfully! 🚀",
-    "app": "discord"
-  }
-}
-```
-
-### C. Multi-Target Burst Orchestration
-```json
-{
-  "name": "browser_burst",
-  "arguments": {
-    "app": "vscode",
-    "steps": [
-      { "action": "click_and_wait", "selector": ".monaco-editor" },
-      { "action": "type_and_send", "text": "npm test" }
-    ]
-  }
-}
-```
-
----
-
-## 5. Launching Existing Desktop Apps in Debug Mode
-
-If you prefer to attach Weavetab to your existing desktop app instance:
-
-```bash
-# Launch VS Code with CDP debugging enabled
-code --remote-debugging-port=9222
-
-# Launch Obsidian with CDP debugging enabled
-obsidian --remote-debugging-port=9225
-
-# Launch Discord with CDP debugging enabled
-discord --remote-debugging-port=9223
-```
-Then in your `config.json`, simply map `"vscode": 9222` or `"obsidian": 9225`.
+---
+title: "Desktop & Electron Apps"
+description: "Native Layer 0 automation for VS Code, Discord, Figma, Slack, and any Electron app."
+product: mcp
+section: desktop-automation
+badge: new
+icon: AppWindow
+slug: electron-apps
+---
+
+# Desktop & Electron Application Automation
+
+Weavetab is a **universal Layer 0 agent runtime**. In addition to standard Chromium web browsing, Weavetab gives AI agents direct, native CDP control over **any desktop Electron application** — including Discord, VS Code, Figma, Slack, Obsidian, Postman, Notion, Spotify, and custom internal tools.
+
+## How It Works
+
+Because modern desktop applications are built on the Chromium/Electron framework, Weavetab can communicate with them directly over CDP WebSocket without requiring separate drivers or UI automation bridges.
+
+```text
+AI Agent (MCP) ──► withSecurity()
+                     ├── (Default) ─────────► CDP:9222 ──► Google Chrome / Chromium
+                     ├── (app: "discord") ──► CDP:9223 ──► Discord Desktop
+                     ├── (app: "figma")   ──► CDP:9224 ──► Figma Desktop
+                     └── (app: "vscode")  ──► CDP:9225 ──► VS Code Desktop
+```
+
+### Dual-Port Concurrency & Multi-Target Sessions
+- **Concurrent Execution**: Web browser sessions and Electron desktop app sessions run side-by-side on independent CDP ports (e.g. port `9222` for Chrome, `9223` for Discord, `9224` for Figma).
+- **Zero Session Clobbering**: Switching between a browser tab and a desktop app does not close, disconnect, or reload either target.
+- **Unified Tool Interface**: Pass `"app": "<appName>"` to any Weavetab tool to target that desktop application. Omit `app` to target the active web browser.
+
+---
+
+## Interactive App Configurator
+
+Build your `electron` block in the [Desktop app configurator](/mcp/desktop) — presets for Discord, VS Code, Figma, Slack and more, path / port / advanced formats, plus a copy-ready agent setup prompt. Then paste the block into your global `~/.weavetab/config.json`.
+
+---
+
+## 1. Configuring Desktop Apps in `config.json`
+
+Add an `"electron"` object to your global `~/.weavetab/config.json` (the only config file Weavetab reads):
+
+```json
+{
+  "electron": {
+    "discord": "C:\\Users\\username\\AppData\\Local\\Discord\\app-<version>\\Discord.exe",
+    "vscode": 9222,
+    "figma": {
+      "path": "C:\\Users\\username\\AppData\\Local\\Figma\\Figma.exe",
+      "port": 9224,
+      "url": "https://www.figma.com",
+      "args": ["--enable-features=WebRTCPipeWireCapturer"]
+    },
+    "slack": "/Applications/Slack.app/Contents/MacOS/Slack",
+    "obsidian": "/usr/bin/obsidian"
+  }
+}
+```
+
+### Configuration Formats Supported
+
+| Format | Example | Description |
+|---|---|---|
+| **Executable Path String** | `"discord": "C:\\path\\to\\Discord.exe"` | Automatically launches the binary on an isolated port and dedicated profile. |
+| **Port Number** | `"vscode": 9222` | Attaches directly to an already-running instance started with `--remote-debugging-port=9222`. |
+| **Full Configuration Object** | `"figma": { "path": "...", "port": 9224, "url": "..." }` | Custom control over binary path, debug port, initial launch URL, custom profile directory, and startup CLI args. |
+
+---
+
+## 2. Security & Profile Isolation
+
+Weavetab enforces enterprise-grade sandbox separation for all desktop applications:
+
+1. **Dedicated User Profiles**: Automated sessions are assigned isolated data profiles under `~/.weavetab-system/apps/<appName>/`.
+2. **Real AppData Protection**: Weavetab strictly enforces `assertNotRealElectronProfile` — attempting to target your primary OS user data directories (`%APPDATA%`, `~/Library/Application Support`, or `~/.config`) is blocked to protect your personal logins and local databases from accidental automation corruption.
+3. **Lock & Mutex Isolation**: Dedicated lockfiles (`~/.weavetab-system/locks/<appName>.lock`) ensure concurrent agent operations never conflict.
+
+---
+
+## 3. Supported Desktop Schemes & Protocols
+
+Weavetab automatically allows and whitelist-bypasses desktop internal protocols:
+- `app://` (Electron internal resources)
+- `vscode-webview://` / `vscode-file://` (VS Code extensions and webviews)
+- `discord://` / `slack://` (Deep-links)
+- `devtools://` / `chrome://` / `about:`
+- `file:///` (Local files)
+
+---
+
+## 4. How Agents Interact with Desktop Apps
+
+To target an Electron application, simply pass the `app` argument to any Weavetab tool:
+
+### A. Inspect Desktop DOM Tree
+```json
+{
+  "name": "browser_map",
+  "arguments": {
+    "app": "discord",
+    "scope": "main_content"
+  }
+}
+```
+
+### B. Click & Type in Desktop Apps
+```json
+{
+  "name": "browser_click",
+  "arguments": {
+    "ref": "w:42",
+    "app": "discord"
+  }
+}
+```
+
+```json
+{
+  "name": "browser_type",
+  "arguments": {
+    "ref": "w:45",
+    "text": "Automated build passed successfully! 🚀",
+    "app": "discord"
+  }
+}
+```
+
+### C. Multi-Target Burst Orchestration
+```json
+{
+  "name": "browser_burst",
+  "arguments": {
+    "app": "vscode",
+    "steps": [
+      { "action": "click_and_wait", "selector": ".monaco-editor" },
+      { "action": "type_and_send", "text": "npm test" }
+    ]
+  }
+}
+```
+
+---
+
+## 5. Launching Existing Desktop Apps in Debug Mode
+
+If you prefer to attach Weavetab to your existing desktop app instance:
+
+```bash
+# Launch VS Code with CDP debugging enabled
+code --remote-debugging-port=9222
+
+# Launch Obsidian with CDP debugging enabled
+obsidian --remote-debugging-port=9225
+
+# Launch Discord with CDP debugging enabled
+discord --remote-debugging-port=9223
+```
+Then in your `config.json`, simply map `"vscode": 9222` or `"obsidian": 9225`.
+
+---
+
+## 6. Environment Discovery Handshake (`browser_detect`)
+
+`browser_detect` is the foundational tool agents invoke upon initial engagement. It inspects local browsers and configured desktop applications, returning their real-time state:
+
+```json
+{
+  "available": [
+    { "engine": "chromium", "name": "Google Chrome", "path": "C:\\Program Files\\...\\chrome.exe" }
+  ],
+  "current": "chromium",
+  "configuredApps": [
+    {
+      "name": "discord",
+      "status": "running_no_debug",
+      "configuredPath": "C:\\Users\\username\\AppData\\Local\\Discord\\app-1.0.9256\\Discord.exe"
+    },
+    {
+      "name": "slack",
+      "status": "connected",
+      "port": 9222,
+      "configuredPath": "C:\\Users\\username\\AppData\\Local\\slack\\app-4.38.125\\slack.exe",
+      "activeTabs": [
+        { "id": "PAGE_1", "title": "general - Slack", "url": "https://app.slack.com/client/..." }
+      ]
+    },
+    {
+      "name": "vscode",
+      "status": "offline",
+      "configuredPath": "C:\\Users\\username\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe"
+    }
+  ]
+}
+```
+
+### Application Lifecycle States:
+- **`connected`**: The app is running with CDP remote debugging active and Weavetab is attached. Agents can immediately operate tabs/windows using `"app": "<name>"`.
+- **`running_no_debug`**: The app process is currently running on the OS, but was opened by the user without `--remote-debugging-port`. Weavetab alerts the agent that DOM interactions are blocked until the app is launched or restarted with debugging flags.
+- **`offline`**: The process is not running. Calling `browser_navigate(app: "<name>")` launches and connects the app automatically.
+
+### Windows Squirrel Auto-Path Resolution:
+On Windows, applications like Discord and Slack install inside versioned folders (e.g. `Discord\app-1.0.9256\Discord.exe`) that change on every background update. Weavetab dynamically resolves the newest `app-1.0.xxxx` version at launch time, eliminating broken path errors after silent background updates.
+
+---
+
+## 7. Smart Domain Routing & Sticky Context
+
+To ensure external AI agents do not accidentally trigger a web browser launch when intending to control an Electron application:
+
+1. **Automatic Domain Routing**: When `browser_navigate` or `browser_tabs(action: "open")` receives an app domain (e.g. `discord.com`, `slack.com`, `linear.app`, `notion.so`), Weavetab automatically routes the target to the configured desktop application.
+2. **Sticky App Sessions**: When an agent operates inside an Electron app, the target session context remains sticky. Subsequent calls to `browser_tabs` or DOM tools stick to that active desktop app without spawning an unwanted Chrome window.
+3. **Explicit Browser Targeting**: When the agent specifically intends to use the web browser, passing `"app": "browser"` overrides desktop routing and directs operations to the web browser.
+