agentleFS
jmylchreestjmylchreest/aide/skills/autopilot/SKILL.md

autopilot

Skill19 starsChanged 3 months agoMITView on GitHub

Full autonomous execution - keeps working until all tasks are verified complete

74 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-bugbot, rename-chat and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 3 projects that use this

  • 0mlkrizzz655335vSkill

    rename-chat

    重命名当前聊天。按聊天内容改标题。"disable-model-invocation: true

    Also in 3 projects that use this

  • Tsumugii24Skill

    split-to-prs

    Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

    Also in 4 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 3 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 3 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 3 projects that use this

  • +1 more from 32103210
  • +1 more from 0mlkrizzz655335v

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 66 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When autopilot mode is active:

    line 37
  2. Distinctive:

    If incomplete tasks exist in the todo list, the agent is re-prompted to continue

    line 40
  3. Distinctive:

    When autopilot mode is activated:

    line 101

“Common” is measured: kept by at least 6 in 10 of the 66 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Autopilot Mode

Recommended model tier: smart (opus) - this mode handles complex multi-step tasks

Full autonomous execution mode. The agent keeps working until all tasks in the todo list are verified complete. No stopping early, no partial results.

Activation

Type naturally:

autopilot build me a web app
autopilot fix all failing tests
autopilot refactor the auth module

Or explicitly set the mode:

aide state set mode autopilot

How It Works

When autopilot mode is active:

  1. The persistence hook intercepts stop signals
  2. If incomplete tasks exist in the todo list, the agent is re-prompted to continue
  3. The agent keeps working through its task list
  4. Auto-releases when ALL tasks are complete (terminal state)
  5. Safety cap: releases after 20 iterations even if tasks remain

Platform Behavior

PlatformMechanism
Claude CodeStop-blocking — prevents the AI from ending the conversation early
OpenCodeRe-prompting — session.prompt() is called on idle to keep going

Task Tracking

Autopilot relies on the todo list to determine completeness:

  • Has incomplete tasks → Block stop, continue working
  • All tasks complete → Auto-release, allow stop
  • No tasks exist → Generic reinforcement (verify your work)

When to Use

Autopilot mode is ideal for:

  • Multi-step implementations — "autopilot implement the user dashboard"
  • Fixing all test failures — "autopilot fix all failing tests"
  • Complete refactors — "autopilot refactor all error handling to use Result types"
  • Migration tasks — "autopilot migrate all components to the new API"
  • Build fixes — "autopilot make the build pass"

When NOT to Use

Avoid autopilot for:

  • Exploratory tasks — "investigate why X happens" (no clear completion criteria)
  • Design work — Use the design skill instead (needs human input)
  • Tasks requiring human judgment — Autopilot continues based on automated checks
  • Parallel work — Use swarm mode instead for decomposed parallel stories

Combining with Skills

Autopilot works well with any skill:

autopilot fix the build errors       # autopilot + build-fix behavior
autopilot make all tests pass        # autopilot + implement behavior
autopilot debug why login fails      # autopilot + debug behavior

Deactivation

To stop autopilot mode early:

aide state set mode ""

Or type "stop" — the keyword detector clears the active mode.

Instructions

When autopilot mode is activated:

  1. Create a comprehensive todo list — Break the task into specific, actionable items
  2. Work through items sequentially — Mark each as in_progress then completed
  3. Verify each step — Run tests, check builds, confirm behavior
  4. Do not stop until all items are complete — The persistence hook will block premature stops
  5. If stuck on an item after 3 attempts, record a blocker memory and move to the next item:
    ./.aide/bin/aide memory add --category=blocker --tags=project:<name>,session:<id>,source:discovered "Blocked on <task>: <reason>"

Binary location: The aide binary is at .aide/bin/aide. If it's on your $PATH, you can use aide directly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.