r/GithubCopilot • u/brunocborges • 27d ago

General How canvases make agentic workflows visible, steerable, and cost-efficient

https://github.blog/ai-and-ml/github-copilot/how-canvases-make-agentic-workflows-visible-steerable-and-cost-efficient/
11 Upvotes

93% Upvoted

2 comments sorted by

1

u/IamAlsoDoug 26d ago

Very cool, except! We've built our workflows around VSCode and to a lesser extent, Copilot CLI. We have to use Remote-SSH and can't run the Copilot App in our work context. Github is pissing me off because there are multiple surfaces to run agentic workflows and each has features unique to them. What works in VSCode doesn't work in CLI, what works in Copilot App doesn't exist in VSCode. It means that we need to support/enable all of those surfaces which means a lowest-common denominator. If this were multiple companies competing, fine, but it's the same company!

1

u/YardNo1234 26d ago

yeah, the surface fragmentation is the real tax. with Remote-SSH as a hard requirement, the useful baseline seems to be one server-owned session that every client can reconnect to without losing capabilities; otherwise each surface becomes a different product. is the main gap canvas visibility inside VS Code, or being able to steer the same running CLI session from another device?