Summary
There is currently no way to make autopilot mode persist across multiple interactive turns when started from the command line. The --autopilot flag (and --mode autopilot) only sets the initial mode — after the first task completes, the session falls back to the standard interactive mode. The only sticky mechanism is the in-session Shift+Tab toggle, which is manual and cannot be set at launch.
Current behavior
--autopilot → help text: "Start in autopilot mode" (initial only)--mode <mode> → help text: "Set the initial agent mode" (initial only)- No
settings.json key exists to set a persistent default mode (keys like model, keepAlive, continueOnAutoMode, stream exist; none for agent mode).
- Result: launching via an alias such as
copilot --yolo --autopilot ... runs autopilot for the first turn, then reverts to normal mode for every subsequent turn. The user must press Shift+Tab again each time (or rely on it) to stay in autopilot.
Expected / desired behavior
A way to make autopilot persist across interactive turns without manual Shift+Tab each turn. Either:
- A persistent setting, e.g.
settings.json "defaultMode": "autopilot", or
- A launch flag that makes
--mode autopilot sticky for the whole interactive session (not just the initial turn).
Use case
Users who wrap the CLI in a shell alias for a consistently hands-off local workflow (full permissions + autopilot) want every turn in the session to run in autopilot, configured once at launch, rather than re-toggling Shift+Tab after each completed task.
Environment
- Copilot CLI v1.0.66-2
- macOS (Darwin), zsh launcher function
Workarounds today
- Programmatic single-shot:
copilot --autopilot --yolo --max-autopilot-continues N -p "PROMPT" (non-interactive, one prompt).
- Interactive: launch with
--yolo, then press Shift+Tab once (sticky for the session, but manual).
Summary
There is currently no way to make autopilot mode persist across multiple interactive turns when started from the command line. The
--autopilotflag (and--mode autopilot) only sets the initial mode — after the first task completes, the session falls back to the standard interactive mode. The only sticky mechanism is the in-session Shift+Tab toggle, which is manual and cannot be set at launch.Current behavior
--autopilot→ help text: "Start in autopilot mode" (initial only)--mode <mode>→ help text: "Set the initial agent mode" (initial only)settings.jsonkey exists to set a persistent default mode (keys likemodel,keepAlive,continueOnAutoMode,streamexist; none for agent mode).copilot --yolo --autopilot ...runs autopilot for the first turn, then reverts to normal mode for every subsequent turn. The user must press Shift+Tab again each time (or rely on it) to stay in autopilot.Expected / desired behavior
A way to make autopilot persist across interactive turns without manual Shift+Tab each turn. Either:
settings.json"defaultMode": "autopilot", or--mode autopilotsticky for the whole interactive session (not just the initial turn).Use case
Users who wrap the CLI in a shell alias for a consistently hands-off local workflow (full permissions + autopilot) want every turn in the session to run in autopilot, configured once at launch, rather than re-toggling Shift+Tab after each completed task.
Environment
Workarounds today
copilot --autopilot --yolo --max-autopilot-continues N -p "PROMPT"(non-interactive, one prompt).--yolo, then press Shift+Tab once (sticky for the session, but manual).