Menu
Run one Codex-managed autopilot iteration using Ruflo MCP or CLI state
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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
Observe Ruflo swarm status from Codex with bounded checks
Initialize a Ruflo swarm and coordinate Codex-native follow-up work
Create a new sequentially numbered database migration with up/down SQL files
| name | autopilot-loop |
| description | Run one Codex-managed autopilot iteration using Ruflo MCP or CLI state |
| argument-hint | |
| allowed-tools | mcp__claude-flow__autopilot_status mcp__claude-flow__autopilot_predict mcp__claude-flow__autopilot_log mcp__claude-flow__autopilot_progress mcp__claude-flow__autopilot_disable |
Run one autopilot iteration under Codex control. Codex does not provide Claude Code persistent-loop or wakeup primitives; treat this skill as a single iteration that the current Codex session executes immediately.
mcp__claude-flow__autopilot_status.mcp__claude-flow__autopilot_disable and stop.mcp__claude-flow__autopilot_predict for the recommended next action.mcp__claude-flow__autopilot_log and check mcp__claude-flow__autopilot_progress.There is no native persistent wakeup primitive in Codex. For long-running or periodic loops, use an explicit external scheduler, a shell script, or a user-requested follow-up session.
Prefer Ruflo/MCP-backed sources that Codex can access:
Avoid Claude Code-only task sources unless the user is explicitly running this skill inside Claude Code.