
What happened
GitHub introduced the Copilot app, a workspace that organizes AI coding work around projects and sessions. Instead of a single chat window, it lets developers run multiple agent sessions tied to a repository, use Quick Chat for side tasks, preview changes in a browser canvas, and employ Agent Merge to help manage pull requests through review and CI processes.
Why it matters
Real development work jumps between bug fixes, code review, and exploring new parts of a codebase—activities a single chat interface handles poorly. By connecting AI sessions to projects and allowing developers to switch between tasks without losing their place, the Copilot app lets teams spend less time setting up their environment and more time building. The canvas preview and Agent Merge features close the loop from code change to merge, reducing friction in the full development cycle.
What to watch
The Copilot app is available now; developers can start by selecting a project from GitHub or their local machine and creating their first agent session. GitHub encourages trying it on backlog tasks to see how it streamlines exploration, building, and shipping with AI agents.
Summaries like this, in your inbox every morning.
The GitHub Copilot app represents a shift in how AI coding tools integrate with a developer's actual workflow. Traditional AI coding assistants treat interaction as a single linear conversation—the user asks a question, the AI answers, and the context resets. But the body describes a different reality: developers spend their day jumping between activities (fixing bugs, reviewing code, exploring unfamiliar parts of a codebase, trying new ideas). By anchoring each AI session to a project and allowing multiple parallel sessions, the Copilot app avoids the friction of re-explaining context every time a developer switches tasks.
The addition of the canvas—an embedded browser preview with direct element selection—bridges a gap that chat-only tools leave open: the gap between what code says it should do and what the UI actually shows. The Pick & Polish feature lets a developer point at a specific visual problem and use that as context for the next request, collapsing the cycle time from "ask AI to change component" to "see result, refine it, repeat." Similarly, Agent Merge extends the workflow beyond the initial code change by automating routine pull request chores (addressing review feedback, resolving CI failures, handling merge conflicts), reducing manual context-switching during the review phase.
Taken together, these features suggest the maturation of AI coding from a novelty chat interface to a tool that mirrors the actual shape of development work—sequential tasks, parallel threads, visual feedback loops, and collaborative review. The body frames this as a "workspace" rather than a chat, a distinction that signals a deeper integration into the development cycle rather than a separate assistance layer.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
ElevenLabs completed a $300 million employee tender at a $22 billion valuation, and co-founder Mati Staniszews…

On October 15, OpenAI announced the Rosalind Academic Plan, giving approved US university labs free access to…

A Qiita article compared automated red-teaming methods for LLM apps — GCG, PAIR, and TAP — using mock implemen…

Liquid AI released d1-ultra on October 15, 2026, an upgraded open-weights decision model that averaged 76.7 ac…

Circlia started a proof-of-concept for TASTE SIGNAL: visitors to Holland Village Cafe FUKUOKA taste cookies an…

In a webinar hosted by French Mathematical Society president Isabelle Gallagher, Fields Medal winner Hugo Dumi…
