Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/autopilot:autopilot-stopThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /autopilot-stop Gracefully stop a running autopilot session. ## What to do 1. Check `.autopilot/loop.pid` exists and process is running. 2. Create `.autopilot/STOP` signal file (the loop script checks for this). 3. Wait up to 30 seconds for the current iteration to finish: 4. If user passes `--force`, kill the process directly: 5. Show final status using the same dashboard as `/autopilot-status`. 6. Update `mission.json` status to "stopped".
Gracefully stop a running autopilot session.
Check .autopilot/loop.pid exists and process is running.
Create .autopilot/STOP signal file (the loop script checks for this).
Wait up to 30 seconds for the current iteration to finish:
touch .autopilot/STOP
echo "Stop signal sent. Waiting for current iteration to finish..."
If user passes --force, kill the process directly:
kill $(cat .autopilot/loop.pid) 2>/dev/null
Show final status using the same dashboard as /autopilot-status.
Update mission.json status to "stopped".
npx claudepluginhub george11642/george-plugins --plugin autopilot/stopCompletes the current task before stopping autorun mode, providing a graceful session halt unlike immediate emergency stops.
/cancel-loopStops the active research loop by deleting _autonomous/loop.state.md and killing the autorun tmux session. Confirms cancellation or reports no active loop.