Skip to content

docs(playwriter): fix OpenCode MCP configuration#153

Merged
marcusquinn merged 1 commit intomainfrom
fix/playwriter-mcp-opencode-config
Jan 22, 2026
Merged

docs(playwriter): fix OpenCode MCP configuration#153
marcusquinn merged 1 commit intomainfrom
fix/playwriter-mcp-opencode-config

Conversation

@marcusquinn
Copy link
Owner

@marcusquinn marcusquinn commented Jan 22, 2026

Summary

  • Update Playwriter MCP documentation with correct OpenCode configuration format
  • Add -y flag to npx command for auto-confirmation
  • Document full path usage for reliability
  • Add per-agent tool enabling example for token optimization

Changes

Documentation (playwriter.md)

  • Fixed OpenCode config example: ["npx", "playwriter@latest"]["/opt/homebrew/bin/npx", "-y", "playwriter@latest"]
  • Added note about using full path to npx
  • Added Claude Desktop config with -y flag
  • Added per-agent tool enabling example with explanation

Testing

The user's OpenCode config was also updated (outside this repo) to:

  1. Use correct npx command format
  2. Enable playwriter_* tools for Build+ and Research agents

Related

Summary by CodeRabbit

  • Documentation
    • Updated Playwriter tool configuration guidance with clearer setup instructions
    • Added user-facing notes clarifying proper command usage and automatic confirmation behavior
    • Enhanced configuration examples for OpenCode and Claude Desktop environments

✏️ Tip: You can customize this high-level summary in your review settings.

- 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
@gemini-code-assist
Copy link

Summary of Changes

Hello @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

  • OpenCode Configuration Update: The OpenCode MCP configuration for Playwriter has been updated to use the correct format, including the full path for npx and the -y flag for auto-confirmation.
  • npx Command Enhancements: The npx command now includes the -y flag to automatically confirm package installations, improving the user experience.
  • Full Path Documentation: Documentation now explicitly recommends using the full path to npx for enhanced reliability across different environments.
  • Per-Agent Tool Enabling: An example has been added to demonstrate how to enable Playwriter tools on a per-agent basis, which helps optimize context token usage.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 22, 2026

Walkthrough

Updates Playwriter browser tool documentation to use absolute npx paths with -y auto-confirmation flag. Adds per-agent tool enablement guidance and user-facing clarifications for configuration across OpenCode and Claude Desktop MCP settings.

Changes

Cohort / File(s) Change Summary
Playwriter Configuration Documentation
.agent/tools/browser/playwriter.md
Replaces local npx invocations with absolute paths and introduces -y flag for automatic installation confirmation. Adds per-agent tool enablement guidance for OpenCode config and Claude Desktop MCP server setup. Includes user-facing notes clarifying full path usage and -y auto-confirm behavior.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🎭 Paths made absolute, flags dance with -y,
Configuration wisdom reaches the sky,
Per-agent clarity, debt-free and bright,
Playwriter documentation shines with delight! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating Playwriter MCP documentation to fix OpenCode configuration format, which aligns with the core objective of replacing npx invocation patterns and adding configuration guidance.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud
Copy link

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To enable syntax highlighting for this JSON example and improve readability, please specify the language in the markdown code block. Using json is appropriate here.

Suggested change
```
```json

Comment on lines 77 to +78
"command": "npx",
"args": ["playwriter@latest"]
"args": ["-y", "playwriter@latest"]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Similar to the other configuration block, specifying the language as json here will enable syntax highlighting, making the example easier to read and understand.

Suggested change
```
```json

@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 353 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Thu Jan 22 14:54:43 UTC 2026: Code review monitoring started
Thu Jan 22 14:54:44 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 353
Thu Jan 22 14:54:44 UTC 2026: Qlty - 0 issues found, auto-formatting applied
Thu Jan 22 14:54:46 UTC 2026: Codacy analysis completed with auto-fixes

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 353
  • VULNERABILITIES: 0

Generated on: Thu Jan 22 14:56:01 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@augmentcode
Copy link

augmentcode bot commented Jan 22, 2026

🤖 Augment PR Summary

Summary: Updates Playwriter MCP docs to correct the OpenCode configuration format and make installs non-interactive via npx -y.
Changes: Adjusts OpenCode/Claude Desktop examples and adds a per-agent tool enable/disable snippet to help reduce unnecessary tool context loading.

🤖 Was this summary useful? React with 👍 or 👎

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 npx path, 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 have npx in 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`).

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. 2 suggestions posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

"playwriter": {
"type": "local",
"command": ["npx", "playwriter@latest"],
"command": ["/opt/homebrew/bin/npx", "-y", "playwriter@latest"],
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix This in Augment

🤖 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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

@marcusquinn marcusquinn merged commit 62d61d9 into main Jan 22, 2026
17 checks passed
marcusquinn added a commit that referenced this pull request Jan 22, 2026
Combined commits:
- 🤖 AUTO-FIX: Apply code quality improvements
- docs(playwriter): update OpenCode config with correct npx format (#153)
marcusquinn added a commit that referenced this pull request Jan 23, 2026
* 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
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