GitHub Wants to Be Everything
GitHub Universe 2025 happened and the message from Microsoft's favourite acquisition is crystal clear: GitHub does not want to just host your code anymore. It wants to write it, review it, deploy it, and eventually think for you. Let's talk about what they announced and whether any of it actually matters. Copilot Workspace Is the Big Bet Copilot Workspace went general availability this year after a long preview period and it is genuinely impressive. The pitch: open an issue, Copilot reads the issue, reads your codebase, proposes a plan with specific file changes, and implements the plan. You review and merge. In practice, it works surprisingly well for straightforward feature requests and bug fixes. We tested it on a real project — filed an issue to add pagination to an API endpoint — and Copilot Workspace produced a working implementation across three files in under two minutes. The code was not perfect but it was a solid 80% solution that needed minor tweaks. The limitations are obvious though. Complex architectural changes, multi-service features, and anything requiring deep domain knowledge still produce plans that miss the mark. It is an incredible tool for the kind of work that was already easy — and that is not nothing. A huge percentage of development time is spent on mechanical, well-understood changes. Automating that is valuable. GitHub Spark Is Wild Spark is GitHub's "natural language to full application" tool and honestly it is the most interesting announcement. You describe an app in plain English — "build me a habit tracker with streak counting and a calendar view" — and Spark generates a full, deployable application. Not a mockup. Not a prototype. A working app with a database, API, and frontend. The generated apps are obviously simple and the code quality is what you would expect from a code generator. But the speed is remarkable. In demos, GitHub showed complete CRUD applications going from idea to deployed URL in under five minutes. For internal tools, prototypes, and proof-of-concepts, this eliminates days of boilerplate work. Copilot Got Multi-Model The Copilot chat and code completion features now support multiple models — GPT-4o, Claude 3.5 Sonnet, and Gemini Pro. You can switch between models mid-conversation. This is smart strategy from GitHub. Rather than betting everything on OpenAI, they are becoming the interface layer that lets you use whichever model is best for your task. Claude for nuanced code review. GPT-4o for quick completions. Gemini for large context analysis. The model wars benefit GitHub regardless of who wins. Is GitHub Becoming an IDE? Sort of. github.dev already gives you a VS Code instance in the browser. Codespaces gives you a full cloud development environment. Copilot Workspace lets you develop without leaving the browser at all. Add Spark for app generation and you have a platform that can take you from idea to deployed application without ever opening a local editor. For professional developers, this is complementary rather than a replacement. You are still going to use your local setup for serious work. But for quick fixes, code reviews, and prototyping, the browser-based workflow is getting surprisingly good. The Lock-in Question Here is the part nobody talks about at Universe. Every one of these tools deepens your dependency on GitHub's ecosystem. Copilot Workspace only works with GitHub repos. Spark deploys to GitHub's infrastructure. Codespaces runs on Azure. The developer experience is improving, but so is the gravitational pull toward Microsoft's platform. GitLab and Bitbucket are scrambling to match these features, but they are years behind on the AI integration story. What This Means for Agencies For agencies like ours, the practical takeaway is that Copilot Workspace is worth integrating into the workflow for issue-driven development. Spark is useful for client prototypes and proof of concepts. The multi-model Copilot is the most underrated announcement — being able to switch between Claude and GPT-4o depending on the task is genuinely useful. GitHub is not replacing developers. But it is making the gap between "idea" and "working code" shorter every year. The developers who win are the ones who use these tools to move faster while keeping their architectural judgment sharp.