claudecode-omc 4.4.5 → 4.4.7

package/.mcp.json

@@ -4,13 +4,9 @@
       "command": "node",
       "args": ["${CLAUDE_PLUGIN_ROOT}/bridge/mcp-server.cjs"]
     },
-    "x": {
+    "team": {
       "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/bridge/codex-server.cjs"]
-    },
-    "g": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/bridge/gemini-server.cjs"]
+      "args": ["${CLAUDE_PLUGIN_ROOT}/bridge/team-mcp.cjs"]
     }
   }
 }

package/README.es.md

@@ -36,6 +36,55 @@ autopilot: build a REST API for managing tasks
 
 Eso es todo. Todo lo demás es automático.
 
+## Modo Team (Recomendado)
+
+A partir de **v4.1.7**, **Team** es la superficie canónica de orquestación en OMC. Los puntos de entrada legados como **swarm** y **ultrapilot** siguen siendo compatibles, pero ahora **enrutan a Team internamente**.
+
+```bash
+/team 3:executor "fix all TypeScript errors"
+```
+
+Team se ejecuta como un pipeline por etapas:
+
+`team-plan → team-prd → team-exec → team-verify → team-fix (loop)`
+
+Habilita los equipos nativos de Claude Code en `~/.claude/settings.json`:
+
+```json
+{
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+  }
+}
+```
+
+> Si los equipos están desactivados, OMC te avisará y hará fallback a ejecución sin Team cuando sea posible.
+
+### Trabajadores CLI tmux — Codex & Gemini (v4.4.0+)
+
+**v4.4.0 elimina los servidores MCP de Codex/Gemini** (proveedores `x`, `g`). Usa `/omc-teams` para lanzar procesos CLI reales en paneles divididos de tmux:
+
+```bash
+/omc-teams 2:codex   "review auth module for security issues"
+/omc-teams 2:gemini  "redesign UI components for accessibility"
+/omc-teams 1:claude  "implement the payment flow"
+```
+
+Para trabajo mixto de Codex + Gemini en un solo comando, usa la habilidad **`/ccg`**:
+
+```bash
+/ccg Review this PR — architecture (Codex) and UI components (Gemini)
+```
+
+| Habilidad | Trabajadores | Mejor Para |
+|-------|---------|----------|
+| `/omc-teams N:codex` | N paneles Codex CLI | Revisión de código, análisis de seguridad, arquitectura |
+| `/omc-teams N:gemini` | N paneles Gemini CLI | Diseño UI/UX, docs, tareas de gran contexto |
+| `/omc-teams N:claude` | N paneles Claude CLI | Tareas generales via Claude CLI en tmux |
+| `/ccg` | 1 Codex + 1 Gemini | Orquestación tri-modelo en paralelo |
+
+Los trabajadores se inician bajo demanda y terminan cuando su tarea se completa — sin uso de recursos en espera. Requiere las CLIs `codex` / `gemini` instaladas y una sesión tmux activa.
+
 > **Nota: Nombre del paquete** — El proyecto usa la marca **oh-my-claudecode** (repositorio, plugin, comandos), pero el paquete npm se publica como [`oh-my-claudecode`](https://www.npmjs.com/package/oh-my-claude-sisyphus). Si instalas las herramientas CLI via npm/bun, usa `npm install -g oh-my-claude-sisyphus`.
 
 ### Actualizar
@@ -81,14 +130,16 @@ Si experimentas problemas despues de actualizar, limpia la cache antigua del plu
 ### Modos de Ejecución
 Múltiples estrategias para diferentes casos de uso - desde construcciones completamente autónomas hasta refactorización eficiente en tokens. [Aprende más →](https://yeachan-heo.github.io/oh-my-claudecode-website/docs.html#execution-modes)
 
-| Modo | Velocidad | Usar Para |
-|------|-------|---------|
-| **Autopilot** | Rápido | Flujos de trabajo completamente autónomos |
-| **Ultrawork** | Paralelo | Máximo paralelismo para cualquier tarea |
-| **Ralph** | Persistente | Tareas que deben completarse totalmente |
-| **Ultrapilot** | 3-5x más rápido | Sistemas multi-componente |
-| **Swarm** | Coordinado | Tareas independientes en paralelo |
-| **Pipeline** | Secuencial | Procesamiento multi-etapa |
+| Modo | Característica | Usar Para |
+|------|---------|---------|
+| **Team (recomendado)** | Pipeline por etapas | Agentes Claude coordinados en una lista de tareas compartida |
+| **omc-teams** | Trabajadores CLI tmux | Tareas Codex/Gemini CLI; se inician bajo demanda, terminan al completar |
+| **ccg** | Tri-modelo en paralelo | Codex (analítico) + Gemini (diseño), Claude sintetiza |
+| **Autopilot** | Ejecución autónoma | Trabajo de feature end-to-end con mínima ceremonia |
+| **Ultrawork** | Máximo paralelismo | Correcciones/refactorizaciones en ráfaga cuando Team no es necesario |
+| **Ralph** | Modo persistente | Tareas que deben completarse totalmente |
+| **Pipeline** | Procesamiento secuencial | Transformaciones multi-etapa con ordenación estricta |
+| **Swarm / Ultrapilot (legado)** | Enrutan a Team | Flujos de trabajo existentes y documentación antigua |
 
 ### Orquestación Inteligente
 
@@ -113,11 +164,16 @@ Atajos opcionales para usuarios avanzados. El lenguaje natural funciona bien sin
 
 | Palabra Clave | Efecto | Ejemplo |
 |---------|--------|---------|
+| `team` | Orquestación canónica con Team | `/team 3:executor "fix all TypeScript errors"` |
+| `omc-teams` | Trabajadores CLI tmux (codex/gemini/claude) | `/omc-teams 2:codex "security review"` |
+| `ccg` | Orquestación tri-modelo Codex+Gemini | `/ccg review this PR` |
 | `autopilot` | Ejecución completamente autónoma | `autopilot: build a todo app` |
 | `ralph` | Modo persistencia | `ralph: refactor auth` |
 | `ulw` | Máximo paralelismo | `ulw fix all errors` |
 | `plan` | Entrevista de planificación | `plan the API` |
 | `ralplan` | Consenso de planificación iterativa | `ralplan this feature` |
+| `swarm` | Palabra clave legada (enruta a Team) | `swarm 5 agents: fix lint errors` |
+| `ultrapilot` | Palabra clave legada (enruta a Team) | `ultrapilot: build a fullstack app` |
 
 **ralph incluye ultrawork:** Cuando activas el modo ralph, automáticamente incluye la ejecución paralela de ultrawork. No es necesario combinar palabras clave.
 

package/README.ja.md

@@ -36,6 +36,55 @@ autopilot: build a REST API for managing tasks
 
 以上です。あとは自動で進みます。
 
+## Team モード（推奨）
+
+**v4.1.7** から **Team** が OMC の標準オーケストレーション方式です。**swarm** や **ultrapilot** などのレガシーエントリポイントは引き続きサポートされていますが、**内部的に Team にルーティング**されます。
+
+```bash
+/team 3:executor "fix all TypeScript errors"
+```
+
+Team はステージ型パイプラインで実行されます:
+
+`team-plan → team-prd → team-exec → team-verify → team-fix (loop)`
+
+`~/.claude/settings.json` で Claude Code ネイティブチームを有効化:
+
+```json
+{
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+  }
+}
+```
+
+> チームが無効の場合、OMC は警告を表示し、可能な場合は Team なしの実行にフォールバックします。
+
+### tmux CLI ワーカー — Codex & Gemini (v4.4.0+)
+
+**v4.4.0 で Codex/Gemini MCP サーバー**（`x`、`g` プロバイダー）が**削除されます**。代わりに `/omc-teams` を使って tmux 分割ペインで実際の CLI プロセスを起動してください:
+
+```bash
+/omc-teams 2:codex   "review auth module for security issues"
+/omc-teams 2:gemini  "redesign UI components for accessibility"
+/omc-teams 1:claude  "implement the payment flow"
+```
+
+Codex + Gemini を一つのコマンドで使うには **`/ccg`** スキルを使います:
+
+```bash
+/ccg Review this PR — architecture (Codex) and UI components (Gemini)
+```
+
+| スキル | ワーカー | 最適用途 |
+|-------|---------|----------|
+| `/omc-teams N:codex` | N 個の Codex CLI ペイン | コードレビュー、セキュリティ解析、アーキテクチャ |
+| `/omc-teams N:gemini` | N 個の Gemini CLI ペイン | UI/UX デザイン、ドキュメント、大規模コンテキスト |
+| `/omc-teams N:claude` | N 個の Claude CLI ペイン | tmux で Claude CLI を使う汎用タスク |
+| `/ccg` | Codex 1 個 + Gemini 1 個 | 並列トライモデルオーケストレーション |
+
+ワーカーはオンデマンドで起動し、タスク完了後に終了します — アイドルリソースの無駄なし。`codex` / `gemini` CLI のインストールとアクティブな tmux セッションが必要です。
+
 > **注意: パッケージ名について** — プロジェクトのブランド名は **oh-my-claudecode**（リポジトリ、プラグイン、コマンド）ですが、npmパッケージは [`oh-my-claudecode`](https://www.npmjs.com/package/oh-my-claude-sisyphus) として公開されています。npm/bunでCLIツールをインストールする場合は `npm install -g oh-my-claude-sisyphus` を使用してください。
 
 ### アップデート
@@ -81,14 +130,16 @@ autopilot: build a REST API for managing tasks
 ### 実行モード
 用途に応じた複数の戦略 - 完全自律ビルドからトークン効率の良いリファクタリングまで。[詳しくはこちら →](https://yeachan-heo.github.io/oh-my-claudecode-website/docs.html#execution-modes)
 
-| モード | スピード | 用途 |
-|------|-------|------|
-| **Autopilot** | 高速 | 完全自律ワークフロー |
-| **Ultrawork** | 並列 | あらゆるタスクの最大並列化 |
-| **Ralph** | 粘り強い | 必ず完遂すべきタスク |
-| **Ultrapilot** | 3〜5倍速 | 複数コンポーネントシステム |
-| **Swarm** | 協調 | 並列独立タスク |
-| **Pipeline** | 逐次 | 多段階処理 |
+| モード | 特徴 | 用途 |
+|------|---------|------|
+| **Team（推奨）** | ステージ型パイプライン | 共有タスクリストで協力する Claude エージェント |
+| **omc-teams** | tmux CLI ワーカー | Codex/Gemini CLI タスク; オンデマンド起動、完了後終了 |
+| **ccg** | トライモデル並列 | Codex（分析）+ Gemini（デザイン）、Claude が統合 |
+| **Autopilot** | 自律実行 | 最小限のセレモニーで end-to-end 機能開発 |
+| **Ultrawork** | 最大並列 | Team 不要な並列修正/リファクタリング |
+| **Ralph** | 粘り強いモード | 完全に完了させるべきタスク |
+| **Pipeline** | 逐次処理 | 厳密な順序が必要な多段階変換 |
+| **Swarm / Ultrapilot（レガシー）** | Team へルーティング | 既存ワークフローと古いドキュメント |
 
 ### インテリジェント・オーケストレーション
 
@@ -113,11 +164,16 @@ autopilot: build a REST API for managing tasks
 
 | キーワード | 効果 | 例 |
 |---------|-----|-----|
+| `team` | 標準 Team オーケストレーション | `/team 3:executor "fix all TypeScript errors"` |
+| `omc-teams` | tmux CLI ワーカー (codex/gemini/claude) | `/omc-teams 2:codex "security review"` |
+| `ccg` | トライモデル Codex+Gemini オーケストレーション | `/ccg review this PR` |
 | `autopilot` | 完全自律実行 | `autopilot: build a todo app` |
 | `ralph` | 粘り強いモード | `ralph: refactor auth` |
 | `ulw` | 最大並列化 | `ulw fix all errors` |
 | `plan` | 計画インタビュー | `plan the API` |
 | `ralplan` | 反復的計画合意形成 | `ralplan this feature` |
+| `swarm` | レガシーキーワード（Team にルーティング） | `swarm 5 agents: fix lint errors` |
+| `ultrapilot` | レガシーキーワード（Team にルーティング） | `ultrapilot: build a fullstack app` |
 
 **ralph は ultrawork を含む:** ralph モードを有効にすると、ultrawork の並列実行が自動的に含まれます。キーワードを組み合わせる必要はありません。
 

package/README.ko.md

@@ -36,6 +36,55 @@ autopilot: build a REST API for managing tasks
 
 끝입니다. 나머지는 모두 자동입니다.
 
+## Team Mode (권장)
+
+**v4.1.7**부터 **Team**이 OMC의 표준 오케스트레이션 방식입니다. **swarm** 및 **ultrapilot** 같은 레거시 엔트리포인트는 계속 지원되지만, 이제 **내부적으로 Team으로 라우팅**됩니다.
+
+```bash
+/team 3:executor "fix all TypeScript errors"
+```
+
+Team은 단계별 파이프라인으로 실행됩니다:
+
+`team-plan → team-prd → team-exec → team-verify → team-fix (loop)`
+
+`~/.claude/settings.json`에서 Claude Code 네이티브 팀을 활성화하세요:
+
+```json
+{
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+  }
+}
+```
+
+> 팀이 비활성화된 경우 OMC가 경고를 표시하고 가능한 경우 팀 없이 실행으로 폴백합니다.
+
+### tmux CLI 워커 — Codex & Gemini (v4.4.0+)
+
+**v4.4.0에서 Codex/Gemini MCP 서버**(`x`, `g` 프로바이더)가 **제거됩니다**. `/omc-teams`를 사용하여 tmux 분할 창에서 실제 CLI 프로세스를 실행하세요:
+
+```bash
+/omc-teams 2:codex   "review auth module for security issues"
+/omc-teams 2:gemini  "redesign UI components for accessibility"
+/omc-teams 1:claude  "implement the payment flow"
+```
+
+하나의 명령으로 Codex + Gemini 작업을 처리하려면 **`/ccg`** 스킬을 사용하세요:
+
+```bash
+/ccg Review this PR — architecture (Codex) and UI components (Gemini)
+```
+
+| 스킬 | 워커 | 최적 용도 |
+|-------|---------|----------|
+| `/omc-teams N:codex` | N개 Codex CLI 창 | 코드 리뷰, 보안 분석, 아키텍처 |
+| `/omc-teams N:gemini` | N개 Gemini CLI 창 | UI/UX 디자인, 문서, 대용량 컨텍스트 |
+| `/omc-teams N:claude` | N개 Claude CLI 창 | tmux에서 Claude CLI를 통한 일반 작업 |
+| `/ccg` | Codex 1개 + Gemini 1개 | 병렬 트라이-모델 오케스트레이션 |
+
+워커는 요청 시 생성되고 작업 완료 후 종료됩니다 — 유휴 리소스 낭비 없음. `codex` / `gemini` CLI가 설치되어 있고 활성 tmux 세션이 필요합니다.
+
 > **참고: 패키지 이름** — 프로젝트 브랜드명은 **oh-my-claudecode** (저장소, 플러그인, 명령어)이지만, npm 패키지는 [`oh-my-claudecode`](https://www.npmjs.com/package/oh-my-claude-sisyphus)로 배포됩니다. npm/bun으로 CLI 도구를 설치할 때는 `npm install -g oh-my-claude-sisyphus`를 사용하세요.
 
 ### 업데이트
@@ -81,14 +130,16 @@ autopilot: build a REST API for managing tasks
 ### 실행 모드
 다양한 사용 사례를 위한 여러 전략 - 완전 자율 빌드부터 토큰 효율적인 리팩토링까지. [자세히 보기 →](https://yeachan-heo.github.io/oh-my-claudecode-website/docs.html#execution-modes)
 
-| 모드 | 속도 | 용도 |
-|------|-------|---------|
-| **Autopilot** | 빠름 | 완전 자율 워크플로우 |
-| **Ultrawork** | 병렬 | 모든 작업에 최대 병렬화 |
-| **Ralph** | 지속적 | 반드시 완료해야 하는 작업 |
-| **Ultrapilot** | 3-5배 빠름 | 다중 컴포넌트 시스템 |
-| **Swarm** | 협조적 | 병렬 독립 작업 |
-| **Pipeline** | 순차적 | 다단계 처리 |
+| 모드 | 특징 | 용도 |
+|------|---------|---------|
+| **Team (권장)** | 단계별 파이프라인 | 공유 작업 목록에서 협력하는 Claude 에이전트 |
+| **omc-teams** | tmux CLI 워커 | Codex/Gemini CLI 작업; 요청 시 실행, 완료 후 종료 |
+| **ccg** | 트라이-모델 병렬 | Codex(분석) + Gemini(디자인), Claude가 통합 |
+| **Autopilot** | 자율 실행 | 최소한의 설정으로 end-to-end 기능 개발 |
+| **Ultrawork** | 최대 병렬 | Team이 필요 없는 병렬 수정/리팩토링 |
+| **Ralph** | 지속 모드 | 완전히 완료되어야 하는 작업 |
+| **Pipeline** | 순차 처리 | 엄격한 순서가 필요한 다단계 변환 |
+| **Swarm / Ultrapilot (레거시)** | Team으로 라우팅 | 기존 워크플로우와 이전 문서 |
 
 ### 지능형 오케스트레이션
 
@@ -113,11 +164,16 @@ autopilot: build a REST API for managing tasks
 
 | 키워드 | 효과 | 예시 |
 |---------|--------|---------|
+| `team` | 표준 Team 오케스트레이션 | `/team 3:executor "fix all TypeScript errors"` |
+| `omc-teams` | tmux CLI 워커 (codex/gemini/claude) | `/omc-teams 2:codex "security review"` |
+| `ccg` | 트라이-모델 Codex+Gemini 오케스트레이션 | `/ccg review this PR` |
 | `autopilot` | 완전 자율 실행 | `autopilot: build a todo app` |
 | `ralph` | 지속 모드 | `ralph: refactor auth` |
 | `ulw` | 최대 병렬화 | `ulw fix all errors` |
 | `plan` | 계획 인터뷰 | `plan the API` |
 | `ralplan` | 반복적 계획 합의 | `ralplan this feature` |
+| `swarm` | 레거시 키워드 (Team으로 라우팅) | `swarm 5 agents: fix lint errors` |
+| `ultrapilot` | 레거시 키워드 (Team으로 라우팅) | `ultrapilot: build a fullstack app` |
 
 **ralph는 ultrawork를 포함합니다:** ralph 모드를 활성화하면 자동으로 ultrawork의 병렬 실행이 포함됩니다. 키워드를 결합할 필요가 없습니다.
 

package/README.pt.md

@@ -60,6 +60,31 @@ Ative os times nativos do Claude Code em `~/.claude/settings.json`:
 
 > Se os times estiverem desativados, o OMC vai avisar você e fazer fallback para execução sem Team quando possível.
 
+### Trabalhadores CLI tmux — Codex & Gemini (v4.4.0+)
+
+**v4.4.0 remove os servidores MCP de Codex/Gemini** (provedores `x`, `g`). Use `/omc-teams` para lançar processos CLI reais em painéis divididos do tmux:
+
+```bash
+/omc-teams 2:codex   "review auth module for security issues"
+/omc-teams 2:gemini  "redesign UI components for accessibility"
+/omc-teams 1:claude  "implement the payment flow"
+```
+
+Para trabalho misto de Codex + Gemini em um único comando, use a skill **`/ccg`**:
+
+```bash
+/ccg Review this PR — architecture (Codex) and UI components (Gemini)
+```
+
+| Skill | Trabalhadores | Melhor Para |
+|-------|---------|----------|
+| `/omc-teams N:codex` | N painéis Codex CLI | Revisão de código, análise de segurança, arquitetura |
+| `/omc-teams N:gemini` | N painéis Gemini CLI | Design UI/UX, docs, tarefas de grande contexto |
+| `/omc-teams N:claude` | N painéis Claude CLI | Tarefas gerais via Claude CLI no tmux |
+| `/ccg` | 1 Codex + 1 Gemini | Orquestração tri-modelo em paralelo |
+
+Trabalhadores são iniciados sob demanda e encerrados quando a tarefa é concluída — sem uso ocioso de recursos. Requer as CLIs `codex` / `gemini` instaladas e uma sessão tmux ativa.
+
 > **Observação: Nome do pacote** — O projeto usa a marca **oh-my-claudecode** (repo, plugin, comandos), mas o pacote npm é publicado como [`oh-my-claudecode`](https://www.npmjs.com/package/oh-my-claude-sisyphus). Se você instalar as ferramentas de CLI via npm/bun, use `npm install -g oh-my-claude-sisyphus`.
 
 ### Atualizando
@@ -109,6 +134,8 @@ Múltiplas estratégias para diferentes casos de uso — da orquestração com T
 | Modo | O que é | Usar para |
 |------|---------|-----------|
 | **Team (recommended)** | Pipeline canônico em estágios (`team-plan → team-prd → team-exec → team-verify → team-fix`) | Agentes coordenados trabalhando em uma lista de tarefas compartilhada |
+| **omc-teams** | Trabalhadores CLI tmux — processos reais `claude`/`codex`/`gemini` em painéis divididos | Tarefas Codex/Gemini CLI; criados sob demanda, encerrados ao terminar |
+| **ccg** | Tri-modelo: Codex (analítico) + Gemini (design) em paralelo, Claude sintetiza | Trabalho misto de backend+UI que precisa de Codex e Gemini |
 | **Autopilot** | Execução autônoma (um único agente líder) | Trabalho de feature ponta a ponta com cerimônia mínima |
 | **Ultrawork** | Paralelismo máximo (sem Team) | Rajadas de correções/refatorações paralelas quando Team não é necessário |
 | **Ralph** | Modo persistente com loops de verify/fix | Tarefas que precisam ser concluídas por completo (sem parciais silenciosos) |
@@ -139,6 +166,8 @@ Atalhos opcionais para usuários avançados. Linguagem natural funciona bem sem
 | Palavra-chave | Efeito | Exemplo |
 |---------------|--------|---------|
 | `team` | Orquestração canônica com Team | `/team 3:executor "fix all TypeScript errors"` |
+| `omc-teams` | Trabalhadores CLI tmux (codex/gemini/claude) | `/omc-teams 2:codex "security review"` |
+| `ccg` | Orquestação tri-modelo Codex+Gemini | `/ccg review this PR` |
 | `autopilot` | Execução autônoma completa | `autopilot: build a todo app` |
 | `ralph` | Modo persistente | `ralph: refactor auth` |
 | `ulw` | Paralelismo máximo | `ulw fix all errors` |

package/README.vi.md

@@ -60,6 +60,31 @@ Bật Claude Code native teams trong `~/.claude/settings.json`:
 
 > Nếu teams bị tắt, OMC sẽ cảnh báo và chuyển sang chế độ thực thi không dùng team khi có thể.
 
+### Công nhân CLI tmux — Codex & Gemini (v4.4.0+)
+
+**v4.4.0 xóa các máy chủ MCP Codex/Gemini** (nhà cung cấp `x`, `g`). Dùng `/omc-teams` để khởi động tiến trình CLI thực sự trong các pane tmux phân chia:
+
+```bash
+/omc-teams 2:codex   "review auth module for security issues"
+/omc-teams 2:gemini  "redesign UI components for accessibility"
+/omc-teams 1:claude  "implement the payment flow"
+```
+
+Để xử lý công việc Codex + Gemini trong một lệnh, dùng skill **`/ccg`**:
+
+```bash
+/ccg Review this PR — architecture (Codex) and UI components (Gemini)
+```
+
+| Skill | Công nhân | Tốt nhất cho |
+|-------|---------|----------|
+| `/omc-teams N:codex` | N pane Codex CLI | Xem xét code, phân tích bảo mật, kiến trúc |
+| `/omc-teams N:gemini` | N pane Gemini CLI | Thiết kế UI/UX, tài liệu, tác vụ ngữ cảnh lớn |
+| `/omc-teams N:claude` | N pane Claude CLI | Tác vụ chung qua Claude CLI trong tmux |
+| `/ccg` | 1 Codex + 1 Gemini | Điều phối ba mô hình song song |
+
+Công nhân được tạo theo yêu cầu và tắt khi hoàn thành tác vụ — không lãng phí tài nguyên. Cần cài `codex` / `gemini` CLI và có phiên tmux đang hoạt động.
+
 > **Lưu ý: Tên package** — Dự án được xây dựng thương hiệu là **oh-my-claudecode** (repo, plugin, commands), nhưng package npm được phát hành dưới tên [`oh-my-claudecode`](https://www.npmjs.com/package/oh-my-claude-sisyphus). Nếu bạn cài công cụ CLI qua npm/bun, hãy dùng `npm install -g oh-my-claude-sisyphus`.
 
 ### Cập nhật
@@ -109,6 +134,8 @@ Nhiều chiến lược cho nhiều tình huống — từ điều phối dựa
 | Mode | Nó là gì | Dùng cho |
 |------|------------|---------|
 | **Team (khuyến nghị)** | Pipeline chuẩn theo giai đoạn (`team-plan → team-prd → team-exec → team-verify → team-fix`) | Các tác tử phối hợp trên một danh sách nhiệm vụ chung |
+| **omc-teams** | Công nhân CLI tmux — tiến trình `claude`/`codex`/`gemini` thực trong pane chia | Tác vụ Codex/Gemini CLI; tạo theo yêu cầu, tắt khi xong |
+| **ccg** | Tri-model: Codex (phân tích) + Gemini (thiết kế) song song, Claude tổng hợp | Công việc backend+UI cần cả Codex và Gemini |
 | **Autopilot** | Thực thi tự động (một tác tử dẫn dắt) | Làm tính năng end-to-end với ít thao tác phụ |
 | **Ultrawork** | Song song tối đa (không dùng team) | Sửa lỗi/refactor kiểu burst song song khi không cần Team |
 | **Ralph** | Chế độ bền bỉ với vòng lặp verify/fix | Tác vụ bắt buộc hoàn tất đầy đủ (không có hoàn thành một phần âm thầm) |
@@ -139,6 +166,8 @@ Các phím tắt tùy chọn cho người dùng nâng cao. Không dùng chúng t
 | Keyword | Hiệu ứng | Ví dụ |
 |---------|--------|---------|
 | `team` | Điều phối Team chuẩn | `/team 3:executor "fix all TypeScript errors"` |
+| `omc-teams` | Công nhân CLI tmux (codex/gemini/claude) | `/omc-teams 2:codex "security review"` |
+| `ccg` | Điều phối tri-model Codex+Gemini | `/ccg review this PR` |
 | `autopilot` | Thực thi tự động toàn phần | `autopilot: build a todo app` |
 | `ralph` | Chế độ bền bỉ | `ralph: refactor auth` |
 | `ulw` | Song song tối đa | `ulw fix all errors` |

package/README.zh.md

@@ -36,6 +36,55 @@ autopilot: build a REST API for managing tasks
 
 就这么简单。其余都是自动的。
 
+## Team 模式（推荐）
+
+从 **v4.1.7** 开始，**Team** 是 OMC 的标准编排方式。**swarm** 和 **ultrapilot** 等旧版入口仍受支持，但现在**在底层路由到 Team**。
+
+```bash
+/team 3:executor "fix all TypeScript errors"
+```
+
+Team 按阶段化流水线运行：
+
+`team-plan → team-prd → team-exec → team-verify → team-fix (loop)`
+
+在 `~/.claude/settings.json` 中启用 Claude Code 原生团队：
+
+```json
+{
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+  }
+}
+```
+
+> 如果团队被禁用，OMC 会发出警告并在可能的情况下回退到非 Team 执行模式。
+
+### tmux CLI 工作者 — Codex & Gemini (v4.4.0+)
+
+**v4.4.0 移除了 Codex/Gemini MCP 服务器**（`x`、`g` 提供商）。请改用 `/omc-teams` 在 tmux 分屏中启动真实的 CLI 进程：
+
+```bash
+/omc-teams 2:codex   "review auth module for security issues"
+/omc-teams 2:gemini  "redesign UI components for accessibility"
+/omc-teams 1:claude  "implement the payment flow"
+```
+
+如需在一个命令中混合使用 Codex + Gemini，请使用 **`/ccg`** 技能：
+
+```bash
+/ccg Review this PR — architecture (Codex) and UI components (Gemini)
+```
+
+| 技能 | 工作者 | 最适合 |
+|-------|---------|----------|
+| `/omc-teams N:codex` | N 个 Codex CLI 窗格 | 代码审查、安全分析、架构 |
+| `/omc-teams N:gemini` | N 个 Gemini CLI 窗格 | UI/UX 设计、文档、大上下文任务 |
+| `/omc-teams N:claude` | N 个 Claude CLI 窗格 | 通过 tmux 中的 Claude CLI 处理通用任务 |
+| `/ccg` | 1 个 Codex + 1 个 Gemini | 并行三模型编排 |
+
+工作者按需生成，任务完成后自动退出 — 无空闲资源浪费。需要安装 `codex` / `gemini` CLI 并有活跃的 tmux 会话。
+
 > **注意：包命名** — 项目品牌名为 **oh-my-claudecode**（仓库、插件、命令），但 npm 包以 [`oh-my-claudecode`](https://www.npmjs.com/package/oh-my-claude-sisyphus) 发布。通过 npm/bun 安装 CLI 工具时，请使用 `npm install -g oh-my-claude-sisyphus`。
 
 ### 更新
@@ -81,14 +130,16 @@ autopilot: build a REST API for managing tasks
 ### 执行模式
 针对不同场景的多种策略 - 从全自动构建到 token 高效重构。[了解更多 →](https://yeachan-heo.github.io/oh-my-claudecode-website/docs.html#execution-modes)
 
-| 模式 | 速度 | 适用场景 |
-|------|-------|---------|
-| **Autopilot** | 快速 | 全自动工作流 |
-| **Ultrawork** | 并行 | 任何任务的最大并行化 |
-| **Ralph** | 持久 | 必须完整完成的任务 |
-| **Ultrapilot** | 3-5倍速 | 多组件系统 |
-| **Swarm** | 协同 | 并行独立任务 |
-| **Pipeline** | 顺序 | 多阶段处理 |
+| 模式 | 特点 | 适用场景 |
+|------|---------|---------|
+| **Team（推荐）** | 阶段化流水线 | 在共享任务列表上协作的 Claude 智能体 |
+| **omc-teams** | tmux CLI 工作者 | Codex/Gemini CLI 任务；按需生成，完成后退出 |
+| **ccg** | 三模型并行 | Codex（分析）+ Gemini（设计），Claude 合成 |
+| **Autopilot** | 自主执行 | 最小化繁琐配置的端到端功能开发 |
+| **Ultrawork** | 最大并行 | 不需要 Team 的并行修复/重构 |
+| **Ralph** | 持久模式 | 必须完整完成的任务 |
+| **Pipeline** | 顺序处理 | 需要严格顺序的多阶段转换 |
+| **Swarm / Ultrapilot（旧版）** | 路由到 Team | 现有工作流和旧文档 |
 
 ### 智能编排
 
@@ -113,11 +164,16 @@ autopilot: build a REST API for managing tasks
 
 | 关键词 | 效果 | 示例 |
 |---------|--------|---------|
+| `team` | 标准 Team 编排 | `/team 3:executor "fix all TypeScript errors"` |
+| `omc-teams` | tmux CLI 工作者 (codex/gemini/claude) | `/omc-teams 2:codex "security review"` |
+| `ccg` | 三模型 Codex+Gemini 编排 | `/ccg review this PR` |
 | `autopilot` | 全自动执行 | `autopilot: build a todo app` |
 | `ralph` | 持久模式 | `ralph: refactor auth` |
 | `ulw` | 最大并行化 | `ulw fix all errors` |
 | `plan` | 规划访谈 | `plan the API` |
 | `ralplan` | 迭代规划共识 | `ralplan this feature` |
+| `swarm` | 旧版关键词（路由到 Team） | `swarm 5 agents: fix lint errors` |
+| `ultrapilot` | 旧版关键词（路由到 Team） | `ultrapilot: build a fullstack app` |
 
 **ralph 包含 ultrawork：** 激活 ralph 模式时，会自动包含 ultrawork 的并行执行。无需组合关键词。
 

package/agents/architect.md

@@ -22,6 +22,7 @@ disallowedTools: Write, Edit
     - Recommendations are concrete and implementable (not "consider refactoring")
     - Trade-offs are acknowledged for each recommendation
     - Analysis addresses the actual question, not adjacent concerns
+    - In ralplan consensus reviews, strongest steelman antithesis and at least one real tradeoff tension are explicit
   </Success_Criteria>
 
   <Constraints>
@@ -30,6 +31,7 @@ disallowedTools: Write, Edit
     - Never provide generic advice that could apply to any codebase.
     - Acknowledge uncertainty when present rather than speculating.
     - Hand off to: analyst (requirements gaps), planner (plan creation), critic (plan review), qa-tester (runtime verification).
+    - In ralplan consensus reviews, never rubber-stamp the favored option without a steelman counterargument.
   </Constraints>
 
   <Investigation_Protocol>
@@ -40,6 +42,7 @@ disallowedTools: Write, Edit
     5) Synthesize into: Summary, Diagnosis, Root Cause, Recommendations (prioritized), Trade-offs, References.
     6) For non-obvious bugs, follow the 4-phase protocol: Root Cause Analysis, Pattern Analysis, Hypothesis Testing, Recommendation.
     7) Apply the 3-failure circuit breaker: if 3+ fix attempts fail, question the architecture rather than trying variations.
+    8) For ralplan consensus reviews: include (a) strongest antithesis against favored direction, (b) at least one meaningful tradeoff tension, (c) synthesis if feasible, and (d) in deliberate mode, explicit principle-violation flags.
   </Investigation_Protocol>
 
   <Tool_Usage>
@@ -48,13 +51,12 @@ disallowedTools: Write, Edit
     - Use lsp_diagnostics_directory to verify project-wide health.
     - Use ast_grep_search to find structural patterns (e.g., "all async functions without try/catch").
     - Use Bash with git blame/log for change history analysis.
-    <MCP_Consultation>
-      When a second opinion from an external model would improve quality:
-      - Codex (GPT): `mcp__x__ask_codex` with `agent_role`, `prompt` (inline text, foreground only)
-      - Gemini (1M context): `mcp__g__ask_gemini` with `agent_role`, `prompt` (inline text, foreground only)
-      For large context or background execution, use `prompt_file` and `output_file` instead.
-      Skip silently if tools are unavailable. Never block on external consultation.
-    </MCP_Consultation>
+    <External_Consultation>
+      When a second opinion would improve quality, spawn a Claude Task agent:
+      - Use `Task(subagent_type="oh-my-claudecode:critic", ...)` for plan/design challenge
+      - Use `/team` to spin up a CLI worker for large-context architectural analysis
+      Skip silently if delegation is unavailable. Never block on external consultation.
+    </External_Consultation>
   </Tool_Usage>
 
   <Execution_Policy>
@@ -83,6 +85,12 @@ disallowedTools: Write, Edit
     | A | ... | ... |
     | B | ... | ... |
 
+    ## Consensus Addendum (ralplan reviews only)
+    - **Antithesis (steelman):** [Strongest counterargument against favored direction]
+    - **Tradeoff tension:** [Meaningful tension that cannot be ignored]
+    - **Synthesis (if viable):** [How to preserve strengths from competing options]
+    - **Principle violations (deliberate mode):** [Any principle broken, with severity]
+
     ## References
     - `path/to/file.ts:42` - [what it shows]
     - `path/to/other.ts:108` - [what it shows]
@@ -107,5 +115,7 @@ disallowedTools: Write, Edit
     - Is the root cause identified (not just symptoms)?
     - Are recommendations concrete and implementable?
     - Did I acknowledge trade-offs?
+    - If this was a ralplan review, did I provide antithesis + tradeoff tension (+ synthesis when possible)?
+    - In deliberate mode reviews, did I flag principle violations explicitly?
   </Final_Checklist>
 </Agent_Prompt>

package/agents/code-reviewer.md

@@ -47,13 +47,12 @@ disallowedTools: Write, Edit
     - Use ast_grep_search to detect patterns: `console.log($$$ARGS)`, `catch ($E) { }`, `apiKey = "$VALUE"`.
     - Use Read to examine full file context around changes.
     - Use Grep to find related code that might be affected.
-    <MCP_Consultation>
-      When a second opinion from an external model would improve quality:
-      - Codex (GPT): `mcp__x__ask_codex` with `agent_role`, `prompt` (inline text, foreground only)
-      - Gemini (1M context): `mcp__g__ask_gemini` with `agent_role`, `prompt` (inline text, foreground only)
-      For large context or background execution, use `prompt_file` and `output_file` instead.
-      Skip silently if tools are unavailable. Never block on external consultation.
-    </MCP_Consultation>
+    <External_Consultation>
+      When a second opinion would improve quality, spawn a Claude Task agent:
+      - Use `Task(subagent_type="oh-my-claudecode:code-reviewer", ...)` for cross-validation
+      - Use `/team` to spin up a CLI worker for large-scale code review tasks
+      Skip silently if delegation is unavailable. Never block on external consultation.
+    </External_Consultation>
   </Tool_Usage>
 
   <Execution_Policy>