GitHub Next investigates the future of software development.

We are a team of researchers and engineers at GitHub, exploring things beyond the adjacent possible. We prototype tools and technologies that will change our craft. We identify new approaches to building healthy, productive software engineering teams.

@agorischek @agorischek
@davidslater @davidslater
@dsyme @dsyme
@iamnbutler @iamnbutler
@idan @idan
@insop @insop
@krzysztof-cieslak @krzysztof-cieslak
@lpcox @lpcox
@lukeed @lukeed
@maggieappleton @maggieappleton
@mnkiefer @mnkiefer
@mrjf @mrjf
@pelikhan @pelikhan
@ppenna @ppenna
@rahulpandita @rahulpandita
@rfonseca @rfonseca
@szabta89 @szabta89
@terkelg @terkelg
@vic-lsh @vic-lsh
A launch readiness flow with insights and checklist triage.
Post
Chris Butler

Agentics Beyond Code

What happens when you give PMs, compliance teams, and leaders their own agents? A tour of Agentics Beyond Code — an open-source set of GitHub Agentic Workflows for the non-engineering roles that ship, govern, and operate products.

Post
Landon CoxPeli de HalleuxRodrigo FonsecaVic LiPedro Henrique PennaDon Syme

Control what your agentic workflows see with integrity filtering

GitHub Agentic Workflows filter untrusted GitHub content before it reaches the agent. Here’s why integrity filtering matters for repository maintainers, and how we built it.

Post
Russell Horton

Agent Functions

Prompts are programs. You wouldn’t write a complex program completely from scratch, in a big, soupy loop without subroutines, and then write it again the next time you wanted to run it. Why let your agent work that way?

Little ideas
Terkel Gjervig

A loader with level of detail

Borrowed from 3D rendering: level of detail. The loader shows more as it grows and strips back as it shrinks, so it reads cleanly at any size.

Post
Tamás Szabó

Canary: a harm gate for agentic systems

Canary puts a small, auditable gate in front of agentic workflows so untrusted artifacts are classified before powerful agents act on them.

Link
Don Syme

The Impact of Automated Repository Maintenance Assistance

https://github.com/githubnext/repo-assist-impact/blob/main/report.md

What happens when a proactive AI repository agent is deployed across 13 open source repositories? 578 issues closed, median 8x increase in issue closure velocity, and 10x in PR merge velocity — transforming largely dormant projects into actively maintained ones. The single most important factor? The rate at which human maintainers decide to act.

Read the full report from GitHub Next.