Skip to content

fix: add Oh-My-OpenCode MCPs to LAZY_MCPS for proper disabling#329

Merged
marcusquinn merged 1 commit intomainfrom
bugfix/disable-omo-mcps-correct-names
Feb 5, 2026
Merged

fix: add Oh-My-OpenCode MCPs to LAZY_MCPS for proper disabling#329
marcusquinn merged 1 commit intomainfrom
bugfix/disable-omo-mcps-correct-names

Conversation

@marcusquinn
Copy link
Owner

@marcusquinn marcusquinn commented Feb 5, 2026

Problem

Oh-My-OpenCode MCPs (grep_app, websearch) were still showing as 'Connected' after aidevops update.

Root Cause

The previous fix tried to disable MCPs after the loading policy ran, but the MCPs need to be in the LAZY_MCPS set for the policy to disable them.

Fix

Add Oh-My-OpenCode MCPs to LAZY_MCPS:

  • grep_app - GitHub code search (use @github-search subagent instead)
  • websearch - Exa web search
  • gh_grep - May exist from old configs

Also disable tool patterns globally:

  • grep_app_*
  • websearch_*
  • gh_grep_*

After Update

MCPs should show as 'Disabled' instead of 'Connected'.

Summary by CodeRabbit

  • Chores
    • Optimized tool management configuration by consolidating global disabling of specific tools through pattern-based rules, improving system organization and efficiency.

- Add grep_app, websearch, gh_grep to LAZY_MCPS set
- MCP loading policy now correctly disables these
- Also disable tool patterns globally (grep_app_*, websearch_*, gh_grep_*)
- Previous approach only worked if MCPs existed before policy ran
@marcusquinn marcusquinn merged commit c10752b into main Feb 5, 2026
6 of 8 checks passed
@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 addresses an issue where certain Oh-My-OpenCode MCPs were not being properly disabled, leading to incorrect status indications. The changes ensure that these specific MCPs and their related tools are correctly identified and disabled by the system's loading policy, streamlining the use of preferred subagents for GitHub code search and web search functionalities.

Highlights

  • Corrected MCP Disabling: Oh-My-OpenCode MCPs (grep_app, websearch, gh_grep) are now correctly added to the LAZY_MCPS set. This ensures that the loading policy properly disables these MCPs, preventing them from appearing as 'Connected' after an 'aidevops update'.
  • Global Tool Pattern Disabling: Associated tool patterns (grep_app_, websearch_, gh_grep_*) are now explicitly disabled globally. This change reinforces the use of alternative subagents like @github-search and @Context7 for these functionalities.
Changelog
  • .agent/scripts/generate-opencode-agents.sh
    • Added 'grep_app', 'websearch', and 'gh_grep' to the 'LAZY_MCPS' set to ensure these Oh-My-OpenCode MCPs are disabled by the loading policy.
    • Updated the comment regarding 'gh_grep' to clarify its status and potential existence from old configurations.
    • Refactored the tool disabling logic to explicitly disable 'grep_app_', 'websearch_', and 'gh_grep_*' tool patterns globally, promoting the use of alternative subagents.
Activity
  • No human activity has been recorded on this pull request yet.
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 Feb 5, 2026

Caution

Review failed

The pull request is closed.

Walkthrough

The PR expands the LAZY_MCPS list to include Oh-My-OpenCode MCPs (grep_app, websearch, gh_grep) and refactors the MCP disabling mechanism from per-MCP logic to a consolidated tool-pattern-based global disable block using pattern matching.

Changes

Cohort / File(s) Summary
MCP Loading Policy Refactor
.agent/scripts/generate-opencode-agents.sh
Expands LAZY_MCPS with three Oh-My-OpenCode MCPs and shifts tool disabling from individual MCP suppression to consolidated global tool-pattern matching (grep_app_, websearch_, gh_grep_*). Removes per-MCP disabling loop; adds centralized pattern-based disable block with logging.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

From eager to lazy, the MCPs now glide, 🚀
Tool patterns replace the per-MCP divide,
No loop, just one block—clean and refined,
Zero debt climbing, the DevOps way aligned! ⚡

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bugfix/disable-omo-mcps-correct-names

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

sonarqubecloud bot commented Feb 5, 2026

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 correctly moves the Oh-My-OpenCode MCPs (grep_app, websearch, gh_grep) to the LAZY_MCPS set to ensure they are properly disabled by the loading policy. The code is also refactored to remove the now-redundant manual MCP disabling logic, simplifying the script. My only suggestion is to make the log message more generic to accurately reflect the replacements for all disabled tools.

for tool_pattern in omo_tool_patterns:
if tool_pattern not in config.get('tools', {}):
config['tools'][tool_pattern] = False
print(f" Disabled {tool_pattern} tools globally (use @github-search subagent)")

Choose a reason for hiding this comment

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

medium

The log message suggests using the @github-search subagent as a replacement. While this is correct for grep_app_* and gh_grep_*, it's not accurate for websearch_*, which is for Exa web search. To avoid confusion, I recommend using a more generic message that applies to all disabled tool patterns.

Suggested change
print(f" Disabled {tool_pattern} tools globally (use @github-search subagent)")
print(f" Disabled {tool_pattern} tools globally (use aidevops subagents instead)")

@github-actions
Copy link

github-actions bot commented Feb 5, 2026

🔍 Code Quality Report

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

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

�[0;34m[INFO]�[0m Recent monitoring activity:
Thu Feb 5 02:44:06 UTC 2026: Code review monitoring started
Thu Feb 5 02:44:06 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 2
Thu Feb 5 02:44:06 UTC 2026: Qlty - 0 issues found, auto-formatting applied
Thu Feb 5 02:44:08 UTC 2026: Codacy analysis completed with auto-fixes

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 2
  • VULNERABILITIES: 0

Generated on: Thu Feb 5 02:45:43 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

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