docs(playwriter): fix OpenCode MCP configuration#153
Conversation
- Add -y flag to auto-confirm package installation - Use full path to npx for reliability - Add per-agent tool enabling example - Document token optimization strategy
Summary of ChangesHello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refines the documentation for Playwriter's integration with OpenCode, focusing on improving configuration accuracy and user guidance. The changes aim to ensure more reliable tool execution and provide strategies for efficient resource management, particularly concerning context token usage in agent-based setups. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
WalkthroughUpdates Playwriter browser tool documentation to use absolute npx paths with Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
There was a problem hiding this comment.
Code Review
This pull request improves the documentation for Playwriter by updating configuration examples and adding guidance on per-agent tool enabling. The changes are clear and helpful. I've provided a few suggestions to enhance the documentation's clarity and consistency, mainly by specifying language identifiers for code blocks to enable syntax highlighting and by addressing a potential point of confusion regarding the use of full paths in command configurations.
| } | ||
| } | ||
| ```text | ||
| ``` |
| "command": "npx", | ||
| "args": ["playwriter@latest"] | ||
| "args": ["-y", "playwriter@latest"] |
There was a problem hiding this comment.
There's an inconsistency in the documentation. The note for the OpenCode configuration recommends using the full path to npx for reliability, but this claude_desktop example uses just npx. This could be confusing for users. For consistency and to ensure reliability, please consider either updating this example to also use a full path for npx or adding a clarification on why it's not necessary in this case.
| } | ||
| } | ||
| ```text | ||
| ``` |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Thu Jan 22 14:56:01 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
🤖 Augment PR SummarySummary: Updates Playwriter MCP docs to correct the OpenCode configuration format and make installs non-interactive via 🤖 Was this summary useful? React with 👍 or 👎 |
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.agent/tools/browser/playwriter.md (1)
71-82: Align Claude Desktop example with full-path guidance.The reliability note recommends a full
npxpath, but the Claude Desktop example still uses"command": "npx". This can fail in hardened PATH environments. Consider either switching to a full path in the Claude example or adding a note clarifying that Claude Desktop must havenpxin PATH.🔧 Suggested doc tweak
-**Claude Desktop** (`claude_desktop_config.json`): +**Claude Desktop** (`claude_desktop_config.json`): +> **Note**: If Claude Desktop runs with a restricted PATH, use the full `npx` path (e.g., `/opt/homebrew/bin/npx`).
| "playwriter": { | ||
| "type": "local", | ||
| "command": ["npx", "playwriter@latest"], | ||
| "command": ["/opt/homebrew/bin/npx", "-y", "playwriter@latest"], |
There was a problem hiding this comment.
This hard-codes the Homebrew Apple Silicon npx path, which will differ for Intel Homebrew (and for nvm/asdf installs), so copy/paste may fail for many readers. Consider clarifying that the npx path is environment-specific and should be verified locally before use.
🤖 Was this useful? React with 👍 or 👎
| ```text | ||
| ``` | ||
|
|
||
| > **Note**: Use full path to `npx` (e.g., `/opt/homebrew/bin/npx` on macOS with Homebrew) for reliability. The `-y` flag auto-confirms package installation. |
There was a problem hiding this comment.
This note calls out full-path npx for OpenCode, but Claude Desktop (GUI-launched) often doesn’t inherit the user’s shell PATH, so command: "npx" can also fail. It may be worth mentioning that Claude Desktop users might need a full npx path for the same reliability reason.
🤖 Was this useful? React with 👍 or 👎
Combined commits: - 🤖 AUTO-FIX: Apply code quality improvements - docs(playwriter): update OpenCode config with correct npx format (#153)
* docs(playwriter): update OpenCode config with correct npx format - Add -y flag to auto-confirm package installation - Use full path to npx for reliability - Add per-agent tool enabling example - Document token optimization strategy * Squash commits from fix/playwriter-mcp-opencode-config Combined commits: - 🤖 AUTO-FIX: Apply code quality improvements - docs(playwriter): update OpenCode config with correct npx format (#153) * feat: add aidevops skill CLI command with telemetry disabled Adds cmd_skill() to aidevops.sh providing a unified interface for managing Agent Skills (agentskills.io) with telemetry disabled by default. Delegates to existing add-skill-helper.sh and skill-update-helper.sh for implementation. - Exports DISABLE_TELEMETRY, DO_NOT_TRACK, SKILLS_NO_TELEMETRY env vars - Supports add/list/remove/check/update/status subcommands - Updates help text with skill command and examples section - Updates README with new CLI syntax and reference links * feat: add -skill suffix for imports, generate/clean subcommands, AGENTS.md docs - Imported skills now saved as *-skill.md to distinguish from native subagents - Conflict detection differentiates NATIVE vs IMPORTED conflicts - Removed merge option (was unimplemented), simplified to replace/separate/skip - Added generate/clean subcommands delegating to generate-skills.sh - Updated AGENTS.md with Imported Skills section, CLI table, key scripts - Updated commands/add-skill.md with naming convention docs and examples * fix: address PR review feedback (changelog, error handling, timeout) - Add CHANGELOG entry for skill command under [Unreleased] - Separate unknown subcommand from help (exit 1 with error message) - Add curl --connect-timeout 10 --max-time 30 to GitHub API call



Summary
-yflag to npx command for auto-confirmationChanges
Documentation (
playwriter.md)["npx", "playwriter@latest"]→["/opt/homebrew/bin/npx", "-y", "playwriter@latest"]-yflagTesting
The user's OpenCode config was also updated (outside this repo) to:
playwriter_*tools for Build+ and Research agentsRelated
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.