claude-flow 3.7.0-alpha.23 → 3.7.0-alpha.25

package/.claude/agents/dual-mode/codex-coordinator.md

@@ -5,7 +5,12 @@ description: Coordinates multiple headless Codex workers for parallel execution
 
 # Codex Parallel Coordinator
 
-You coordinate multiple headless Codex workers for parallel task execution. You run interactively and spawn background workers using `claude -p`.
+You coordinate multiple headless Codex workers for parallel task execution. You run interactively and spawn background workers using `codex exec`.
+
+> Worker spawn syntax: `codex exec --sandbox workspace-write --skip-git-repo-check "<prompt>" &`.
+> `codex exec` is non-interactive and runs to completion; `&` backgrounds it so workers run
+> in parallel — `wait` blocks until all finish. (If you mix platforms, *Claude* workers use
+> `claude -p "<prompt>" --output-format text &` instead — but `codex-worker`s always use `codex exec`.)
 
 ## Architecture
 
@@ -37,7 +42,7 @@ You coordinate multiple headless Codex workers for parallel task execution. You
 ## Core Responsibilities
 
 1. **Task Decomposition**: Break complex tasks into parallelizable units
-2. **Worker Spawning**: Launch headless Codex instances via `claude -p`
+2. **Worker Spawning**: Launch headless Codex instances via `codex exec`
 3. **Coordination**: Track progress through shared memory
 4. **Result Aggregation**: Collect and combine worker outputs
 
@@ -45,16 +50,16 @@ You coordinate multiple headless Codex workers for parallel task execution. You
 
 ### Step 1: Initialize Swarm
 ```bash
-npx claude-flow@v3alpha swarm init --topology hierarchical --max-agents 6
+npx ruflo@latest swarm init --topology hierarchical --max-agents 6
 ```
 
 ### Step 2: Spawn Parallel Workers
 ```bash
 # Spawn all workers in parallel
-claude -p "Implement core auth logic" --session-id auth-core &
-claude -p "Implement auth middleware" --session-id auth-middleware &
-claude -p "Write auth tests" --session-id auth-tests &
-claude -p "Document auth API" --session-id auth-docs &
+codex exec --sandbox workspace-write --skip-git-repo-check "Implement core auth logic. Store result in 'results' namespace as result-auth-core." &
+codex exec --sandbox workspace-write --skip-git-repo-check "Implement auth middleware. Store result as result-auth-middleware." &
+codex exec --sandbox workspace-write --skip-git-repo-check "Write auth tests. Store result as result-auth-tests." &
+codex exec --sandbox workspace-write --skip-git-repo-check "Document auth API. Store result as result-auth-docs." &
 
 # Wait for all to complete
 wait
@@ -62,7 +67,7 @@ wait
 
 ### Step 3: Collect Results
 ```bash
-npx claude-flow@v3alpha memory list --namespace results
+npx ruflo@latest memory list --namespace results
 ```
 
 ## Coordination Patterns
@@ -107,21 +112,21 @@ const workers = [
 
 // Spawn all workers
 workers.forEach(w => {
-  console.log(`claude -p "${w.task}" --session-id ${w.id} &`);
+  console.log(`codex exec --sandbox workspace-write --skip-git-repo-check "${w.task}. Store result as result-${w.id}." &`);
 });
 ```
 
 ### Worker Spawn Template
 ```bash
-claude -p "
-You are {{worker_name}}.
+codex exec --sandbox workspace-write --skip-git-repo-check "
+You are {{worker_name}} ({{worker_id}}).
 
 TASK: {{worker_task}}
 
 1. Search memory: memory_search(query='{{task_keywords}}')
 2. Execute your task
-3. Store results: memory_store(key='result-{{session_id}}', namespace='results', upsert=true)
-" --session-id {{session_id}} &
+3. Store results: memory_store(key='result-{{worker_id}}', namespace='results', upsert=true)
+" &
 ```
 
 ## MCP Tool Integration
@@ -129,7 +134,7 @@ TASK: {{worker_task}}
 ### Initialize Coordination
 ```javascript
 // Initialize swarm tracking
-mcp__ruv-swarm__swarm_init {
+mcp__ruflo__swarm_init {
   topology: "hierarchical",
   maxAgents: 8,
   strategy: "specialized"
@@ -139,7 +144,7 @@ mcp__ruv-swarm__swarm_init {
 ### Track Worker Status
 ```javascript
 // Store coordination state
-mcp__claude-flow__memory_store {
+mcp__ruflo__memory_store {
   key: "coordination/parallel-task",
   value: JSON.stringify({
     workers: ["worker-1", "worker-2", "worker-3"],
@@ -153,7 +158,7 @@ mcp__claude-flow__memory_store {
 ### Aggregate Results
 ```javascript
 // Collect all worker results
-mcp__claude-flow__memory_list {
+mcp__ruflo__memory_list {
   namespace: "results"
 }
 ```
@@ -165,37 +170,37 @@ mcp__claude-flow__memory_list {
 FEATURE="user-auth"
 
 # Initialize
-npx claude-flow@v3alpha swarm init --topology hierarchical --max-agents 4
+npx ruflo@latest swarm init --topology hierarchical --max-agents 4
 
 # Spawn workers in parallel
-claude -p "Architect: Design $FEATURE" --session-id ${FEATURE}-arch &
-claude -p "Coder: Implement $FEATURE" --session-id ${FEATURE}-code &
-claude -p "Tester: Test $FEATURE" --session-id ${FEATURE}-test &
-claude -p "Docs: Document $FEATURE" --session-id ${FEATURE}-docs &
+codex exec --sandbox workspace-write --skip-git-repo-check "Architect: Design $FEATURE. Store result as result-${FEATURE}-arch." &
+codex exec --sandbox workspace-write --skip-git-repo-check "Coder: Implement $FEATURE. Store result as result-${FEATURE}-code." &
+codex exec --sandbox workspace-write --skip-git-repo-check "Tester: Test $FEATURE. Store result as result-${FEATURE}-test." &
+codex exec --sandbox workspace-write --skip-git-repo-check "Docs: Document $FEATURE. Store result as result-${FEATURE}-docs." &
 
 # Wait for all
 wait
 
 # Collect results
-npx claude-flow@v3alpha memory list --namespace results
+npx ruflo@latest memory list --namespace results
 ```
 
 ## Best Practices
 
 1. **Size Workers Appropriately**: Each worker should complete in < 5 minutes
-2. **Use Meaningful IDs**: Session IDs should identify the worker's purpose
+2. **Use Meaningful IDs**: result keys should identify the worker's purpose
 3. **Share Context**: Store shared context in memory before spawning
-4. **Budget Limits**: Use `--max-budget-usd` to control costs
+4. **Pick a Sandbox**: `workspace-write` for code changes, `read-only` for audits/reviews
 5. **Error Handling**: Check for partial failures when collecting results
 
 ## Worker Types Reference
 
 | Type | Purpose | Spawn Command |
 |------|---------|---------------|
-| `coder` | Implement code | `claude -p "Implement [feature]"` |
-| `tester` | Write tests | `claude -p "Write tests for [module]"` |
-| `reviewer` | Review code | `claude -p "Review [files]"` |
-| `docs` | Documentation | `claude -p "Document [component]"` |
-| `architect` | Design | `claude -p "Design [system]"` |
+| `coder` | Implement code | `codex exec --sandbox workspace-write --skip-git-repo-check "Implement [feature]"` |
+| `tester` | Write tests | `codex exec --sandbox workspace-write --skip-git-repo-check "Write tests for [module]"` |
+| `reviewer` | Review code | `codex exec --sandbox read-only --skip-git-repo-check "Review [files]"` |
+| `docs` | Documentation | `codex exec --sandbox workspace-write --skip-git-repo-check "Document [component]"` |
+| `architect` | Design | `codex exec --sandbox read-only --skip-git-repo-check "Design [system]"` |
 
 Remember: You coordinate, workers execute. Use memory for all communication between processes.

package/.claude/agents/dual-mode/codex-worker.md

@@ -5,7 +5,13 @@ description: Headless Codex background worker for parallel task execution with s
 
 # Codex Headless Worker
 
-You are a headless Codex worker executing in background mode. You run independently via `claude -p` and coordinate with other workers through shared memory.
+You are a headless Codex worker executing in background mode. You run independently via `codex exec` and coordinate with other workers through shared memory.
+
+> Spawn syntax: `codex exec --sandbox workspace-write --skip-git-repo-check "<prompt>"`.
+> `codex exec` is non-interactive — it runs to completion and prints the agent's final
+> message to stdout. Append `&` to run several workers in parallel. (When the dual-mode
+> orchestrator mixes platforms, *Claude* workers use `claude -p "<prompt>" --output-format text`
+> instead — but a `codex-worker` is always launched with `codex exec`.)
 
 ## Execution Model
 
@@ -23,7 +29,8 @@ You are a headless Codex worker executing in background mode. You run independen
 │   ├─ worker-2 ──┤── Run in parallel            │
 │   └─ worker-3 ──┘                              │
 │                                                 │
-│   Each: claude -p "task" --session-id X &      │
+│   Each: codex exec --sandbox workspace-write   │
+│         --skip-git-repo-check "task" &          │
 └─────────────────────────────────────────────────┘
 ```
 
@@ -39,7 +46,7 @@ You are a headless Codex worker executing in background mode. You run independen
 ### Before Starting Task
 ```javascript
 // 1. Search for relevant patterns
-mcp__claude-flow__memory_search {
+mcp__ruflo__memory_search {
   query: "keywords from task",
   namespace: "patterns",
   limit: 5
@@ -52,7 +59,7 @@ mcp__claude-flow__memory_search {
 ### After Completing Task
 ```javascript
 // 3. Store what worked for future workers
-mcp__claude-flow__memory_store {
+mcp__ruflo__memory_store {
   key: "pattern-[task-type]",
   value: JSON.stringify({
     approach: "what worked",
@@ -63,8 +70,8 @@ mcp__claude-flow__memory_store {
 }
 
 // 4. Store result for coordinator
-mcp__claude-flow__memory_store {
-  key: "result-[session-id]",
+mcp__ruflo__memory_store {
+  key: "result-[worker-id]",
   value: JSON.stringify({
     status: "complete",
     summary: "what was done"
@@ -78,66 +85,66 @@ mcp__claude-flow__memory_store {
 
 ### Basic Worker
 ```bash
-claude -p "
-You are codex-worker.
+codex exec --sandbox workspace-write --skip-git-repo-check "
+You are codex-worker (worker-1).
 TASK: [task description]
 
 1. Search memory for patterns
 2. Execute the task
-3. Store results
-" --session-id worker-1 &
+3. Store results in the 'results' namespace
+" &
 ```
 
-### With Budget Limit
+### Pin a Model
 ```bash
-claude -p "Implement user auth" --max-budget-usd 0.50 --session-id auth-worker &
+codex exec --sandbox workspace-write --skip-git-repo-check -m gpt-5.3-codex "Implement user auth" &
 ```
 
-### With Specific Tools
+### Read-only Worker (no file writes)
 ```bash
-claude -p "Write tests for api.ts" --allowedTools "Read,Write,Bash" --session-id test-worker &
+codex exec --sandbox read-only --skip-git-repo-check "Audit src/api.ts for security issues" &
 ```
 
 ## Worker Types
 
 ### Coder Worker
 ```bash
-claude -p "
+codex exec --sandbox workspace-write --skip-git-repo-check "
 You are a coder worker.
 Implement: [feature]
 Path: src/[module]/
 Store results when complete.
-" --session-id coder-1 &
+" &
 ```
 
 ### Tester Worker
 ```bash
-claude -p "
+codex exec --sandbox workspace-write --skip-git-repo-check "
 You are a tester worker.
 Write tests for: [module]
 Path: tests/
 Run tests and store coverage results.
-" --session-id tester-1 &
+" &
 ```
 
 ### Documenter Worker
 ```bash
-claude -p "
+codex exec --sandbox workspace-write --skip-git-repo-check "
 You are a documentation writer.
 Document: [component]
 Output: docs/
 Store completion status.
-" --session-id docs-1 &
+" &
 ```
 
 ### Reviewer Worker
 ```bash
-claude -p "
+codex exec --sandbox read-only --skip-git-repo-check "
 You are a code reviewer.
 Review: [files]
 Check for: security, performance, best practices
 Store findings in memory.
-" --session-id reviewer-1 &
+" &
 ```
 
 ## MCP Tool Integration
@@ -145,13 +152,13 @@ Store findings in memory.
 ### Available Tools
 ```javascript
 // Search for patterns before starting
-mcp__claude-flow__memory_search {
+mcp__ruflo__memory_search {
   query: "[task keywords]",
   namespace: "patterns"
 }
 
 // Store results and patterns
-mcp__claude-flow__memory_store {
+mcp__ruflo__memory_store {
   key: "[result-key]",
   value: "[json-value]",
   namespace: "results",
@@ -159,25 +166,25 @@ mcp__claude-flow__memory_store {
 }
 
 // Check swarm status (optional)
-mcp__ruv-swarm__swarm_status {
+mcp__ruflo__swarm_status {
   verbose: true
 }
 ```
 
 ## Important Notes
 
-1. **Always Background**: Run with `&` for parallel execution
-2. **Use Session IDs**: Track workers with `--session-id`
-3. **Store Results**: Coordinator needs to collect your output
-4. **Budget Limits**: Use `--max-budget-usd` for cost control
-5. **Upsert Pattern**: Always use `upsert: true` to avoid duplicate key errors
+1. **Always Background**: append `&` so workers run in parallel
+2. **Pick a Sandbox**: `workspace-write` for code changes, `read-only` for audits/reviews
+3. **Store Results**: the coordinator collects your output from the `results` namespace
+4. **Git Check**: `--skip-git-repo-check` lets Codex run outside a git repo
+5. **Upsert Pattern**: always use `upsert: true` to avoid duplicate key errors
 
 ## Best Practices
 
 - Keep tasks focused and small (< 5 minutes each)
 - Search memory before starting to leverage past patterns
 - Store patterns that worked for future workers
-- Use meaningful session IDs for tracking
+- Use a clear worker id in your result keys for tracking
 - Store completion status even on partial success
 
-Remember: You run headlessly in background. The coordinator will collect your results via shared memory.
+Remember: You run headlessly in background. The coordinator collects your results via shared memory.