← Journal
10 min readAI Dev Review

GitHub Copilot Workspace: an honest six-month review

Workspace promised an end-to-end agent inside GitHub. Half a year in, here's what's living up to the pitch.

ReviewsGitHub CopilotAgents

Copilot Workspace shipped to general availability with an ambitious pitch: take an issue, produce a PR, no IDE required. Six months of using it on real work has produced a clear picture of what it does well and where it still falls short.

What works

Workspace shines on small, well-scoped issues with clear acceptance criteria. The spec-to-plan-to-diff loop matches how good engineers already think, and the GitHub-native UI removes a lot of friction.

Reviewing a Workspace-generated PR feels close to reviewing a junior's PR — which is much better than most agent output a year ago.

What still doesn't

  • Large issues without clear scope produce sprawling, low-quality plans.
  • Repos with unusual build setups confuse it more than they should.
  • Iteration speed inside the Workspace UI lags behind a local editor.

Best workflow we've found

Treat Workspace as a first-pass drafter for tickets you've already written carefully. Generate the plan in Workspace, then either accept the PR or pull the branch locally and finish it in your editor of choice.

This hybrid is faster than either tool alone for a meaningful chunk of work.

Pricing reality

Workspace is bundled with Copilot Enterprise, which makes the marginal cost effectively zero if you're already paying. Standalone, the math is harder to justify against equally-capable agents.

Verdict

Genuinely useful, particularly for teams already on Copilot Enterprise. Not the only agent you'd want in your toolkit, but a comfortable second seat.

Comments

0 replies

Join the conversation

Sign in to leave a comment on "GitHub Copilot Workspace: an honest six-month review".

Loading comments…