/ 目录 / 演练场 / Oh My OpenAgent
← 全部服务器 ↗ GitHub
● 社区 code-yeongyu ⚡ 即开即用

Oh My OpenAgent

作者 code-yeongyu · code-yeongyu/oh-my-openagent

Wire Claude, Codex, and Gemini into one workflow — Oh My OpenAgent routes tasks to the best model and presents one surface.

Skill + harness that orchestrates multiple coding agents. Routes by task type, blends outputs, and keeps a shared task log. Useful when you don't want to be loyal to one vendor.

▶ 观看演示 📦 安装 💡 使用场景

为什么要用

核心特性

实时演示

实际使用效果

就绪

安装

作者仓库 · Claude Skills 官方文档

使用场景

实战用法： Oh My OpenAgent

Ship a feature using the best of three models

👤 Claude Code users ⏱ ~15 min intermediate

何时使用： Claude is best at planning, Codex at refactors, Gemini at long-context — use them together.

步骤
  1. Plan
    Claude scopes.✓ 已复制
    → Plan ready
  2. Refactor
    Codex does the move.✓ 已复制
    → Code shipped
  3. Long context
    Gemini reviews full repo.✓ 已复制
    → Risks surfaced

结果： Each step uses the right tool.

组合

与其他 MCP 搭配，撬动十倍杠杆

oh-my-openagent-skill + gemini-cli-mcp

Plug Gemini CLI in as the long-context agent

Combine oh-my-openagent-skill with gemini-cli-mcp: Plug Gemini CLI in as the long-context agent✓ 已复制

工具

此 MCP 暴露的能力

工具输入参数何时调用成本
route (see docs) Dispatch a task to a specific agent 1 call

成本与限制

运行它的成本

API 配额
Per provider
每次调用 Token 数
High — multiple LLMs
费用
Free skill; provider costs
提示
Pick two of three for most flows; three is overkill

安全

权限、密钥、影响范围

最小权限： multi-provider keys
凭据存储： Keys per provider
数据出站： Configured providers

故障排查

常见错误与修复

Routing picks wrong agent

Override per-task; the heuristics are early

替代方案

Oh My OpenAgent 对比其他方案

替代方案何时用它替代权衡
Sticking with one agentSimplicityPer-task quality ceiling

更多

资源

📖 阅读 GitHub 上的官方 README

🐙 查看未解决的 issue

🔍 浏览全部 400+ MCP 服务器和 Skills