@weavetab/mcp 2.5.0 → 2.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (168) hide show
  1. package/AGENTS.md +49 -49
  2. package/ARCHITECTURE.md +590 -590
  3. package/LICENSE +216 -216
  4. package/README.md +269 -269
  5. package/SECURITY.md +207 -207
  6. package/TROUBLESHOOTING.md +373 -365
  7. package/dist/anticaptcha/detector.js +395 -395
  8. package/dist/anticaptcha/solver.js +130 -130
  9. package/dist/cdp/bridge.js +73 -73
  10. package/dist/cdp/connector.js +46 -22
  11. package/dist/cdp/extension.js +34 -34
  12. package/dist/cdp/helpers.js +174 -174
  13. package/dist/cdp/pruner.js +195 -195
  14. package/dist/cdp/ref_cache.js +66 -66
  15. package/dist/cdp/security.js +10 -10
  16. package/dist/cdp/verify.js +57 -57
  17. package/dist/cdp/walker.js +563 -525
  18. package/dist/cli/plugin.js +26 -3
  19. package/dist/config/loader.d.ts +0 -3
  20. package/dist/config/loader.js +0 -9
  21. package/dist/index.js +0 -4
  22. package/dist/intelligence/intent.js +81 -81
  23. package/dist/intelligence/sessionMemory.js +2 -2
  24. package/dist/overlay/ghost.js +22 -22
  25. package/dist/overlay/injector.js +89 -89
  26. package/dist/plugin/extension_bridge.js +54 -54
  27. package/dist/plugin/interface.d.ts +7 -0
  28. package/dist/plugin/loader.js +3 -4
  29. package/dist/plugin/schema.d.ts +11 -0
  30. package/dist/plugin/schema.js +59 -0
  31. package/dist/security/guard.js +18 -18
  32. package/dist/sensors/actionability.js +167 -167
  33. package/dist/sensors/guard.js +29 -29
  34. package/dist/sensors/network.js +15 -17
  35. package/dist/server.d.ts +1 -1
  36. package/dist/server.js +173 -144
  37. package/dist/state/delta.js +6 -7
  38. package/dist/tools/automation.js +85 -85
  39. package/dist/tools/canvas.js +48 -25
  40. package/dist/tools/checkpoint.js +94 -35
  41. package/dist/tools/click.js +52 -41
  42. package/dist/tools/clipboard.js +80 -74
  43. package/dist/tools/design_extract.js +441 -441
  44. package/dist/tools/dialog.js +13 -13
  45. package/dist/tools/emulation.d.ts +2 -0
  46. package/dist/tools/emulation.js +7 -0
  47. package/dist/tools/fill.js +344 -347
  48. package/dist/tools/find.js +78 -52
  49. package/dist/tools/highlight.js +67 -67
  50. package/dist/tools/inspect.js +54 -25
  51. package/dist/tools/key.js +42 -35
  52. package/dist/tools/navigate.d.ts +1 -1
  53. package/dist/tools/navigate.js +35 -35
  54. package/dist/tools/office/parse.js +62 -18
  55. package/dist/tools/pdf.d.ts +9 -0
  56. package/dist/tools/pdf.js +7 -4
  57. package/dist/tools/performance.d.ts +11 -4
  58. package/dist/tools/performance.js +94 -42
  59. package/dist/tools/performance_test.d.ts +2 -2
  60. package/dist/tools/performance_test.js +69 -69
  61. package/dist/tools/pointer.js +116 -116
  62. package/dist/tools/read.js +99 -67
  63. package/dist/tools/recording.js +9 -0
  64. package/dist/tools/scrape.js +146 -146
  65. package/dist/tools/screenshot.d.ts +2 -0
  66. package/dist/tools/screenshot.js +46 -4
  67. package/dist/tools/scroll.d.ts +3 -1
  68. package/dist/tools/scroll.js +13 -15
  69. package/dist/tools/select.d.ts +3 -0
  70. package/dist/tools/select.js +131 -124
  71. package/dist/tools/snapshot.js +8 -6
  72. package/dist/tools/storage.d.ts +5 -1
  73. package/dist/tools/storage.js +16 -0
  74. package/dist/tools/tabs.d.ts +7 -5
  75. package/dist/tools/tabs.js +79 -26
  76. package/dist/tools/thought.js +8 -8
  77. package/dist/tools/type.js +274 -274
  78. package/dist/tools/type_secret.js +23 -23
  79. package/dist/tools/upload.js +3 -3
  80. package/dist/tools/video_compiler.js +9 -0
  81. package/dist/tools/wait.js +35 -35
  82. package/dist/version.d.ts +1 -1
  83. package/dist/version.js +1 -1
  84. package/docs/DOCUMENTATION.md +583 -585
  85. package/docs/PLUGINS.md +139 -121
  86. package/docs/TOOLS.md +3 -4
  87. package/docs/architecture/blind-injection.md +83 -83
  88. package/docs/architecture/overview.md +49 -49
  89. package/docs/architecture/security.md +36 -36
  90. package/docs/architecture/transport.md +37 -37
  91. package/docs/cli/cli-commands.md +50 -50
  92. package/docs/cli/cli-flags.md +28 -28
  93. package/docs/cli/cli-scripting.md +35 -35
  94. package/docs/configuration/config-locations.md +23 -23
  95. package/docs/configuration/configuration.md +39 -27
  96. package/docs/configuration/env-variables.md +19 -19
  97. package/docs/configuration/folders.md +62 -55
  98. package/docs/desktop-automation/electron-apps.md +225 -214
  99. package/docs/get-started/installation.md +1 -1
  100. package/docs/get-started/introduction.md +60 -60
  101. package/docs/get-started/quickstart.md +2 -2
  102. package/docs/get-started/setup-wizard.md +27 -27
  103. package/docs/intelligence/site-profiles.md +151 -151
  104. package/docs/tools/tools.md +582 -631
  105. package/docs/troubleshooting/trouble-browser.md +27 -27
  106. package/docs/troubleshooting/trouble-loop.md +31 -31
  107. package/ext-dist/background.js +415 -415
  108. package/ext-dist/content.js +2527 -2527
  109. package/ext-dist/dashboard.html +583 -583
  110. package/ext-dist/hud/hud.js +3 -3
  111. package/ext-dist/hud/index.html +20 -20
  112. package/ext-dist/manifest.json +73 -73
  113. package/ext-dist/styles.css +223 -223
  114. package/mcp.json +796 -805
  115. package/package.json +118 -118
  116. package/server.json +23 -23
  117. package/dist/cdp/walker.test.d.ts +0 -2
  118. package/dist/cdp/walker.test.js +0 -172
  119. package/dist/intelligence/sessionMemory.test.d.ts +0 -2
  120. package/dist/intelligence/sessionMemory.test.js +0 -62
  121. package/dist/intelligence/trail.test.d.ts +0 -2
  122. package/dist/intelligence/trail.test.js +0 -110
  123. package/dist/state/cache.test.d.ts +0 -2
  124. package/dist/state/cache.test.js +0 -76
  125. package/dist/state/delta.test.d.ts +0 -2
  126. package/dist/state/delta.test.js +0 -279
  127. package/dist/state/groups.d.ts +0 -15
  128. package/dist/state/groups.js +0 -80
  129. package/dist/tools/accessibility.d.ts +0 -14
  130. package/dist/tools/accessibility.js +0 -32
  131. package/dist/tools/ask.d.ts +0 -14
  132. package/dist/tools/ask.js +0 -49
  133. package/dist/tools/click_and_wait.d.ts +0 -33
  134. package/dist/tools/click_and_wait.js +0 -149
  135. package/dist/tools/drag.d.ts +0 -15
  136. package/dist/tools/drag.js +0 -29
  137. package/dist/tools/geo.d.ts +0 -19
  138. package/dist/tools/geo.js +0 -29
  139. package/dist/tools/github/analyze.d.ts +0 -4
  140. package/dist/tools/github/analyze.js +0 -113
  141. package/dist/tools/github/cache.d.ts +0 -21
  142. package/dist/tools/github/cache.js +0 -28
  143. package/dist/tools/github/index.d.ts +0 -19
  144. package/dist/tools/github/index.js +0 -40
  145. package/dist/tools/github/issues.d.ts +0 -9
  146. package/dist/tools/github/issues.js +0 -88
  147. package/dist/tools/github/pr.d.ts +0 -5
  148. package/dist/tools/github/pr.js +0 -88
  149. package/dist/tools/github/rateLimiter.d.ts +0 -4
  150. package/dist/tools/github/rateLimiter.js +0 -46
  151. package/dist/tools/github/read.d.ts +0 -34
  152. package/dist/tools/github/read.js +0 -74
  153. package/dist/tools/github/repoContext.d.ts +0 -20
  154. package/dist/tools/github/repoContext.js +0 -129
  155. package/dist/tools/hover.d.ts +0 -19
  156. package/dist/tools/hover.js +0 -57
  157. package/dist/tools/integration.test.d.ts +0 -2
  158. package/dist/tools/integration.test.js +0 -96
  159. package/dist/tools/macro_compiler.d.ts +0 -7
  160. package/dist/tools/macro_compiler.js +0 -82
  161. package/dist/tools/mouse.d.ts +0 -21
  162. package/dist/tools/mouse.js +0 -62
  163. package/dist/tools/response.d.ts +0 -129
  164. package/dist/tools/response.js +0 -5
  165. package/dist/tools/wait_for.d.ts +0 -23
  166. package/dist/tools/wait_for.js +0 -30
  167. package/dist/tools/windows.d.ts +0 -22
  168. package/dist/tools/windows.js +0 -57
@@ -1,214 +1,225 @@
1
- ---
2
- title: "Desktop & Electron Apps"
3
- description: "Native Layer 0 automation for VS Code, Discord, Figma, Slack, and any Electron app."
4
- product: mcp
5
- section: desktop-automation
6
- badge: new
7
- icon: AppWindow
8
- slug: electron-apps
9
- ---
10
-
11
- # Desktop & Electron Application Automation
12
-
13
- 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.
14
-
15
- ## How It Works
16
-
17
- 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.
18
-
19
- ```text
20
- AI Agent (MCP) ──► withSecurity()
21
- ├── (Default) ─────────► CDP:9222 ──► Google Chrome / Chromium
22
- ├── (app: "discord") ──► CDP:9223 ──► Discord Desktop
23
- ├── (app: "figma") ──► CDP:9224 ──► Figma Desktop
24
- └── (app: "vscode") ──► CDP:9225 ──► VS Code Desktop
25
- ```
26
-
27
- ### Dual-Port Concurrency & Multi-Target Sessions
28
- - **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).
29
- - **Zero Session Clobbering**: Switching between a browser tab and a desktop app does not close, disconnect, or reload either target.
30
- - **Unified Tool Interface**: Pass `"app": "<appName>"` to any Weavetab tool to target that desktop application. Omit `app` to target the active web browser.
31
-
32
- ---
33
-
34
- ## Interactive App Configurator
35
-
36
- 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`.
37
-
38
- ---
39
-
40
- ## 1. Configuring Desktop Apps in `config.json`
41
-
42
- Add an `"electron"` object to your global `~/.weavetab/config.json` (the only config file Weavetab reads):
43
-
44
- ```json
45
- {
46
- "electron": {
47
- "discord": "C:\\Users\\username\\AppData\\Local\\Discord\\app-<version>\\Discord.exe",
48
- "vscode": 9222,
49
- "figma": {
50
- "path": "C:\\Users\\username\\AppData\\Local\\Figma\\Figma.exe",
51
- "port": 9224,
52
- "url": "https://www.figma.com",
53
- "args": ["--enable-features=WebRTCPipeWireCapturer"]
54
- },
55
- "slack": "/Applications/Slack.app/Contents/MacOS/Slack",
56
- "obsidian": "/usr/bin/obsidian"
57
- }
58
- }
59
- ```
60
-
61
- ### Configuration Formats Supported
62
-
63
- | Format | Example | Description |
64
- |---|---|---|
65
- | **Executable Path String** | `"discord": "C:\\path\\to\\Discord.exe"` | Automatically launches the binary on an isolated port and dedicated profile. |
66
- | **Port Number** | `"vscode": 9222` | Attaches directly to an already-running instance started with `--remote-debugging-port=9222`. |
67
- | **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. |
68
-
69
- ---
70
-
71
- ## 2. Security & Profile Isolation
72
-
73
- Weavetab enforces enterprise-grade sandbox separation for all desktop applications:
74
-
75
- 1. **Dedicated User Profiles**: Automated sessions are assigned isolated data profiles under `~/.weavetab-system/apps/<appName>/`.
76
- 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.
77
- 3. **Lock & Mutex Isolation**: Dedicated lockfiles (`~/.weavetab-system/locks/<appName>.lock`) ensure concurrent agent operations never conflict.
78
-
79
- ---
80
-
81
- ## 3. Supported Desktop Schemes & Protocols
82
-
83
- Weavetab automatically allows and whitelist-bypasses desktop internal protocols:
84
- - `app://` (Electron internal resources)
85
- - `vscode-webview://` / `vscode-file://` (VS Code extensions and webviews)
86
- - `discord://` / `slack://` (Deep-links)
87
- - `devtools://` / `chrome://` / `about:`
88
- - `file:///` (Local files)
89
-
90
- ---
91
-
92
- ## 4. How Agents Interact with Desktop Apps
93
-
94
- To target an Electron application, simply pass the `app` argument to any Weavetab tool:
95
-
96
- ### A. Inspect Desktop DOM Tree
97
- ```json
98
- {
99
- "name": "browser_map",
100
- "arguments": {
101
- "app": "discord",
102
- "scope": "main_content"
103
- }
104
- }
105
- ```
106
-
107
- ### B. Click & Type in Desktop Apps
108
- ```json
109
- {
110
- "name": "browser_click",
111
- "arguments": {
112
- "ref": "w:42",
113
- "app": "discord"
114
- }
115
- }
116
- ```
117
-
118
- ```json
119
- {
120
- "name": "browser_type",
121
- "arguments": {
122
- "ref": "w:45",
123
- "text": "Automated build passed successfully! 🚀",
124
- "app": "discord"
125
- }
126
- }
127
- ```
128
-
129
- ### C. Multi-Target Burst Orchestration
130
- ```json
131
- {
132
- "name": "browser_burst",
133
- "arguments": {
134
- "app": "vscode",
135
- "steps": [
136
- { "action": "click_and_wait", "selector": ".monaco-editor" },
137
- { "action": "type_and_send", "text": "npm test" }
138
- ]
139
- }
140
- }
141
- ```
142
-
143
- ---
144
-
145
- ## 5. Launching Existing Desktop Apps in Debug Mode
146
-
147
- If you prefer to attach Weavetab to your existing desktop app instance:
148
-
149
- ```bash
150
- # Launch VS Code with CDP debugging enabled
151
- code --remote-debugging-port=9222
152
-
153
- # Launch Obsidian with CDP debugging enabled
154
- obsidian --remote-debugging-port=9225
155
-
156
- # Launch Discord with CDP debugging enabled
157
- discord --remote-debugging-port=9223
158
- ```
159
- Then in your `config.json`, simply map `"vscode": 9222` or `"obsidian": 9225`.
160
-
161
- ---
162
-
163
- ## 6. Environment Discovery Handshake (`browser_detect`)
164
-
165
- `browser_detect` is the foundational tool agents invoke upon initial engagement. It inspects local browsers and configured desktop applications, returning their real-time state:
166
-
167
- ```json
168
- {
169
- "available": [
170
- { "engine": "chromium", "name": "Google Chrome", "path": "C:\\Program Files\\...\\chrome.exe" }
171
- ],
172
- "current": "chromium",
173
- "configuredApps": [
174
- {
175
- "name": "discord",
176
- "status": "running_no_debug",
177
- "configuredPath": "C:\\Users\\username\\AppData\\Local\\Discord\\app-1.0.9256\\Discord.exe"
178
- },
179
- {
180
- "name": "slack",
181
- "status": "connected",
182
- "port": 9222,
183
- "configuredPath": "C:\\Users\\username\\AppData\\Local\\slack\\app-4.38.125\\slack.exe",
184
- "activeTabs": [
185
- { "id": "PAGE_1", "title": "general - Slack", "url": "https://app.slack.com/client/..." }
186
- ]
187
- },
188
- {
189
- "name": "vscode",
190
- "status": "offline",
191
- "configuredPath": "C:\\Users\\username\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe"
192
- }
193
- ]
194
- }
195
- ```
196
-
197
- ### Application Lifecycle States:
198
- - **`connected`**: The app is running with CDP remote debugging active and Weavetab is attached. Agents can immediately operate tabs/windows using `"app": "<name>"`.
199
- - **`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.
200
- - **`offline`**: The process is not running. Calling `browser_navigate(app: "<name>")` launches and connects the app automatically.
201
-
202
- ### Windows Squirrel Auto-Path Resolution:
203
- 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.
204
-
205
- ---
206
-
207
- ## 7. Smart Domain Routing & Sticky Context
208
-
209
- To ensure external AI agents do not accidentally trigger a web browser launch when intending to control an Electron application:
210
-
211
- 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.
212
- 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.
213
- 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.
214
-
1
+ ---
2
+ title: "Desktop & Electron Apps"
3
+ description: "Native Layer 0 automation for VS Code, Discord, Figma, Slack, and any Electron app."
4
+ product: mcp
5
+ section: desktop-automation
6
+ badge: new
7
+ icon: AppWindow
8
+ slug: electron-apps
9
+ ---
10
+
11
+ # Desktop & Electron Application Automation
12
+
13
+ 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.
14
+
15
+ ## How It Works
16
+
17
+ 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.
18
+
19
+ ```text
20
+ AI Agent (MCP) ──► withSecurity()
21
+ ├── (Default) ─────────► CDP:9222 ──► Google Chrome / Chromium
22
+ ├── (app: "discord") ──► CDP:9223 ──► Discord Desktop
23
+ ├── (app: "figma") ──► CDP:9224 ──► Figma Desktop
24
+ └── (app: "vscode") ──► CDP:9225 ──► VS Code Desktop
25
+ ```
26
+
27
+ ### Dual-Port Concurrency & Multi-Target Sessions
28
+ - **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).
29
+ - **Zero Session Clobbering**: Switching between a browser tab and a desktop app does not close, disconnect, or reload either target.
30
+ - **Unified Tool Interface**: Pass `"app": "<appName>"` to any Weavetab tool to target that desktop application. Omit `app` to target the active web browser.
31
+
32
+ ---
33
+
34
+ ## Interactive App Configurator
35
+
36
+ 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`.
37
+
38
+ ---
39
+
40
+ ## 1. Configuring Desktop Apps in `config.json`
41
+
42
+ Add an `"electron"` object to your global `~/.weavetab/config.json` (the only config file Weavetab reads):
43
+
44
+ ```json
45
+ {
46
+ "electron": {
47
+ "discord": "C:\\Users\\username\\AppData\\Local\\Discord\\app-<version>\\Discord.exe",
48
+ "vscode": 9222,
49
+ "figma": {
50
+ "path": "C:\\Users\\username\\AppData\\Local\\Figma\\Figma.exe",
51
+ "port": 9224,
52
+ "url": "https://www.figma.com",
53
+ "args": ["--enable-features=WebRTCPipeWireCapturer"]
54
+ },
55
+ "slack": "/Applications/Slack.app/Contents/MacOS/Slack",
56
+ "obsidian": "/usr/bin/obsidian"
57
+ }
58
+ }
59
+ ```
60
+
61
+ ### Configuration Formats Supported
62
+
63
+ | Format | Example | Description |
64
+ |---|---|---|
65
+ | **Executable Path String** | `"discord": "C:\\path\\to\\Discord.exe"` | Automatically launches the binary on an isolated port and dedicated profile. |
66
+ | **Port Number** | `"vscode": 9222` | Attaches directly to an already-running instance started with `--remote-debugging-port=9222`. |
67
+ | **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. |
68
+
69
+ ---
70
+
71
+ ## 2. Security & Profile Isolation
72
+
73
+ Weavetab enforces enterprise-grade sandbox separation for all desktop applications:
74
+
75
+ 1. **Dedicated User Profiles**: Automated sessions are assigned isolated data profiles under `~/.weavetab-system/apps/<appName>/`.
76
+ 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.
77
+ 3. **Lock & Mutex Isolation**: Dedicated lockfiles (`~/.weavetab-system/locks/<appName>.lock`) ensure concurrent agent operations never conflict.
78
+
79
+ ---
80
+
81
+ ## 3. Supported Desktop Schemes & Protocols
82
+
83
+ Weavetab automatically allows and whitelist-bypasses desktop internal protocols:
84
+ - `app://` (Electron internal resources)
85
+ - `vscode-webview://` / `vscode-file://` (VS Code extensions and webviews)
86
+ - `discord://` / `slack://` (Deep-links)
87
+ - `devtools://` / `chrome://` / `about:`
88
+ - `file:///` (Local files)
89
+
90
+ ---
91
+
92
+ ## 4. How Agents Interact with Desktop Apps
93
+
94
+ To target an Electron application, simply pass the `app` argument to any Weavetab tool:
95
+
96
+ ### A. Inspect Desktop DOM Tree
97
+ ```json
98
+ {
99
+ "name": "browser_map",
100
+ "arguments": {
101
+ "app": "discord",
102
+ "scope": "main_content"
103
+ }
104
+ }
105
+ ```
106
+
107
+ ### B. Click & Type in Desktop Apps
108
+ ```json
109
+ {
110
+ "name": "browser_click",
111
+ "arguments": {
112
+ "ref": "w:42",
113
+ "app": "discord"
114
+ }
115
+ }
116
+ ```
117
+
118
+ ```json
119
+ {
120
+ "name": "browser_type",
121
+ "arguments": {
122
+ "ref": "w:45",
123
+ "text": "Automated build passed successfully! 🚀",
124
+ "app": "discord"
125
+ }
126
+ }
127
+ ```
128
+
129
+ ### C. Multi-Target Burst Orchestration
130
+ ```json
131
+ {
132
+ "name": "browser_burst",
133
+ "arguments": {
134
+ "app": "vscode",
135
+ "steps": [
136
+ { "tool": "click_and_wait", "selector": ".monaco-editor" },
137
+ { "tool": "type_and_send", "text": "npm test" }
138
+ ]
139
+ }
140
+ }
141
+ ```
142
+
143
+ ---
144
+
145
+ ## 5. Launching Existing Desktop Apps in Debug Mode
146
+
147
+ If you prefer to attach Weavetab to your existing desktop app instance:
148
+
149
+ ```bash
150
+ # Launch VS Code with CDP debugging enabled
151
+ code --remote-debugging-port=9222
152
+
153
+ # Launch Obsidian with CDP debugging enabled
154
+ obsidian --remote-debugging-port=9225
155
+
156
+ # Launch Discord with CDP debugging enabled
157
+ discord --remote-debugging-port=9223
158
+ ```
159
+ Then in your `config.json`, simply map `"vscode": 9222` or `"obsidian": 9225`.
160
+
161
+ ---
162
+
163
+ ## 6. Environment Discovery Handshake (`browser_detect`)
164
+
165
+ `browser_detect` is the foundational tool agents invoke upon initial engagement. It inspects local browsers and configured desktop applications, returning their real-time state:
166
+
167
+ ```json
168
+ {
169
+ "available": [
170
+ { "engine": "chromium", "name": "Google Chrome", "path": "C:\\Program Files\\...\\chrome.exe" }
171
+ ],
172
+ "current": "chromium",
173
+ "configuredApps": [
174
+ {
175
+ "name": "discord",
176
+ "status": "running_no_debug",
177
+ "configuredPath": "C:\\Users\\username\\AppData\\Local\\Discord\\app-1.0.9256\\Discord.exe"
178
+ },
179
+ {
180
+ "name": "slack",
181
+ "status": "connected",
182
+ "port": 9222,
183
+ "configuredPath": "C:\\Users\\username\\AppData\\Local\\slack\\app-4.38.125\\slack.exe",
184
+ "activeTabs": [
185
+ { "id": "PAGE_1", "title": "general - Slack", "url": "https://app.slack.com/client/..." }
186
+ ]
187
+ },
188
+ {
189
+ "name": "vscode",
190
+ "status": "offline",
191
+ "configuredPath": "C:\\Users\\username\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe"
192
+ }
193
+ ]
194
+ }
195
+ ```
196
+
197
+ ### Application Lifecycle States:
198
+ - **`connected`**: The app is running with CDP remote debugging active and Weavetab is attached. Agents can immediately operate tabs/windows using `"app": "<name>"`.
199
+ - **`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.
200
+ - **`offline`**: The process is not running. Calling `browser_navigate(app: "<name>")` launches and connects the app automatically.
201
+
202
+ ### Windows Squirrel Auto-Path Resolution:
203
+ 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.
204
+
205
+ ---
206
+
207
+ ## 7. Smart Domain Routing & Sticky Context
208
+
209
+ To ensure external AI agents do not accidentally trigger a web browser launch when intending to control an Electron application:
210
+
211
+ 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.
212
+ 2. **Sticky App Sessions**: When an agent operates inside an Electron app, the target session context remains sticky. Subsequent DOM calls stick to that active desktop app without spawning an unwanted Chrome window. The sticky Electron app is only used while **no web-browser session is active**; once a web-browser session is running, a plain `browser_tabs(action: "open")` (no `app`) targets the browser.
213
+ 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.
214
+
215
+ ---
216
+
217
+ ## 8. Opening Tabs Inside Electron Apps
218
+
219
+ Electron apps do **not** implement the CDP `Target.createTarget` command, so a brand-new tab or window cannot be created inside a desktop app from the outside. `browser_tabs(action: "open")` therefore:
220
+
221
+ - **Reuses** the existing tab/window when the requested URL is already loaded (focuses it) — the default `reuse: true` behavior.
222
+ - **Fails fast with an actionable error** when a genuinely new tab is required in an Electron app, e.g. `[!] Electron app "slack" does not support opening new tabs or windows via CDP ... Use browser_navigate with { app: "slack", url: "..." } ...` — instead of surfacing a raw `Not supported` CDP message.
223
+
224
+ To load a URL inside an Electron app, navigate its existing window with `browser_navigate({ app: "<name>", url: "..." })`.
225
+
@@ -21,7 +21,7 @@ npm install -D @weavetab/sdk@latest
21
21
 
22
22
  # Verify installation
23
23
  weavetab --version
24
- # → @weavetab/mcp 2.5.0
24
+ # → @weavetab/mcp 2.5.1
25
25
  ```
26
26
 
27
27
  ## System Requirements
@@ -1,60 +1,60 @@
1
- ---
2
- title: "Introduction"
3
- description: "What Weavetab is, Layer 0 CDP architecture, and design tenets."
4
- product: mcp
5
- section: get-started
6
- icon: BookOpen
7
- slug: introduction
8
- ---
9
-
10
- # Introduction
11
-
12
- Weavetab is a production-grade, local **Model Context Protocol (MCP) server** that grants AI agents human-like control over Chromium browsers and native **Electron desktop applications** (VS Code, Discord, Slack, Figma, Obsidian, Postman, Antigravity IDE, etc.) — communicating directly over the **Chrome DevTools Protocol (CDP)** at Layer 0.
13
-
14
- No WebDriver. No browser binary downloads. No Playwright or Puppeteer abstraction layer. No cloud dependency. Tool invocations resolve in **3–8 ms** of mean latency.
15
-
16
- ## Synchronized Ecosystem Releases
17
-
18
- Both **`@weavetab/mcp`** and the **`@weavetab/sdk`** share synchronized release lines. Every capability introduced in the core runtime is immediately available in the developer SDK with 100% type safety and zero version mismatch.
19
-
20
- ```bash
21
- # Install core Weavetab MCP server globally
22
- npm install -g @weavetab/mcp@latest
23
-
24
- # Or run directly via npx
25
- npx -y @weavetab/mcp@latest
26
-
27
- # Install Weavetab Developer SDK as a dev dependency
28
- npm install -D @weavetab/sdk@latest
29
- ```
30
-
31
- ## Design Tenets
32
-
33
- | Tenet | Implementation |
34
- |---|---|
35
- | **Ultra-Low Latency** | Sub-10 ms tool execution via direct CDP WebSocket connections |
36
- | **Universal Control** | Native orchestration across Chromium web tabs and any Electron desktop app |
37
- | **Autonomous CAPTCHA** | Zero-API solving (Cloudflare Turnstile, GeeTest, reCAPTCHA) via human Bézier mouse physics |
38
- | **Security & RBAC** | 4-tier RBAC + domain policies + Blind Credential Injection + profile isolation |
39
- | **Token Efficiency** | Semantic Delta diffing (up to 97% reduction) + intelligent DOM pruning |
40
- | **Stealth & Physics** | Ghost Cursor (Bézier curves), human typing jitter, and CDP early-script fingerprint spoofing |
41
- | **Self-Learning** | Per-domain session memory, framework detection, and automated loop recovery |
42
- | **Zero Cloud** | Pure local computation. No external telemetry or cloud tracking unless explicitly opted in |
43
-
44
- ## What You Get
45
-
46
- - **44 built-in MCP tools** covering DOM vision, input synthesis, desktop apps, tabs, network interception, office files, design extraction, and plugin lifecycle
47
- - **Universal Desktop App Runtime** — control Chrome and native Electron apps (Discord, Figma, VS Code) side-by-side without port conflicts
48
- - **Autonomous Zero-API CAPTCHA Solver** — solve Cloudflare Turnstile, GeeTest, and reCAPTCHA locally via CDP mouse physics with $0 API costs
49
- - **Two transport modes** — stdio (Claude Desktop, Cursor, VS Code, Windsurf, Antigravity) and WebSocket (`weavetab --ws --port 3000`)
50
- - **Five RBAC roles** — `admin`, `operator`, `viewer`, `automation`, and `system`
51
- - **Per-domain policies** — ring-fences sensitive banking, internal, and production surfaces
52
- - **Blind Injection** — credentials resolved server-side from `secrets.json` and never exposed to the LLM
53
- - **Extensible Plugin System** — auto-discovers and mounts custom MCP tools from `node_modules`
54
-
55
- ## Next Steps
56
-
57
- - **[Quickstart](quickstart.md)** — install and run a first mission in 60 seconds
58
- - **[Desktop & Electron Apps](../desktop-automation/electron-apps.md)** — configure and control desktop apps
59
- - **[Autonomous CAPTCHA Solver](../captcha-stealth/captcha-solver.md)** — zero-API anti-bot solving
60
- - **[MCP Tools Reference](../tools/tools.md)** — full reference for all 44 built-in automation tools
1
+ ---
2
+ title: "Introduction"
3
+ description: "What Weavetab is, Layer 0 CDP architecture, and design tenets."
4
+ product: mcp
5
+ section: get-started
6
+ icon: BookOpen
7
+ slug: introduction
8
+ ---
9
+
10
+ # Introduction
11
+
12
+ Weavetab is a production-grade, local **Model Context Protocol (MCP) server** that grants AI agents human-like control over Chromium browsers and native **Electron desktop applications** (VS Code, Discord, Slack, Figma, Obsidian, Postman, Antigravity IDE, etc.) — communicating directly over the **Chrome DevTools Protocol (CDP)** at Layer 0.
13
+
14
+ No WebDriver. No browser binary downloads. No Playwright or Puppeteer abstraction layer. No cloud dependency. Tool invocations resolve in **3–8 ms** of mean latency.
15
+
16
+ ## Synchronized Ecosystem Releases
17
+
18
+ Both **`@weavetab/mcp`** and the **`@weavetab/sdk`** share synchronized release lines. Every capability introduced in the core runtime is immediately available in the developer SDK with 100% type safety and zero version mismatch.
19
+
20
+ ```bash
21
+ # Install core Weavetab MCP server globally
22
+ npm install -g @weavetab/mcp@latest
23
+
24
+ # Or run directly via npx
25
+ npx -y @weavetab/mcp@latest
26
+
27
+ # Install Weavetab Developer SDK as a dev dependency
28
+ npm install -D @weavetab/sdk@latest
29
+ ```
30
+
31
+ ## Design Tenets
32
+
33
+ | Tenet | Implementation |
34
+ |---|---|
35
+ | **Ultra-Low Latency** | Sub-10 ms tool execution via direct CDP WebSocket connections |
36
+ | **Universal Control** | Native orchestration across Chromium web tabs and any Electron desktop app |
37
+ | **Autonomous CAPTCHA** | Zero-API solving (Cloudflare Turnstile, GeeTest, reCAPTCHA) via human Bézier mouse physics |
38
+ | **Security & RBAC** | 5-tier RBAC + domain policies + Blind Credential Injection + profile isolation |
39
+ | **Token Efficiency** | Semantic Delta diffing (up to 97% reduction) + intelligent DOM pruning |
40
+ | **Stealth & Physics** | Ghost Cursor (Bézier curves), human typing jitter, and CDP early-script fingerprint spoofing |
41
+ | **Self-Learning** | Per-domain session memory, framework detection, and automated loop recovery |
42
+ | **Zero Cloud** | Pure local computation. No external telemetry or cloud tracking unless explicitly opted in |
43
+
44
+ ## What You Get
45
+
46
+ - **41 built-in MCP tools** covering DOM vision, input synthesis, desktop apps, tabs, network interception, office files, design extraction, and plugin lifecycle
47
+ - **Universal Desktop App Runtime** — control Chrome and native Electron apps (Discord, Figma, VS Code) side-by-side without port conflicts
48
+ - **Autonomous Zero-API CAPTCHA Solver** — solve Cloudflare Turnstile, GeeTest, and reCAPTCHA locally via CDP mouse physics with $0 API costs
49
+ - **Two transport modes** — stdio (Claude Desktop, Cursor, VS Code, Windsurf, Antigravity) and WebSocket (`weavetab --ws --port 3000`)
50
+ - **Five RBAC roles** — `admin`, `operator`, `viewer`, `automation`, and `system`
51
+ - **Per-domain policies** — ring-fences sensitive banking, internal, and production surfaces
52
+ - **Blind Injection** — credentials resolved server-side from `secrets.json` and never exposed to the LLM
53
+ - **Extensible Plugin System** — auto-discovers and mounts custom MCP tools from `node_modules`
54
+
55
+ ## Next Steps
56
+
57
+ - **[Quickstart](quickstart.md)** — install and run a first mission in 60 seconds
58
+ - **[Desktop & Electron Apps](../desktop-automation/electron-apps.md)** — configure and control desktop apps
59
+ - **[Autonomous CAPTCHA Solver](../captcha-stealth/captcha-solver.md)** — zero-API anti-bot solving
60
+ - **[MCP Tools Reference](../tools/tools.md)** — full reference for all 41 built-in automation tools
@@ -44,8 +44,8 @@ Use `browser_burst` to chain multiple actions in a single round-trip:
44
44
  "name": "browser_burst",
45
45
  "arguments": {
46
46
  "steps": [
47
- { "action": "navigate_and_read", "url": "https://example.com" },
48
- { "action": "click_and_wait", "selector": "#login-btn" }
47
+ { "tool": "navigate_and_read", "url": "https://example.com" },
48
+ { "tool": "click_and_wait", "selector": "#login-btn" }
49
49
  ]
50
50
  }
51
51
  }
@@ -1,27 +1,27 @@
1
- ---
2
- title: "Setup Wizard"
3
- description: "Interactive wizard that writes a clean config.json."
4
- product: mcp
5
- section: get-started
6
- icon: Wand2
7
- slug: setup-wizard
8
- ---
9
-
10
- # Setup Wizard
11
-
12
- Run the interactive CLI configuration wizard:
13
-
14
- ```bash
15
- weavetab config
16
- ```
17
-
18
- The wizard walks through every option across 6 interactive phases. Re-run it at any time to update your saved config.
19
-
20
- ## Wizard Phases
21
-
22
- 1. **Phase 1 — Essentials:** Browser path, RBAC role (`admin`, `viewer`, `automation`), headless mode, dev mode, max tabs, actionability timeout, domain block/allow lists.
23
- 2. **Phase 2 — Advanced (optional):** Browser engine selection, timeouts and rate limits, telemetry opt-in, download/proxy directories, domain policy entries.
24
- 3. **Phase 3 — Save Location:** Global (`~/.weavetab/config.json`).
25
- 4. **Phase 4 — MCP Auto-Config:** Auto-detects installed IDEs (Claude Desktop, Cursor, Windsurf) and merges Weavetab into their MCP configuration.
26
- 5. **Phase 5 — Agent Skills:** Optionally installs `@weavetab/skills` for your agent framework.
27
- 6. **Phase 6 — Summary:** Displays full configuration validation report.
1
+ ---
2
+ title: "Setup Wizard"
3
+ description: "Interactive wizard that writes a clean config.json."
4
+ product: mcp
5
+ section: get-started
6
+ icon: Wand2
7
+ slug: setup-wizard
8
+ ---
9
+
10
+ # Setup Wizard
11
+
12
+ Run the interactive CLI configuration wizard:
13
+
14
+ ```bash
15
+ weavetab config
16
+ ```
17
+
18
+ The wizard walks through every option across 6 interactive phases. Re-run it at any time to update your saved config.
19
+
20
+ ## Wizard Phases
21
+
22
+ 1. **Phase 1 — Essentials:** Browser path, RBAC role (`admin`, `operator`, `viewer`, `automation`), headless mode, dev mode, max tabs, actionability timeout, domain block/allow lists.
23
+ 2. **Phase 2 — Advanced (optional):** Browser engine selection, timeouts and rate limits, telemetry opt-in, download/proxy directories, domain policy entries.
24
+ 3. **Phase 3 — Save Location:** Global (`~/.weavetab/config.json`).
25
+ 4. **Phase 4 — MCP Auto-Config:** Auto-detects installed IDEs (Claude Desktop, Cursor, Windsurf) and merges Weavetab into their MCP configuration.
26
+ 5. **Phase 5 — Agent Skills:** Optionally installs `@weavetab/skills` for your agent framework.
27
+ 6. **Phase 6 — Summary:** Displays full configuration validation report.