Run one cycle of autonomous task work in Claude Code: check progress, select and execute the next action, log the work, and schedule another cycle. Stop when all tasks are complete or the iteration limit is reached.
Run an autonomous /loop iteration -- check progress, work on next task, schedule next wake
Review the instructions the agent will receive before you install.
Run one autopilot iteration using Claude Code's native /loop:
mcp__plugin_ruflo-core_ruflo__autopilot_statusmcp__plugin_ruflo-core_ruflo__autopilot_disable and stopmcp__plugin_ruflo-core_ruflo__autopilot_predict for the optimal next actionmcp__plugin_ruflo-core_ruflo__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__plugin_ruflo-core_ruflo__autopilot_config({ taskSources: ["team-tasks", "swarm-tasks"] })
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.