القائمة
Run an autonomous /loop iteration -- check progress, work on next task, schedule next wake
| name | autopilot-loop |
| description | Run an autonomous /loop iteration -- check progress, work on next task, schedule next wake |
| 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 ScheduleWakeup Agent |
Run one autopilot iteration using Claude Code's native /loop:
mcp__claude-flow__autopilot_statusmcp__claude-flow__autopilot_disable and stopmcp__claude-flow__autopilot_predict for the optimal next actionmcp__claude-flow__autopilot_logScheduleWakeup({ delaySeconds: 270, reason: "next autopilot iteration" })Always use delay 270s (under 300s cache TTL) to keep the prompt cache warm between iterations.
Autopilot discovers tasks from:
Configure: mcp__claude-flow__autopilot_config({ taskSources: ["team-tasks", "swarm-tasks"] })
Spawn nested sub-agents (agents that spawn sub-agents, up to depth=5) via Claude Code's native Task tool — for context-managed deep delegation
Author a workflow — either an MCP workflow template (persisted, lifecycle) or a native .claude/workflows/*.js orchestration script (agent/parallel/pipeline fan-out)
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix
Walk through a complete GAIA benchmark→submit flow — from key resolution through HAL-compatible package generation