For Microsoft's GitHub Copilot
Stuck in GitHub Copilot? Press the dot.
Copilot lives inside the IDE. The press is for the moments Copilot isn't enough on its own.
When GitHub Copilot needs a person.
01
When Copilot's suggestions stop being useful
Mid-refactor, in unfamiliar code, against a non-mainstream framework — Copilot's prediction quality drops. The press surfaces an engineer who knows the framework.
02
When the PR review needs a real reviewer
Copilot Workspace is excellent for first-draft review. For PRs where one wrong merge costs a week, a software engineer joins and reviews live.
03
When the build is enterprise-shaped
Copilot in an enterprise context — SSO, code policies, compliance — has a different shape. A Relay engineer who's stood it up before walks the team through the rollout.
Common questions
- Do you support Copilot Workspace?
- Yes. PR-level review, plan generation, and the agent-driven changes — engineers are familiar with the surface.
- What about Copilot Chat?
- Yes. The engineer can pair with you inside VS Code, Visual Studio, or JetBrains — wherever Copilot Chat lives.
- Does Copilot's enterprise plan integrate?
- We don't integrate at the API level — we integrate at the human level. Engineers join your screen, regardless of the plan you're on.
Related reading
- Field notes · 9 min readAnatomy of the handoff: what we learned shipping the first 1,000 sessionsA median match in seconds isn’t a marketing number; it’s a system constraint we engineered toward and missed by 16 seconds in the first month.
- Research · 17 min readWhen does an AI build want a person? A study of 4,200 stuck momentsWe logged every press in the first quarter of the private beta. Four patterns explain almost everything.
- Essay · 11 min readThe irreducibly human moment in softwareAn argument for why software engineering doesn’t shrink in the age of AI, it sharpens, and moves to a new place in the build.
Press the dot.
A senior Relay engineer joins your GitHub Copilot session in seconds.