From 3c381b93053d1ad0fc12df319c4c18814cedcc40 Mon Sep 17 00:00:00 2001
From: Matt Van Horn <mvanhorn@gmail.com>
Date: Sat, 24 Jan 2026 07:41:44 -0800
Subject: [PATCH] Add Codex + Claude Code workflow example
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Shows /last30days discovering emerging developer workflows:
- MCP integration pattern for combining Claude Code + Codex
- Review loop workflow (Claude builds → Codex reviews → Claude fixes)
- Actual implementation with claude mcp add command

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---
 README.md | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 61 insertions(+)

diff --git a/README.md b/README.md
index 0fff0ad..a633662 100644
--- a/README.md
+++ b/README.md
@@ -377,6 +377,67 @@ This example shows /last30days learning **music AI prompting patterns** (bracket
 
 ---
 
+## Example: Developer Workflow Discovery (Codex + Claude Code)
+
+**Query:** `/last30days how do I use Codex with Claude Code on same app to make it better`
+
+**Research Output:**
+> Developers are combining Claude Code and Codex through MCP integration and custom plugins. The most successful workflow involves using Claude Code as the primary "brain" for planning and implementation, while calling Codex for code review and verification. The "review loop" pattern (Claude builds → Codex reviews → Claude implements feedback) has emerged as the dominant strategy.
+
+**Key patterns discovered:**
+1. MCP Integration - Add Codex as an MCP server inside Claude Code
+2. Review Loop Workflow - Claude implements, Codex reviews, Claude fixes
+3. Task Division - Claude for planning/coding, Codex for review/debugging
+4. Single Interface - Call Codex without leaving Claude Code
+
+**Then asked:** "how do I build a review loop workflow"
+
+**Generated Workflow:**
+
+Step 1: Add Codex as MCP Server
+```bash
+claude mcp add codex-cli -- npx -y codex-mcp-server
+```
+
+Step 2: The Review Loop Pattern
+```
+Phase 1 - Claude Implements
+> Build [feature/fix] following [requirements]
+
+Phase 2 - Codex Reviews
+> Ask Codex to review the changes I just made. Look for bugs,
+> edge cases, performance issues, security concerns.
+
+Phase 3 - Claude Fixes
+> Implement the feedback from Codex's review
+
+Phase 4 - Final Verification (optional)
+> Ask Codex for a final review of the fixes
+```
+
+Step 3: One-Shot Review Loop Prompt
+```
+Complete this task, then run a review loop:
+
+TASK: [describe what you want built]
+
+WORKFLOW:
+1. Implement the task fully
+2. When done, call Codex via MCP to review your changes
+3. Parse Codex's feedback and fix any issues it identifies
+4. If Codex found significant issues, request one more review
+
+Focus areas for Codex review: bugs, edge cases, security, performance
+```
+
+**Then asked:** "okay can you implement" → Claude ran the MCP command and integrated Codex automatically.
+
+**Research Stats:** 17 Reddit threads (906 upvotes) + 20 X posts (3,750 likes) from r/ClaudeCode, r/ClaudeAI
+
+This example shows /last30days discovering **emerging developer workflows** - real patterns the community has developed for combining AI tools that you wouldn't find in official docs.
+
+---
+
 ## Options
 
 | Flag | Description |