@bdayadev/flutter-ultra-mcp 1.10.8 → 1.11.0

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "flutter",
       "description": "Durable cross-platform Flutter automation via 8 specialized MCP servers, in-app mixin binding, and an optional DevTools panel. Replaces marionette_mcp and the official dart mcp-server for Claude Code.",
-      "version": "1.10.8",
+      "version": "1.11.0",
       "author": {
         "name": "Bdaya-Dev",
         "url": "https://github.com/Bdaya-Dev"
@@ -23,5 +23,5 @@
       "tags": ["flutter", "dart", "mcp", "testing", "automation", "patrol", "cross-platform"]
     }
   ],
-  "version": "1.10.8"
+  "version": "1.11.0"
 }

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "flutter",
-  "version": "1.10.8",
+  "version": "1.11.0",
   "description": "Durable cross-platform Flutter automation via 8 specialized MCP servers, in-app mixin binding, and an optional DevTools panel. Replaces marionette_mcp and the official dart mcp-server for Claude Code.",
   "author": {
     "name": "Bdaya-Dev",

package/dart/ultra_flutter/pubspec.yaml

@@ -4,7 +4,7 @@ description: >-
   extensions (gesture, screenshot, inspector, screencast, log collection)
   for the flutter-ultra-mcp Claude Code plugin. Composable with Sentry and
   other WidgetsFlutterBinding subclasses via the mixin form.
-version: 1.10.8
+version: 1.11.0
 homepage: https://github.com/Bdaya-Dev/flutter-ultra-mcp
 repository: https://github.com/Bdaya-Dev/flutter-ultra-mcp
 issue_tracker: https://github.com/Bdaya-Dev/flutter-ultra-mcp/issues

package/dart/ultra_flutter_devtools/pubspec.yaml

@@ -2,7 +2,7 @@ name: ultra_flutter_devtools
 description: >-
   Flutter DevTools extension showing live MCP activity for the flutter-ultra-mcp
   Claude Code plugin (sessions, recent tool calls, errors, screenshot grid).
-version: 1.10.8
+version: 1.11.0
 homepage: https://github.com/Bdaya-Dev/flutter-ultra-mcp
 repository: https://github.com/Bdaya-Dev/flutter-ultra-mcp
 issue_tracker: https://github.com/Bdaya-Dev/flutter-ultra-mcp/issues

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bdayadev/flutter-ultra-mcp",
-  "version": "1.10.8",
+  "version": "1.11.0",
   "description": "Flutter Ultra MCP plugin monorepo — 8 MCP servers + ultra_flutter Dart packages + skills for Claude Code.",
   "license": "Apache-2.0",
   "homepage": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",

package/skills/drive/SKILL.md

@@ -99,6 +99,72 @@ When a flow involves an external OAuth consent screen:
 
 Produce a numbered summary: steps taken, pass/fail status per step, screenshot paths, and any errors from `mcp__plugin_flutter_flutter-ultra-runtime__get_runtime_errors`.
 
+## Web launch modes
+
+When launching a Flutter web app, choose the mode based on what the flow needs:
+
+| Mode | Command | VM Service | Hot Reload | Startup | Best for |
+|------|---------|-----------|-----------|---------|----------|
+| `chrome` (default) | `-d chrome --headless=new` | Yes (DWDS) | Yes | 60-90s | Debugging, widget inspection, evaluate, state reading |
+| `chrome-headed` | `-d chrome` (visible) | Yes (DWDS) | Yes | 60-90s | Local development, watching the agent work |
+| `web-server` | `-d web-server` | No | No | 5-10s | Visual tours, screenshots, parallel subagent runs |
+
+### When to use each mode
+
+**Use `chrome` (default)** when the flow needs:
+- Widget tree inspection (`get_widget_tree`, `find_widget`)
+- Expression evaluation (`evaluate`)
+- Hot reload after code changes
+- Runtime error inspection (`get_runtime_errors`)
+- Gesture tools via VM Service (`tap`, `enter_text`, `scroll_to`)
+
+**Use `chrome-headed`** when:
+- You want to visually watch the agent drive the app
+- Debugging a flow that doesn't work headless (rare)
+
+**Use `web-server`** when:
+- The flow only needs screenshots and Playwright navigation
+- Running multiple parallel app instances for subagent tours
+- Fast iteration without waiting for DWDS connection
+- Cross-browser testing (Firefox, WebKit via Playwright)
+
+### Launching in each mode
+
+```
+# Default (chrome headless + DWDS):
+launch_app(projectDir, target, device: "chrome")
+
+# Chrome headed (visible + DWDS):
+launch_app(projectDir, target, device: "chrome", webLaunchMode: "chrome-headed")
+
+# Web-server (fast, no DWDS):
+launch_app(projectDir, target, device: "chrome", webLaunchMode: "web-server", webPort: 8080)
+```
+
+For web-server mode, after `poll_launch_app` shows `attached`, use browser server tools:
+- `mcp__plugin_flutter_flutter-ultra-browser__launch_browser` → navigate to `webServerUrl`
+- `mcp__plugin_flutter_flutter-ultra-browser__screenshot` for captures
+- `mcp__plugin_flutter_flutter-ultra-browser__click` / `fill` for interaction
+
+### Parallel instances for subagent tours
+
+Multiple app instances can run simultaneously on different ports. This enables parallel visual documentation where each subagent drives a different section of the app:
+
+```
+# Agent A: tour the auth flows
+launch_app(projectDir, target, device: "chrome", webLaunchMode: "web-server", webPort: 8081)
+
+# Agent B: tour the dashboard (simultaneous)
+launch_app(projectDir, target, device: "chrome", webLaunchMode: "web-server", webPort: 8082)
+
+# Agent C: tour settings (simultaneous)
+launch_app(projectDir, target, device: "chrome", webLaunchMode: "web-server", webPort: 8083)
+```
+
+Each agent launches its own Playwright browser, navigates to its port, and captures screenshots independently. No shared state, no conflicts.
+
+**Limitation**: `chrome` mode (with DWDS) does NOT support parallel instances to the same project — Flutter's machine-mode daemon locks the compile. Use `web-server` for parallelism.
+
 ## Handling edge cases
 
 - **Element not found**: call `mcp__plugin_flutter_flutter-ultra-runtime__get_widget_tree` to find where the element is. Wait up to 3s via `mcp__plugin_flutter_flutter-ultra-gesture__wait_for`.

package/skills/setup/SKILL.md

@@ -156,6 +156,34 @@ User: "Set up flutter-ultra on my app."
 -> "Setup complete. 2 files changed. Smoke screenshot saved."
 ```
 
+## Known issues
+
+### Sentry zone mismatch warning on web
+
+When using the composed binding pattern with Sentry (`SentryWidgetsBindingMixin` + `UltraFlutterBinding`), Flutter may emit a "Zone mismatch" assertion warning on web. This happens because Sentry wraps `appRunner` in `runZonedGuarded`, and the binding is created in a different zone than where `runApp` executes.
+
+**This warning is non-fatal** — the app works correctly. To minimize it, create the binding inside Sentry's zone guard:
+
+```dart
+Future<void> main() async {
+  await SentryFlutter.init(
+    (options) { options.dsn = '...'; },
+    appRunner: () {
+      if (kDebugMode) {
+        AppBinding();
+      } else {
+        WidgetsFlutterBinding.ensureInitialized();
+      }
+      runApp(const MyApp());
+    },
+  );
+}
+```
+
+### Inspector extensions unavailable on web (DWDS)
+
+`ext.flutter.inspector.screenshot` and `ext.flutter.inspector.getRootWidgetSummaryTree` fail on web targets with `(-32000) Server error`. This is a known Flutter DWDS limitation ([flutter/flutter#97898](https://github.com/flutter/flutter/issues/97898)). The runtime server automatically falls back to `ext.flutter.ultra.*` extensions when the inspector fails, and then to CDP `Page.captureScreenshot` for screenshots on web.
+
 ## See also
 
 - `flutter-tour` — visual screenshot tour after setup

package/skills/tour/SKILL.md

@@ -15,6 +15,18 @@ description: Captures route-by-route screenshots of a running Flutter app for vi
 - `mcp__plugin_flutter_flutter-ultra-runtime__attach` with the returned URI.
 - For web targets, also `mcp__plugin_flutter_flutter-ultra-browser__launch_browser` or `mcp__plugin_flutter_flutter-ultra-browser__connect_over_cdp` to get a browser context.
 
+**Web launch mode for tours**: Use `webLaunchMode: "web-server"` for fast startup and parallel instance support. Tours are screenshot-only and don't need VM Service tools. See `flutter-drive` skill for the full launch mode reference.
+
+**Parallel subagent tours**: Launch multiple instances on different ports (`webPort: 8081`, `8082`, etc.) and assign route subsets to each subagent for faster coverage:
+
+```
+# Subagent 1: auth routes (port 8081)
+launch_app(..., webLaunchMode: "web-server", webPort: 8081)
+
+# Subagent 2: dashboard routes (port 8082)
+launch_app(..., webLaunchMode: "web-server", webPort: 8082)
+```
+
 ### 2. Discover routes
 
 Call `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` to extract the route table: