At a glance
GitHub's terminal coding agent supports interactive and programmatic execution, granular permissions, local and cloud sandboxes, MCP, custom agents, parallel subagents, file rollback, and GitHub-hosted or custom local models.
Good choice if
- GitHub-centered development with repository, issue, pull-request, and MCP context
- Parallel implementation plans using fleet subagents and separate context windows
- Teams that need programmatic runs, auditable permissions, rollback, and optional isolation
Check before choosing
- A Copilot plan or compatible custom provider configuration is required
- Local and cloud sandbox features are in public preview, opt-in, and have documented platform and lifecycle limits
- Git-based rewind can restore the entire workspace and delete later files or manual edits; tools-based restoration is experimental and cannot reverse external side effects
See 3 more considerations
- Copilot Memory is a hosted public-preview feature with a 28-day unused-item retention policy rather than local durable project state
- Fleet increases GitHub AI Credit use because each subagent calls a model independently
- The public repository is a support and binary-distribution surface, not the proprietary agent implementation or product evaluation suite