Git Tools

Spoiler: GitHub finally shipped the autonomous-PR product they teased two years ago. Copilot Workspaces is GA, lives inside the GitHub UI, and turns a labelled issue into a plan, then code, then a PR.

The Setup

Open any issue, click "Open in Workspace", and Copilot proposes a plan you can edit before it writes a line of code. The plan is just markdown — it's the bit that makes the whole loop actually work, because you fix the misunderstanding before the agent commits anything.

# nothing to install, it's in the GitHub UI
# enable per-repo:
gh api -X PUT /repos/:owner/:repo/copilot/workspaces \
  -f enabled=true

The Money Pattern

Behold a workspace plan for a typical Pipedrive integration ticket — this is what Workspaces hands you before it touches the repo:

## Plan: Add Pipedrive deal sync to /api/leads

### Files to change
- src/lib/pipedrive.ts (new): wrap Pipedrive Deals API with typed client
- src/pages/api/leads.ts: POST handler calls pipedrive.deals.create
- src/types/pipedrive.ts (new): shared deal shape (zod)

### Steps
1. Add PIPEDRIVE_API_TOKEN to env schema
2. Implement createDeal() with retry + timeout
3. Wire into /api/leads after Supabase insert
4. Add integration test mocking the Pipedrive endpoint

Edit the plan, hit go, get a PR. The model behind it loops over your repo's CI feedback and self-corrects up to three times before asking for help.

The Catch

It still loops on big repos. Anything over ~50k files and the planning phase takes minutes, sometimes times out entirely. It's also GitHub-only — no GitLab, no Gitea, no Codeberg. And it can't see your private package registries unless you wire them up explicitly.

The Verdict

For a smallish Astro/Next repo with good CI, Workspaces is genuinely useful for tickets-shaped work. For deep refactors, Claude Code in a terminal still wins. Use Workspaces for the boring stuff and your agent budget for the actual thinking. Both tools, both jobs.