owned by · as of 2026-09-15
Browse · Organizations
GitHub
Microsoft’s software development platform expanded from sharing Git repositories to code suggestions and delegated agent work, with branches, tests, and pull requests keeping proposed changes inspectable.
GitHub is Microsoft’s software development platform and the organization behind GitHub Copilot and Agent HQ. Its AI products connect models to repositories, issues, execution environments, and code review. Copilot began with suggestions offered as a developer typed; cloud agents now research repositories, plan changes, and implement tasks that developers can inspect before accepting.[5][6][10][8]
Copilot: from completions to delegated repository work
GitHub launched Copilot’s technical preview on June 29, 2021, developed with OpenAI and initially powered by OpenAI Codex. It used the code being edited as context to suggest whole lines or functions. Suggested uses included writing tests, exploring unfamiliar APIs, and considering alternative implementations. The original interaction was immediate: the developer typed, and the model offered a continuation.[6]
Delegated repository work changes the unit of assistance from a continuation to a task. Copilot cloud agent has its own ephemeral development environment powered by GitHub Actions, where it can explore code, edit a branch, and run automated tests and linters. Tasks include bug fixes, incremental features, documentation updates, improved test coverage, and technical-debt work.[10]
On GitHub.com, developers can ask the agent to research a repository, create a plan, and refine changes before optionally opening a pull request, a proposal to review and merge the work. Some external integrations create pull requests directly. Cloud agent runs separately from the developer’s machine; IDE agent mode makes edits in the local development environment. Branches separate proposed changes, while commits and logs record the work for inspection.[10]
Agent HQ and access across providers
GitHub announced Agent HQ on October 28, 2025 to bring multiple providers’ agents into existing GitHub workflows. Kyle Daigle described the problem as “incredible power fragmented across different tools and interfaces”. Its mission control provides a common interface to assign, steer, and track agents, alongside enterprise controls for agent access, policies, audit logging, and usage metrics.[8]
On February 4, 2026, GitHub announced Claude by Anthropic and OpenAI Codex in public preview for Copilot Pro+ and Enterprise users on GitHub, GitHub Mobile, and VS Code. Developers could assign different agents to the same problem, compare approaches, and review proposed changes through draft pull requests and comments. Google, Cognition, and xAI remained prospective integrations in that announcement.[9]
GitHub’s official Model Context Protocol (MCP) server connects compatible AI tools to GitHub API capabilities: reading repositories, managing issues and pull requests, and examining Actions workflow runs. Configurable toolsets and individual tools let operators select the capabilities exposed to an agent; read-only mode excludes write tools. GitHub recommends limiting enabled toolsets to reduce context size and help models choose tools.[11]
These agent workflows build on GitHub’s earlier repository-sharing and collaboration service, publicly launched in 2008. That history supplies the context for its present use of branches, issues, pull requests, and automated execution.[1][3][8][10]
Earlier history: Grit, Rails, and the public launch, 2007–2008
GitHub built a service around Git, the version-control system created by Linus Torvalds in 2005. In his account of GitHub’s beginnings, Tom Preston-Werner recalls showing Chris Wanstrath Grit, his Ruby interface to Git repositories, at a San Francisco meetup in October 2007 and proposing a website for sharing repositories. He continued developing Grit and designed the interface; Wanstrath built the Rails application.[4][3]
Preston-Werner dates Wanstrath’s first repository commit to October 19, 2007, followed by a private beta in January 2008. PJ Hyett joined in early 2008. The public launch on April 10 included commit comments, network graphs, and Campfire and Lighthouse integrations. By October, GitHub reported more than 20,000 public repositories, four full-time employees—Preston-Werner, Wanstrath, Hyett, and Scott Chacon—and no venture capital or other outside investment.[3][1][2][4]n1
After Microsoft acquired his employer, Powerset, Preston-Werner says he declined an employment offer including salary plus $300,000 over three years and joined his collaborators full time on GitHub. Early users also wanted to pay: in WIRED’s 2012 history, Wanstrath recalled PeepCode founder Geoffrey Grosenbach asking to send a check because his company’s code was hosted there.[3][4]
In February 2012, WIRED reported that GitHub was profitable, with more than 1.3 million users and over 2 million source-code repositories. Free accounts supported contribution, while private hosting started at $7 per month. Its enterprise product let companies run GitHub behind a corporate firewall, with annual pricing starting at $5,000.[4]
Microsoft ownership and CoreAI
Microsoft completed its acquisition of GitHub on October 26, 2018, with Nat Friedman taking over as CEO. Microsoft said GitHub would operate independently and remain an open platform. In August 2025, Thomas Dohmke announced his departure as CEO and said GitHub’s leadership would continue within Microsoft’s CoreAI organization; he planned to remain through the end of 2025 to support the transition.[5][7]
In September 2026, GitHub’s leadership directory identifies Kyle Daigle as COO and CMO, Mario Rodriguez as chief product officer overseeing AI and Copilot strategy, and Vladimir Fedorov as CTO.[12]
Internal AI adoption and contribution trust
In a June 2026 interview, Daigle described using AI to reconstruct recent work across pull requests, notes, Teams transcripts, and Slack before proposing near-term messaging changes. “I’m always looking at what had happened first,” he said. He also described building a small application to inspect revenue-planning information in SQLite and producing a presentation for GitHub’s revenue and finance teams.[13]
Daigle framed changes to contribution review as an attempt to codify trust. In his view, more verification artifacts do not resolve the human and social question of whether a reviewer trusts a contribution. He favored adaptable maintainer controls and cautioned that passive signals such as stars, commit counts, and account age can be gamed.[13]
Scale and the August 2026 outage
GitHub reported 180 million developers in October 2025. In August 2026, Fedorov reported that monthly commits had risen from 1.4 billion in April to 2.9 billion. These figures describe adoption and platform activity, respectively.[8][14]
GitHub’s account of the August 17, 2026 outage reported 7 hours and 47 minutes of disruption affecting authentication, Actions, APIs, pull requests, issues, and Copilot. Its investigation found that peak traffic overwhelmed a critical infrastructure component in the Central US data center. Copilot client retries increased traffic during recovery. Fedorov attributed both that incident and an August 6 Actions failure to capacity shortages, rather than code or configuration changes.[14]
Fedorov reported adding more than 3 million CPU cores and 120 petabytes of high-speed storage, alongside network capacity and an accelerated Azure migration. By August 20, Azure served roughly 58% of platform load, up from 12% in May. GitHub also redirected resources toward availability and was isolating critical systems and applying consistent retry limits, retry budgets, and variable timeouts to reduce cascading load.[14]
From the Latent Space archive
Original posts and separately reviewed explanations.
Notes
Sources
- 1We LaunchedAccessed 2026-09-17
- 2GitHub Turns One!Accessed 2026-09-17
- 3How I Turned Down $300,000 from Microsoft to go Full-Time on GitHubAccessed 2026-09-17
- 4Lord of the Files: How GitHub Tamed Free Software (And More)Accessed 2026-09-17
- 5Microsoft completes GitHub acquisitionAccessed 2026-09-17
- 6Introducing GitHub Copilot: your AI pair programmerAccessed 2026-09-17
- 7Auf Wiedersehen, GitHub ♥️Accessed 2026-09-17
- 8Introducing Agent HQ: Any agent, any way you workAccessed 2026-09-17
- 9Pick your agent: Use Claude and Codex on Agent HQAccessed 2026-09-17
- 10About GitHub Copilot cloud agentAccessed 2026-09-17
- 11github/github-mcp-server — GitHub’s official MCP ServerAccessed 2026-09-17
- 12Our leadershipAccessed 2026-09-17
- 13GitHub’s plan for Agents — Kyle Daigle, GitHubAccessed 2026-09-17
- 14The August 17 outage, and the work aheadAccessed 2026-09-17
Model source and teaching reviews passed. Human editorial review pending. This profile describes the sources as of 2026-09-17.