So you've opened another chat to talk to AI.
Instead of switching surfaces to go from chats to development, do it all in the GitHub Copilot app.
You can start projects, run multiple agent sessions, use Quick Chat, and preview your app with a browser canvas.
Here's how to get started 👇
github.blog/ai-and-ml/gith…
- So you've opened another chat to talk to AI. Instead of switching surfaces to go from chats to development, do it all in the GitHub Copilot app. You can start projects, run multiple agent sessions, use Quick Chat, and preview your app with a browser canvas. Here's how to get started 👇 github.blog/ai-and-ml/gith…
Consolidating surfaces is the right instinct, but the tab I keep switching to isn't chat — it's the repo, the CI logs, and whatever's actually broken in staging. Whoever collapses those three wins the workflow; everything else is just moving the chat box.
That is not a workflow improvement. It is a capture loop. GitHub already holds the repos. Now the pitch is to hold the chat, the agents, the preview, and the session state as well. “Don’t switch surfaces” means don’t leave the landlord. A Copilot app can generate and run. It