Comparison

Fleet vs. GitHub Copilot Coding Agent: Self-Hosted Multi-Agent Orchestration vs. GitHub Cloud Agent

Name: Fleet
Author: Fleet

GitHub's Copilot Workspace technical preview was sunset on May 30, 2025 and folded into the Copilot coding agent, now generally available — a cloud-hosted agent that turns issues into pull requests. Fleet is a self-hosted orchestration layer that coordinates a full roster of role-based Claude Code agents — dev, reviewer, release manager — with governance and no vendor lock-in.

GitHub's Copilot coding agent (which absorbed the discontinued Copilot Workspace technical preview in 2025) lets you assign a GitHub issue and have an AI agent plan and implement a solution, producing a pull request. It is tightly integrated with GitHub's infrastructure and requires no local setup. For teams already on GitHub, the zero-friction path is appealing.

Fleet covers a broader surface. It runs on your own machine or server, coordinates multiple Claude Code agents with different roles, and handles the full chain from issue triage through development, code review, and merge. Where the Copilot coding agent hands you a PR to review, Fleet can automatically route that PR to a reviewer agent and then to a release manager agent.

Choose Fleet if

Teams that want a full autonomous pipeline — issue to merge — with self-hosted infrastructure, role-based agent coordination, and governance controls.

Choose Copilot Workspace if

Teams on GitHub who want a zero-setup cloud agent that converts issues to pull requests without leaving the GitHub UI.

Fleet vs. Copilot Workspace: side by side

Feature	Fleet	Copilot Workspace
Deployment	Self-hosted binary on your machine or server	GitHub cloud service, no local install
Pipeline scope	Issue -> dev -> reviewer -> release manager	Issue -> pull request
Agent runner	Runs Claude Code as the agent runner	GitHub-managed Copilot models
Code review automation	Dedicated reviewer agent with fabric handoff	Not automated — human reviews the PR
Merge automation	Release manager agent with approval gate	Manual merge after human review
Data residency	Self-hosted; your source code goes only to your model backend (Bedrock/Vertex in your own cloud) + GitHub	Processed on GitHub/Microsoft cloud
Budget controls	Per-agent run-time budgets; 6-dim evaluation + auto-quarantine risk model	Not exposed to operators
Org-level governance	org.yaml, approval gates, audit log	GitHub org settings and CODEOWNERS

Where Fleet is the better fit

End-to-end automation: Fleet's reactive chain takes a ticket from ready to merged without human intervention at each handoff
Self-hosted — no code transmitted to GitHub/Microsoft servers beyond normal git operations
Role-based agent roster with per-agent run-time budgets and approval gates governs the pipeline
Auto-quarantine driven by a separate risk model catches anomalous agent behavior before it reaches production

Where Copilot Workspace is the better fit

Zero installation — works entirely in the GitHub browser UI with no binary or config files to manage
Native integration with GitHub Issues, PRs, and Actions makes the handoff from planning to code seamless
Strong for one-shot implementations of well-defined issues without maintaining any local infrastructure
Backed by Microsoft/GitHub with significant model tuning on code generation tasks

Pricing

The Copilot coding agent is available through GitHub Copilot plans (note: the standalone Copilot Workspace technical preview was discontinued on May 30, 2025). Fleet Team is $49/agent slot/month. For a 5-role fleet (PM, dev, reviewer, QA, release manager), that is $245/month plus model API costs.

Do they compete, or coexist?

Complementary at different scales. The Copilot coding agent handles quick single-issue implementations inside GitHub. Fleet handles the multi-agent coordination around larger features, with its watcher watching for GitHub label changes and dispatching the right agent automatically.

Frequently asked questions

Is Copilot Workspace still available?

No. GitHub sunset the Copilot Workspace technical preview on May 30, 2025 and folded its capabilities into the Copilot coding agent, which is now generally available. This page compares Fleet to that coding agent.

Is Fleet a replacement for the Copilot coding agent?

For teams that want the full issue-to-merge pipeline automated with self-hosted infrastructure and role-based agents, yes. For teams that just want occasional one-shot implementations inside GitHub.com with no setup, the Copilot coding agent is simpler.

More comparisons

Fleet vs. GitHub Copilot →Fleet vs. Devin →Fleet vs. Google Jules →

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet