GitHub Next

A new report from GitHub Next! The Impact of Automated Repository Maintenance Assistance githubnext.com/posts/dsyme-im… What happens when a proactive AI repository agent is deployed across 13 open source repositories? Hundreds of issues closed, median ~8x increase in issue closurea nd 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. #ContinuousAI #RepoAssist #GitHubNext

@PromptSlinger @zeke @idangazit @Mappletons gave a demo of it at AIE London, the visuals are a bit out of date but the core concept is there, in lovely essay form: maggieappleton.com/zero-alignment

@zeke @GitHubNext @idangazit oh wait multiplayer coding like google docs but for actual code? that sounds either amazing or chaotic, probably both

@GitHubNext hey party people I missed @idangazit's demo at AI Engineer last week. Something about a multiplayer coding environment... can I try it out!?

@PromptSlinger @zeke @idangazit

@ilbert_luca @shadcn @Mappletons There wasn't a write up we removed, more that we have been heads down on building and we sucked at spending time on the storytelling. The best resource right now is @Mappletons 's talk but that's on her site: maggieappleton.com/zero-alignment

@GitHubNext @shadcn @Mappletons Good news! Why isn't it visible anymore on the githubnext.com website though?

I didn't expect this tweet to be controversial. But here we are. Okay so look at the most popular apps you use every day. Now think about what they looked like two years ago vs today. They're all converging on the same three panels. An explorer on the left. A chat in the middle. A preview on the right. Look at the new apps being built. Same shape. That's Slack. Now think about how your team actually works. Work starts and happens in Slack. You only tab away for two things: context and ui. Context, because the data you need lives somewhere else. UI, because some things need buttons. Different buttons. An agent collapses both into one app. Context, it's already good at, it goes and gets whatever you need. UI, it's getting there. Soon it'll build the buttons right where you work. Whoever nails this shape owns where work happens next. The 2030 Microsoft Office.

@ilbert_luca @shadcn @Mappletons Not shut down! We're still working very hard on it

@shadcn This sounds really similar to the Ace project that @Mappletons presented recently from @GitHubNext. Though it seems like they've shut it down maggieappleton.com/zero-alignment

The aim of agentic workflows is to make the repo and PDLC a living organism. Think a garden. Alive, evolving, and always improving. We have a wide catalog available and we will continue to expand them. github.blog/changelog/2026…

This is huge! We’ve been partnering with @GitHubNext team and this is a real thing! I know we talk a lot about coworks and Hermes etc but real engineering happens in pipelines and taking advantage of GitHub actions as pipeline runtime plus having the ability to run @GitHubCopilot CLI agent harness there, in a secure manner !!!, is the way to scale where engineering goes to die - endless manual tasks can be agentified And don’t get me wrong - as much as I say it is good it has been a struggle to run it in corporate constrained environment and there is work that can be done e there to improve Also cost management is hard and there are no clear controls to stop spend and u need to build your own But in good timing they also released this x.com/ghchangelog/st… and believe me that this is a game changer cause the previous way on minting tokens was impossible

OMG the one-liner we wish we'd said

Agentic workflows can now use the built-in GITHUB_TOKEN instead of personal access tokens, reducing security risks and simplifying automation. github.blog/changelog/2026…

GitHub Agentic Workflows are now in public preview. Intelligent automations for GitHub, with strong guardrails, observability, and cost controls. Start automating today 👇 gh.io/aw-public-prev…

Python trains, TypeScript ships. Tickets just dropped for TypeScript AI Conference: London → luma.com/tsaiconf Featuring speakers from @GitHubNext, @elastic, @sentry, @arizeai, @CopilotKit, @factorialapp, and others. July 23 | London & Virtual | Builders only

Agents Need Boundaries Too! Read about this GitHub Next exploration of reusable harm gates, to keep the agents in the channel to success, even when subverted by attackers. githubnext.com/posts/canary-h… #GitHubNext #AgenticAI

Read about "Agent Functions", a new agentic design pattern for structuring agents, from GitHub Next githubnext.com/posts/agent-fu… 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?

At GitHub Next, the Autoloop agent is porting Pandas to Typescript Read about this experiment in simple, declarative goal-directed repository automation! githubnext.com/posts/tsb/

Ace👀

We have a draft of new report from GitHub Next! 🚀 github.com/githubnext/rep… The Impact of Automated Repository Maintenance Assistance - We analyze the impact of 🌈 Repo Assist, a proactive AI repository agent implemented as a GitHub Agentic Workflow, across 13 open source repositories in early 2026. - The agent reduced open issue counts in every repository - 578 issues total. - The repositories, which were largely dormant, achieved median velocity increases of 8× for issue closure and 10× for PR merges, transforming largely dormant projects into actively maintained ones. - We model repositories as human-agent software factories - the factory’s throughput is gated by human decision-making. Read the draft in our repository github.com/githubnext/rep…

Thanks for the feedback. We will add notes along these lines: * The rate of "/repo-assist" human guided agentic intervention is mentioned in the report. * There was little other review override - some but not much. * Reopen rate was essentially zero. * Learning memory repo norms is not part of the spec of repo-assist, it could be added through memory.

@GitHubNext The useful signal is not just merged PRs; it is maintenance debt avoided. I would want to see reopen rate, reviewer override rate, and whether Repo Assist learns repo-specific norms without turning every maintainer preference into hidden policy.