Menu
Observe Ruflo swarm status from Codex with bounded checks
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run one Codex-managed autopilot iteration using Ruflo MCP or CLI state
Use learned patterns and current state to predict the optimal next Codex action
Discover and recommend ruflo plugins based on your workflow, installed MCP tools, and current task
Initialize a new Ruflo project with MCP tools, hooks, and agent configuration
Initialize a Ruflo swarm and coordinate Codex-native follow-up work
Create a new sequentially numbered database migration with up/down SQL files
| name | monitor-stream |
| description | Observe Ruflo swarm status from Codex with bounded checks |
| argument-hint | |
| allowed-tools | Bash(npx *) mcp__claude-flow__swarm_status mcp__claude-flow__swarm_health |
Observe swarm state from Codex. Codex does not expose Claude Code's Monitor tool, so prefer bounded status checks over indefinite streams.
For one-shot status, use MCP: mcp__claude-flow__swarm_status or mcp__claude-flow__swarm_health.
For CLI status:
npx @claude-flow/cli@latest swarm status
npx @claude-flow/cli@latest swarm health
If the user explicitly asks for a live stream, run the stream as a bounded shell command with an explicit timeout or stop condition:
npx @claude-flow/cli@latest swarm watch --stream
Do not assume line-by-line stream notifications are delivered to Codex automatically. Summarize observed events after the command returns or when the timeout is reached.