Skip to content

flutter-marionette: match Marionette MCP 0.6.0 - #19

Merged
wzslr321 merged 1 commit into
mainfrom
fix/marionette-upstream-0.6
Sep 23, 2026
Merged

wzslr321 merged 1 commit into
mainfrom
fix/marionette-upstream-0.6

Conversation

@wzslr321

Copy link
Copy Markdown
Member

Brings the plugin in line with Marionette MCP 0.6.0.

  • Log collection. Since 0.4.0, LoggingLogCollector and LoggerLogCollector live in the separate marionette_logging and marionette_logger packages. The README and references/marionette.md named them as if they shipped in marionette_flutter, so following the docs gave an undefined class. Both now say which package to add and how to pass the collector.
  • Tool list. references/marionette.md now covers the gesture, key, restart, device-config and custom-extension tools. It also gives the selectors for tap (prefer key, then identifier) and enter_text (input plus one of key, identifier or focused_element).
  • Build mode. Marionette works in debug and profile builds, not only debug.
  • Version check. connect fails when marionette_mcp and marionette_flutter versions differ; the README says how to align them.
  • Usage skill description. It names the runtime actions (tap, type, scroll, screenshots, smoke tests), so the skill loads when someone asks Claude to drive a running app.

Version 0.1.0 to 0.1.1, with a new CHANGELOG.md. Checked against leancodepl/marionette_mcp at e3fab3c: docs/logging.md, docs/mcp-tools.md and docs/troubleshooting.md.

🤖 Generated with Claude Code

LoggingLogCollector and LoggerLogCollector moved to the separate
marionette_logging and marionette_logger packages in 0.4.0. Update the
log collection docs, the tool list, the build-mode note (debug and
profile) and the version-mismatch note for connect. Name the runtime
actions in the usage skill description.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Hi @wzslr321! 👋 You're a LeanCode member, so a quick sanity check before this ships: is this PR meant for the public marketplace?

Everything merged here becomes publicly visible and is automatically synced into ai-plugins-internal.

  • Internal-only content (client-specific guidance, internal processes, backend/PMO plugins, anything not ready to be public) belongs in ai-plugins-internal instead.
  • Generally useful, public-ready content is right at home here — the internal repo will pick it up through the sync.

If public is what you intended, just ignore this comment. 🙂

@wzslr321
wzslr321 merged commit 8cf3a78 into main Sep 23, 2026
4 checks passed
@wzslr321
wzslr321 deleted the fix/marionette-upstream-0.6 branch September 23, 2026 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant