oh-my-customcodex 0.5.8 → 0.5.10

package/templates/guides/claude-code/15-version-compatibility.md

@@ -2,6 +2,30 @@
 
 This guide records Claude Code release-note impact that affects the Claude compatibility template. The Codex-native runtime still uses `.codex/**` and OMX as the primary surface.
 
+## v2.1.158
+
+Published: 2026-05-30.
+
+Source: upstream oh-my-customcode #1264, Codex port #1436.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Auto mode is available on Bedrock, Vertex, and Foundry for Opus 4.7 and Opus 4.8 via `CLAUDE_CODE_ENABLE_AUTO_MODE=1` | Claude compatibility sessions can opt into provider-backed auto mode for those Opus surfaces. Codex-native model routing and approval policy are unchanged. | Document as Claude provider compatibility only. Do not infer Codex auto-mode behavior from this env var. |
+
+## v2.1.157
+
+Published: 2026-05-29.
+
+Source: upstream oh-my-customcode #1265, Codex port #1437.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Plugins under `.claude/skills` auto-load, `claude plugin init <name>` scaffolds plugins there, and `/plugin` has argument autocomplete | Useful for Claude compatibility plugin setup. Codex-native skills remain under `.codex/skills`, `.agents/skills`, and OMX skill roots. | Keep `.codex/OMX` primary. Mention `.claude/skills` only when documenting Claude plugin compatibility. |
+| `claude agents` honors the `agent` field in `settings.json`, with `--agent <name>` as an override | Claude dispatched sessions can inherit a configured default agent unless explicitly overridden. | Do not mirror this into Codex routing. Codex native subagents still follow prompt routing, role metadata, and explicit delegation. |
+| `EnterWorktree` can switch between Claude-managed worktrees mid-session, and Claude-managed worktrees are left unlocked for `git worktree remove`/`prune` cleanup | Claude worktree lifecycle is more flexible and less likely to leave locked cleanup blockers. | Keep auto-dev work in clean worktrees, verify `git status`, and do not treat Claude-managed worktree state as OMX state. |
+| `tool_decision` telemetry can include `tool_parameters` such as Bash commands and MCP/skill names when `OTEL_LOG_TOOL_DETAILS=1` | Telemetry may contain more detailed operational data, including command and tool-parameter strings. | Treat logs as potentially sensitive. Avoid exporting transcripts or telemetry that may expose secrets, credentials, or privileged commands. |
+| Background/session fixes cover parked subagents, leaked background shells, orphaned `.claude/worktrees`, resume state, date after sleep/wake, fullscreen picker cleanup, current linked worktree return, image placeholders, network prompts, and tmux clipboard behavior | Reduces false blockers and stale-state surprises in Claude compatibility sessions. | No Codex runtime change. Continue using OMX state, Codex worktree checks, and direct command evidence for Codex-native completion claims. |
+
 ## v2.1.156
 
 Published: 2026-05-29.

package/templates/guides/multi-agent-debate-patterns/README.md

@@ -4,7 +4,7 @@
 
 | Pattern | Goal | Use When |
 |---------|------|----------|
-| `agora` | Reach adversarial consensus | Release gates, design approval, high-risk specs |
+| `roundtable-debate` | Preserve dissent while reaching a bounded decision | Release gates, design approval, high-risk specs with minority risks |
 | `roundtable-debate` | Preserve dissent | Strategy choices, tradeoffs, ambiguous product or architecture decisions |
 
 ## Failure Modes

package/templates/guides/multi-provider-exec/README.md

@@ -1,83 +1,13 @@
-# Multi-Provider Exec
+# External Interop Guidance
 
-## Overview
+The packaged multi-provider exec skills have been retired. For Codex interoperability, use the official Claude Code plugin `openai/codex-plugin-cc` only when it is explicitly installed and requested.
 
-Unified reference for executing prompts through external LLM providers via exec skills. Complements the [Multi-Model Routing](../multi-model-routing/README.md) guide (Claude model selection) with cross-provider execution capabilities.
+## Current Paths
 
-Inspired by OpenHarness's provider profile switching pattern, adapted for oh-my-customcodex's skill-based architecture.
+| Need | Preferred path | Notes |
+|------|----------------|-------|
+| Codex interop | `openai/codex-plugin-cc` | Official plugin path; opt-in only. |
+| Token-optimized local command output | `rtk-exec` | Existing RTK proxy remains supported. |
+| Research or independent review | `researcher`, expert agents, or `roundtable-debate` | Prefer in-repo agent workflows unless plugin interop is requested. |
 
-## Provider Matrix
-
-| Provider | Skill | CLI Dependency | Model | Strengths |
-|----------|-------|---------------|-------|-----------|
-| OpenAI (Codex) | `codex-exec` | `codex` CLI | GPT-5.4 | Code generation, broad knowledge |
-| Google (Gemini) | `gemini-exec` | `gemini` CLI | Gemini 2.5 Pro | Long context, multimodal |
-| RTK (proxy) | `rtk-exec` | `rtk` CLI | Configurable | Token-optimized output, cost reduction |
-
-## Availability Detection
-
-The `session-env-check.sh` hook (SessionStart) auto-detects available providers:
-
-```
-[SessionStart] Checking external CLI availability...
-  codex: ✓ available
-  gemini: ✗ not found
-  rtk: ✓ available
-```
-
-Providers are opt-in — missing CLIs are silently skipped.
-
-## Usage Patterns
-
-### Direct Invocation
-
-```
-/codex-exec "Review this function for security issues"
-/gemini-exec "Analyze this architecture diagram"
-/rtk-exec "List files matching pattern X"
-```
-
-### Provider Selection Guide
-
-| Task | Recommended Provider | Rationale |
-|------|---------------------|-----------|
-| Second opinion on code review | codex-exec | Independent model reduces confirmation bias |
-| Long document analysis | gemini-exec | 1M+ context window |
-| Token-heavy batch operations | rtk-exec | Compressed output reduces context cost |
-| Security audit cross-check | codex-exec | Different training data catches different patterns |
-| Multi-model verification | All three | `/multi-model-verification` skill orchestrates this |
-
-### Integration with Existing Skills
-
-| Skill | Uses Provider | How |
-|-------|--------------|-----|
-| `multi-model-verification` | codex-exec + gemini-exec | Parallel verification with severity classification |
-| `reasoning-sandwich` | Any exec skill | Pre/post reasoning with different models |
-| `model-escalation` | Claude models only | Internal escalation (haiku→sonnet→opus), not cross-provider |
-
-## Relationship to Multi-Model Routing
-
-| Aspect | Multi-Model Routing | Multi-Provider Exec |
-|--------|--------------------|--------------------|
-| Scope | Claude model selection | Cross-provider execution |
-| Models | haiku / sonnet / opus | GPT-5.4 / Gemini 2.5 / RTK proxy |
-| Mechanism | `model` frontmatter field | Exec skill invocation |
-| Use case | Cost/quality optimization within Claude | Independent verification, specialized tasks |
-| Guide | `guides/multi-model-routing/` | `guides/multi-provider-exec/` |
-
-## Configuration
-
-No global configuration required. Each exec skill reads its own CLI configuration:
-
-| Skill | Config Source |
-|-------|-------------|
-| codex-exec | `~/.codex/config` or CODEX_API_KEY env |
-| gemini-exec | `~/.gemini/config` or GEMINI_API_KEY env |
-| rtk-exec | RTK proxy running on localhost |
-
-## Limitations
-
-- Provider availability depends on user's CLI installations
-- Cross-provider results are advisory — Claude remains the primary execution engine
-- No automatic fallback between providers (by design — explicit selection preferred)
-- Rate limits and costs are provider-specific and not tracked by oh-my-customcodex
+Do not auto-delegate to retired provider wrapper skills. Keep expert agents responsible for reviewing any plugin-assisted output.

package/templates/manifest.json

@@ -1,11 +1,11 @@
 {
-  "version": "0.5.8",
+  "version": "0.5.10",
   "requiresCC": ">=2.1.121",
   "claudeCode": {
     "minimumVersion": "2.1.121",
     "protectedPathBypassVersion": "2.1.126"
   },
-  "lastUpdated": "2026-05-30T00:00:00.000Z",
+  "lastUpdated": "2026-06-01T00:00:00.000Z",
   "components": [
     {
       "name": "rules",
@@ -23,7 +23,7 @@
       "name": "skills",
       "path": ".agents/skills",
       "description": "Reusable skill modules (project-scoped repo skills)",
-      "files": 123
+      "files": 120
     },
     {
       "name": "guides",

package/templates/.claude/skills/agora/SKILL.md

@@ -1,209 +0,0 @@
----
-name: omcustomcodex:agora
-description: "Multi-LLM adversarial consensus loop — 3+ LLMs compete to find flaws in designs/specs until unanimous agreement is reached"
-user-invocable: true
-argument-hint: "<document-path> [--rounds N] [--severity-threshold HIGH]"
-effort: max
-scope: core
-version: 1.0.0
-source:
-  type: external
-  origin: github
-  url: https://github.com/baekenough/baekenough-skills
-  version: 1.0.0
----
-
-# Agora: Multi-LLM Adversarial Consensus
-
-3개 이상의 LLM(Claude, Codex/GPT, Gemini)이 경쟁적으로 설계/문서의 결함을 찾고, 만장일치 합의에 도달할 때까지 반복하는 적대적 교차 검증 스킬.
-
-## Prerequisites
-
-- `codex-exec` skill (Codex/GPT 호출)
-- `gemini-exec` skill (Gemini 호출)
-- Agent Teams enabled (`OMCODEX_AGENT_TEAMS=1`) or Agent tool available
-
-## Sensitive-Path Delegation
-
-Sensitive-path compatibility note: if this skill delegates work that touches `.claude/**`, `.claude/outputs/**`, `templates/.claude/**`, or read-only measurements of those paths, keep `.codex/**` edits on the normal Codex path. On Claude Code v2.1.121+ with `bypassPermissions`, direct writes to `.claude/skills/`, `.claude/agents/`, and `.claude/commands/` are allowed; on v2.1.126+ that extends to broader protected paths. Only use `/tmp/{skill}-{timestamp}.md` as a legacy fallback when the target runtime is older or still prompts.
-
-## Usage
-
-```
-/omcustomcodex:agora docs/design.md                           # Default: 3 LLMs, unlimited rounds
-/omcustomcodex:agora docs/design.md --rounds 10               # Max 10 rounds
-/omcustomcodex:agora docs/design.md --severity-threshold HIGH # Exit when no HIGH+ findings
-/omcustomcodex:agora docs/design.md --models claude,codex     # 2 LLMs only
-```
-
-## Workflow
-
-### Phase 1: Setup
-1. Read the target document
-2. Create Agent Team: `TeamCreate("agora-review")`
-3. Create review tasks per focus area
-
-### Phase 2: Spawn Reviewers (parallel)
-Spawn 3 reviewers as Agent Team members:
-
-```
-
-### Anti-Groupthink Mode
-
-Use `--anti-groupthink` when consensus itself is a risk:
-
-1. Reviewers submit independent findings before seeing peer output.
-2. One reviewer is assigned as devil's advocate.
-3. Minority findings are preserved unless the synthesis explicitly rejects them with evidence.
-4. Debate is capped at two challenge rounds before the lead either decides or requests more facts.
-
-For decisions where dissent preservation is the main goal, use `roundtable-debate` directly instead of `agora`.
-Agent(name: "claude-critic", model: opus, effort: max)
-  → 20-point deep adversarial review
-  
-Agent(name: "codex-critic", model: opus)
-  → Invoke Skill(codex-exec) for GPT perspective + independent Claude analysis
-  
-Agent(name: "gemini-critic", model: opus)  
-  → Invoke Skill(gemini-exec) for Gemini perspective + independent Claude analysis
-```
-
-### Phase 3: Independent Review
-Each reviewer performs adversarial review with this template:
-
-```
-For EACH review point:
-### Round N: [Topic]
-**Severity**: CRITICAL / HIGH / MEDIUM / LOW
-**Flaw**: [Specific, concrete problem description]
-**Evidence**: [Why this is real, not theoretical]
-**Impact**: [What happens if not addressed]
-**Counter-argument**: [Best case FOR the current design]
-**Verdict**: KEEP / MODIFY / REJECT
-```
-
-Review areas (adapt to document type):
-- Architecture fundamentals
-- Component/service design
-- Data architecture
-- Security & resilience
-- Feasibility & deployment
-- Testing strategy
-- Operational complexity
-
-### Phase 4: Cross-Review (Peer-to-Peer)
-Each reviewer sends findings to the other two via `SendMessage`.
-
-Counter-review template:
-1. Which findings do you **AGREE** with? (and why)
-2. Which findings do you **DISAGREE** with? (evidence-based rebuttal)
-3. What did they **MISS** that you caught?
-4. What did they catch that you **MISSED**?
-5. **SEVERITY** adjustments — upgrade or downgrade with justification
-
-### Phase 5: Synthesis
-Team lead aggregates all findings:
-
-```
-UNANIMOUS CRITICAL: [findings all 3 agreed on]
-STRONG AGREEMENT:   [findings 2/3 agreed on]
-SPLIT DECISIONS:    [findings with disagreement + resolution]
-```
-
-Determine verdict:
-- **BUILD**: No CRITICAL, no unresolved HIGH
-- **BUILD WITH CHANGES**: No CRITICAL, HIGH findings have accepted mitigations
-- **REDESIGN**: Any unresolved CRITICAL findings
-- **ABANDON**: Fundamental concept is flawed
-
-### Phase 6: Loop (if REDESIGN)
-1. Team lead produces/delegates redesign addressing ALL critical findings
-2. New version sent to ALL reviewers: `SendMessage(to: "*")`
-3. Reviewers re-review → GOTO Phase 4
-4. Repeat until EXIT criteria met
-
-### Phase 7: Exit (consensus reached)
-When ALL reviewers agree BUILD or BUILD WITH CHANGES:
-1. Produce final consensus report
-2. Write to `.codex/outputs/sessions/{date}/agora-{topic}-{time}.md`
-3. Shut down team: `SendMessage(to: "*", message: {type: "shutdown_request"})`
-
-## Reviewer Principles
-
-1. **NEUTRAL** — no reviewer has home team advantage
-2. **COMPETITIVE** — find flaws others missed
-3. **CRITICAL** — "fewer than 5 CRITICAL flaws = not looking hard enough"
-4. **EVIDENCE-BASED** — every finding cites specific evidence
-5. **CONSTRUCTIVE** — every flaw includes recommended fix
-6. **CONVERGENT** — goal is consensus, not endless disagreement
-
-## Consensus Criteria
-
-| Condition | Required |
-|-----------|----------|
-| CRITICAL findings resolved | ALL |
-| HIGH findings resolved or accepted | ALL |
-| All reviewers rate BUILD or BUILD WITH CHANGES | YES |
-| Cross-review disagreements resolved | ALL |
-
-## Output Format
-
-```markdown
-# Agora Consensus Report
-
-## Document: [path]
-## Rounds: [N]
-## Reviewers: [list with LLM models used]
-
-## Verdict: [BUILD / BUILD WITH CHANGES / REDESIGN]
-
-## Unanimous Findings
-| # | Finding | Severity | All 3 Agree |
-|---|---------|----------|-------------|
-
-## Required Changes Before Build
-1. [change with source reviewer]
-2. ...
-
-## Accepted Risks
-- [finding accepted with justification]
-
-## Unique Contributions Per Reviewer
-| Reviewer | Findings Others Missed |
-|----------|----------------------|
-
-## Process Metrics
-- Rounds: N
-- Total findings: N
-- Cross-adopted: N
-- Severity upgrades: N
-- Severity downgrades: N
-- Disagreements raised: N
-- Disagreements resolved: N/N
-```
-
-## Configuration
-
-```yaml
-# Default settings
-agora:
-  max_rounds: unlimited       # Set --rounds to limit
-  severity_threshold: HIGH    # EXIT when no findings >= threshold
-  models:
-    - claude (opus, max effort)
-    - codex (via codex-exec skill)
-    - gemini (via gemini-exec skill)
-  review_points: 20           # Per reviewer
-  cross_review: true          # Peer-to-peer sharing
-  auto_redesign: true         # Auto-produce redesign on REDESIGN verdict
-```
-
-## Anti-Patterns
-
-| Anti-Pattern | Why Wrong | Correct |
-|-------------|-----------|---------|
-| Single LLM review | Misses blind spots | 3+ LLMs find complementary flaws |
-| No cross-review | Reviewers don't challenge each other | Peer-to-peer sharing surfaces disagreements |
-| Accepting first BUILD | May miss edge cases | Loop until ALL agree |
-| Ignoring split decisions | Unresolved disagreements fester | Resolve every split with evidence |
-| Push for consensus too fast | Premature agreement | Let reviewers challenge freely |

package/templates/.claude/skills/codex-exec/SKILL.md

@@ -1,218 +0,0 @@
----
-name: codex-exec
-description: Execute OpenAI Codex CLI prompts and return results
-scope: core
-argument-hint: "<prompt> [--json] [--output <path>] [--model <name>] [--timeout <ms>] [--effort <level>]"
-user-invocable: true
----
-
-# Codex Exec Skill
-
-Execute OpenAI Codex CLI prompts in non-interactive mode and return structured results. Enables Claude + Codex hybrid workflows.
-
-## Options
-
-```
-<prompt>          Required. The prompt to send to Codex CLI
---json            Return structured JSON Lines output
---output <path>   Save final message to file
---model <name>    Model override (default: Codex CLI default model)
---timeout <ms>    Execution timeout (default: 120000, max: 600000)
---full-auto       Enable auto-approval mode (codex -a full-auto)
---working-dir     Working directory for Codex execution
---effort <level>  Set reasoning effort level (minimal, low, medium, high, xhigh)
-                  Maps to Codex CLI's model_reasoning_effort config
-                  Default: uses Codex CLI's configured default
-                  Recommended: xhigh for research/analysis tasks
-```
-
-## Workflow
-
-```
-1. Pre-checks
-   - Verify `codex` binary is installed (which codex || npx codex --version)
-   - Verify authentication (`OPENAI_API_KEY`, `CODEX_API_KEY`, or stored `codex login` / ChatGPT login)
-2. Build command
-   - Base: codex exec --ephemeral "<prompt>"
-   - Apply options: --json, --model, --full-auto, -C <dir>
-   - Set --working-dir if specified
-3. Execute
-   - Run via Bash tool with timeout (default 2min, max 10min)
-   - Or use helper script: node .codex/skills/codex-exec/scripts/codex-wrapper.cjs
-4. Parse output
-   - Text mode: return raw stdout
-   - JSON mode: parse JSON Lines, extract final assistant message
-5. Report results
-   - Format output with execution metadata
-```
-
-## Safety Defaults
-
-- `--ephemeral`: No session persistence (conversations not saved)
-- Default mode: Normal approval (Codex prompts for confirmation)
-- Override with `--full-auto` only when explicitly requested
-
-## Output Format
-
-### Success (Text Mode)
-```
-[Codex Exec] Completed
-
-Model: (default)
-Duration: 23.4s
-Working Dir: /path/to/project
-
---- Output ---
-{codex response text}
-```
-
-### Success (JSON Mode)
-```
-[Codex Exec] Completed (JSON)
-
-Model: (default)
-Duration: 23.4s
-Events: 12
-
---- Final Message ---
-{extracted final assistant message}
-```
-
-### Failure
-```
-[Codex Exec] Failed
-
-Error: {error_message}
-Exit Code: {code}
-Suggested Fix: {suggestion}
-```
-
-## Helper Script
-
-For complex executions, use the wrapper script:
-```bash
-node .codex/skills/codex-exec/scripts/codex-wrapper.cjs --prompt "your prompt" [options]
-```
-
-The wrapper provides:
-- Environment validation (binary + auth checks)
-- Safe command construction
-- JSON Lines parsing with event extraction
-- Structured JSON output
-- Timeout handling with graceful termination
-
-## Examples
-
-```bash
-# Simple text prompt
-codex-exec "explain what this project does"
-
-# JSON output with model override
-codex-exec "list all TODO items" --json
-
-# Save output to file
-codex-exec "generate a README" --output ./README.md
-
-# Full auto mode with custom timeout
-codex-exec "fix the failing tests" --full-auto --timeout 300000
-
-# Specify working directory
-codex-exec "analyze the codebase" --working-dir /path/to/project
-```
-
-## Integration
-
-Works with the orchestrator pattern:
-- Main conversation delegates Codex execution via this skill
-- Results are returned to the main conversation for further processing
-- Can be chained with other skills (e.g., dev-review after Codex generates code)
-
-## Availability Check
-
-codex-exec requires the Codex CLI binary to be installed and authenticated. The skill is only usable when:
-
-1. `codex` binary is found in PATH (`which codex` succeeds)
-2. Authentication is valid (`OPENAI_API_KEY`, `CODEX_API_KEY`, or stored auth from `codex login --api-key` / ChatGPT login)
-
-If either check fails, this skill cannot be used. Fall back to Claude agents for the task.
-
-> **Note**: This skill is invoked via `/codex-exec` command, delegated by the orchestrator, or suggested by routing skills when codex is available. The intent-detection system can trigger it for research (xhigh) and code generation (hybrid) workflows.
-
-## Agent Teams Integration
-
-When used within Agent Teams (requires explicit invocation):
-
-1. **As delegated task**: orchestrator explicitly delegates codex-exec for code generation
-2. **Hybrid workflow**: Claude team member analyzes → orchestrator invokes codex-exec → Claude reviews
-3. **Iteration**: Team messaging enables review-fix cycles between Claude and Codex outputs
-
-```
-Orchestrator delegates generation task
-  → /codex-exec invoked explicitly
-  → Output returned to orchestrator
-  → Reviewer validates quality
-  → Iterate if needed
-```
-
-## Research Workflow
-
-When the orchestrator or intent-detection detects a research/information gathering request (routing_rule in agent-triggers.yaml):
-
-1. **Check Codex availability**: Verify `codex` binary plus `OPENAI_API_KEY`, `CODEX_API_KEY`, or stored `codex login` auth
-2. **If available**: Execute with xhigh reasoning effort for thorough research
-3. **If unavailable**: Fall back to Claude's WebFetch/WebSearch
-
-### Research Command Pattern
-
-```
-/codex-exec "Research and analyze: {topic}. Provide structured findings with sources." --effort xhigh --full-auto --json
-```
-
-### Effort Level Guide
-
-| Level | Use Case | Speed | Depth |
-|-------|----------|-------|-------|
-| minimal | Quick lookups | Fastest | Surface |
-| low | Simple queries | Fast | Basic |
-| medium | General tasks | Balanced | Standard |
-| high | Complex analysis | Slower | Deep |
-| xhigh | Research & investigation | Slowest | Maximum |
-
-## Code Generation Workflow
-
-When routing skills detect a code generation task and codex is available:
-
-1. **Check availability**: Verify the codex CLI directly (`command -v codex`) or via current session diagnostics
-2. **If available + new file creation**: Suggest hybrid workflow
-3. **Hybrid pattern**:
-   - codex-exec generates initial code (fast, broad generation)
-   - Claude expert reviews for quality, patterns, best practices
-   - Iterate if needed
-
-### Suitable Tasks
-- New file scaffolding
-- Boilerplate generation
-- Test stub creation
-- Documentation generation
-
-### Unsuitable Tasks
-- Modifying existing code (Claude expert better at understanding context)
-- Architecture decisions (requires reasoning, not generation)
-- Bug fixes (requires deep code understanding)
-
-### Code Generation Command Pattern
-```
-/codex-exec "Generate {description} following {framework} best practices" --effort high --full-auto
-```
-
-## Browser Verify Workflow
-
-For frontend or browser-visible changes, use a Build + Vision + Verify loop instead of stopping at a successful build:
-
-1. Build or start the local dev server.
-2. Open the target in the available browser automation surface.
-3. Capture screenshot evidence and console/network errors.
-4. If the visual state or console is wrong, run `codex-exec` with the concrete evidence and repeat.
-5. Stop only when build, browser render, and error checks all pass.
-
-This pattern composes with the Codex App Browser Use plugin or any local browser MCP. Keep the loop evidence-driven: screenshot, console output, network status, and the exact command that produced the build.