[Archived PR] feat: add profile-level native autopilot mode (opt-in)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- ai, cli, documentation, full-stack
Research direction
This work is already represented by an archived PR, so first verify whether it is still wanted before starting. If it is reopened, read the profile/request schema flow, multi-turn-loop, queue-processor, buildCopilotBaseArgs, and writeVSCodeSettings; run pnpm -r build and pnpm test. Done means the opt-in setting remains off by default and the documented CLI, portal, API, and worker behavior is covered.
Written by the indexing model from the issue text.
Description
Original author: @sinedied
Summary
Adds an optional, versioned autopilot flag to code agent profiles that runs the configured coding agent in its native autopilot mode — fully autonomous, never pausing to ask the user clarifying/decision questions. Placement is profile-only (a reproducible sibling of reasoningEffort), not a per-request override.
Uses each agent's native mechanism — never prompt injection.
Opt-in / backward-compatible
Autopilot defaults to OFF. An unset autopilot reproduces exact pre-PR behavior; only an explicit true enables it (autopilot === true idiom throughout the stack). This keeps existing workflows unchanged.
Per-worker native mapping
| Worker | Mechanism |
|---|---|
| Copilot / Copilot-Windows | native --autopilot startup flag (when enabled) |
| VS Code Web | chat.autopilot.enabled in per-run settings |
| Claude Code | no native toggle (capability gap) — autonomous in headless ACP regardless; logged only when explicitly requested |
Important: permissions vs. HITL
The Copilot ACP selectPermissionMode(#autopilot) call remains unconditional. It is a headless-execution/permissions concern (an ACP session starts in agent mode where bash/build calls are denied non-interactively), not a HITL toggle. Gating it would break command execution — so it stays independent of the profile setting; only the native --autopilot startup flag is gated.
Changes
- shared:
autopilot?: booleanonProfileVersionDocument,RequestDocument,WorkerProcessorOptions; Zod schemas (profile create/response, request response — profile-only, not in create input); threaded throughmulti-turn-loopandqueue-processor. - API:
effectiveAutopilotresolution (default false), stored on request docs; rerun fallback. - workers: shared
buildCopilotBaseArgshelper (Copilot + Windows); VS Code WebwriteVSCodeSettings(autopilot = false); Claude Code capability-gap logging. - CLI: profile create/version
--autopilot/--no-autopilot; display + help ("Default: off"). - Portal: profile create/version forms (Switch, default off), profile detail/preview display,
Run+ profile-input types (closes an API type-consistency gap). - docs:
app-design.md,worker-requirements.md,vscode-web-worker.md,worker-compliance.md.
Testing
pnpm -r build— clean.pnpm test— 2445 passed (addedbuildCopilotBaseArgstests; VS Code default-settings test now expectsfalse).- OpenAPI + CLI snapshots unchanged (schema/flag names identical; only resolution semantics and help text changed).
Co-authored-by: Copilot App [email protected]
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 5
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 15
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/scope
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
author: JaGord documentation good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
author: cedricvidal bug portal
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openedx/frontend-app-authoring#3274 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/documentation status/need-triage
Difficulty 1/5 Under an hour Newbie friendliness 95/100
google-gemini/gemini-cli#29548 ·
Maintainers usually reply within 1 day
-
sdk-typescript vector-store
Difficulty 2/5 Half a day Newbie friendliness 82/100
mem0ai/mem0#7495 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day