Copilot
Switch Claude Code from autonomous agent behavior to human-led copilot mode with relaxed worktree and main-branch rules for paired sessions.
Overview
Copilot is an agent skill most often used in Build (also Operate iterate, Ship review) that switches Claude Code into human-led copilot mode with relaxed worktree and main-branch rules via the shared mode controller.
Install
npx skills add https://github.com/camacho/ai-skills --skill copilotWhat is this skill?
- Sets shared mode to copilot via set-mode.sh (alias of the autonomous skill controller)
- Relaxes worktree requirement and main-branch protection for human-driven sessions
- Claude Code enforcement only; Codex and Cursor stay autonomous unless an adapter uses this controller
- Sliding 4h TTL with 12h absolute ceiling; reverts with /autonomous when the task or plan completes
- Prints confirmation block and follows .claude/rules/operating-mode.md copilot rules
- Copilot mode TTL: 4h sliding renewal per prompt with a 12h absolute ceiling
- Relaxes two enforcement areas: worktree requirement and main branch protection
Adoption & trust: 546 installs on skills.sh; 1 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want the agent to pair with you on main without autonomous worktree enforcement blocking every commit.
Who is it for?
Solo builders on Claude Code who want human-in-the-loop coding on the main branch for a bounded session.
Skip if: Teams that require strict worktree isolation on every change, or users on Codex/Cursor expecting this skill to change default agent behavior without a mode adapter.
When should I use this skill?
User invokes /copilot or asks to enter copilot mode so the human drives and Claude assists with relaxed worktree and main commits.
What do I get? / Deliverables
Mode is set to copilot with documented TTL and operating rules, and you revert to autonomous mode when the current task or plan completes.
- Active copilot mode setting
- Printed mode confirmation (TTL and relaxed rules)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is build/agent-tooling because the skill configures how the coding agent operates during active implementation work. It is an operating-mode controller for the agent runtime (TTL, worktree rules, menu workflow), not a product feature or deployment step.
Where it fits
You spike a feature on main while keeping TTL-bounded copilot rules instead of a long autonomous worktree run.
You walk the agent through review fixes commit-by-commit with you approving each step.
You hotfix production behavior in a short session and want relaxed branch rules until the fix ships.
How it compares
Use for explicit human-led sessions instead of leaving autonomous mode on and fighting worktree rules in chat.
Common Questions / FAQ
Who is copilot for?
Claude Code users in repos that ship the camacho/ai-env autonomous controller scripts and want a short, human-driven pairing mode.
When should I use copilot?
During build implementation when you want menu-style control; during ship review when you commit on main with guardrails relaxed; during operate iterate when you tweak production fixes side-by-side with the agent.
Is copilot safe to install?
It relaxes branch and worktree protections by design—review the Security Audits panel on this page and only enable copilot in repos where main commits are acceptable for your workflow.
SKILL.md
READMESKILL.md - Copilot
# Enter Copilot Mode > **Claude Code enforcement only** — Codex and Cursor default to autonomous unless a future adapter uses this shared controller. > Alias for setting `mode=copilot` through the shared mode controller. ## Shared Controller Mode is a setting with explicit values: `autonomous` and `copilot`. This skill is an alias over the controller currently owned by `/autonomous`; keep behavior in one place unless this repo grows a neutral `/mode` skill later. ## Activate ```bash REPO_ROOT="$(git rev-parse --show-toplevel)" "$REPO_ROOT/.agents/skills/autonomous/scripts/set-mode.sh" copilot ``` If the script does not exist, tell the user: "This project doesn't have mode switching scripts. Install the ai-env template or add set-mode.sh manually." If it fails for another reason, inform the user with the error message and stop. ## Confirmation After activation, print: ``` Mode: copilot Relaxed: worktree requirement, main branch protection Workflow: menu mode — tell me to follow it or just lead TTL: 4h sliding (renews on each prompt) / 12h absolute ceiling ``` ## Behavior Follow **copilot mode** rules in `.claude/rules/operating-mode.md`. When the current task or plan completes, revert with `/autonomous`.