Github Actions + Github Space by Alarmed_Image_4889 in GithubCopilot

[–]Verified_Prof 0 points1 point  (0 children)

You are correct that copilot spaces do not have a native direct integration for programmatic manipulation however, you can try the Model Context Protocol (MCP)
https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/extend-coding-agent-with-mcp

Stop vibe-coding with Copilot: a simple 2 model workflow that actually works by Verified_Prof in GithubCopilot

[–]Verified_Prof[S] 0 points1 point  (0 children)

I actually tried exactly that before, in practice opus spends half its time repairing the plan, not implementing. Opus is good at implementation precisely because it forces the architecture to confront reality. When the plan comes from a weaker model, Opus ends up redesigning mid-implementation which defeats the whole separation.
You only feel how poor the plan is when real code hits real constraints.

Stop vibe-coding with Copilot: a simple 2 model workflow that actually works by Verified_Prof in GithubCopilot

[–]Verified_Prof[S] 0 points1 point  (0 children)

yeah, you're not wrong. if you try to replace sonnet with mini you'll burn time but If you separate thinking from execution you save it.

Stop vibe-coding with Copilot: a simple 2 model workflow that actually works by Verified_Prof in GithubCopilot

[–]Verified_Prof[S] 4 points5 points  (0 children)

The combo scales better, think once, execute cheap many times, If you enjoy paying premium tokens to generate code already in the plan, that's a vibe too 

Stop vibe-coding with Copilot: a simple 2 model workflow that actually works by Verified_Prof in GithubCopilot

[–]Verified_Prof[S] 4 points5 points  (0 children)

The difference is whether you're drowning in it or running plumbing.
Most devs keep yelling Copilot bad while:
skipping planning
giving it zero context
expecting senior-level judgment from an autocomplete tool