We are a team of researchers and engineers at @GitHub who investigate the future of software development.
The Future
Joined July 2020
- Tweets709
- Following47
- Followers29.6K
- Likes1.3K
GitHub Next retweeted
so satisfying
Built a skill to bring the magic of the OP-1 to agentic development and wrote a post about it on @GitHubNext (sound on for maximum clickage)
GitHub Next retweeted
Built a skill to bring the magic of the OP-1 to agentic development and wrote a post about it on @GitHubNext (sound on for maximum clickage)
GitHub Next retweeted
So much is moving towards computers becoming actual terminals again, running their compute *somewhere else*. Even the personal stuff.
The Hypercloud Movement™
GitHub Next retweeted
How do you solve the trust problem with AI-generated code?
AI agents can generate code at a scale too great for humans to review line-by-line. That makes it difficult to ensure the code will do what the developer intended, and it leaves the final output vulnerable to bugs and security risks.
Proof-Driven Development Kit turns plain-language developer intent into a specification in Verus, applying formal methods traditionally used for safety-critical systems. PDD Kit uses mathematical proofs to test agent-generated code against the spec where possible, and clearly indicates where the proofs can’t reach. The result is more reliable agentic code.
Researchers @MatthaiP39719 and @alexlavaee break down Proof-Driven Development in the MSR blog: msft.it/6019af2V7
GitHub Next retweeted
Making 50% of the world’s code verifiably secure.
Traditionally, formal methods have been relegated to verifying safety-critical systems like operating systems, hypervisors, databases, etc. We’re extending this approach to formally and empirically verify code correctness and security for full-stack web applications using Proof-Driven Development Kit (PDD Kit).
A large portion of the world’s software consists of web applications, and we see this as a starting point for our everyday software.
Check out our blog here: githubnext.com/projects/pdd-…
From @GitHubNext x @MSFTResearch
GitHub Next retweeted
We've just published an in-depth write-up about the PDD Kit - collaboration project between us (@GitHubNext) and @MSFTResearch focused on formal verification in the world of AI agents. 🤖
Check it out:
githubnext.com/projects/pdd-…
GitHub Next retweeted
ALT Maggie giving her talk
ALT GitHub Next cooking
ALT Salut Chopin
ALT Chopin in action
GitHub Next retweeted
Today is my first day at @GitHubNext!
GitHub has been one of my favorite places to hang since I signed up 18 years ago(!), a mere month after its founding.
Excited to join this talented team to try and figure out what comes next for our craft ...
GitHub Next retweeted
Found time last week to cleanup the homepage & docs of Agentic Workflows, one of the very successful @GitHubNext projects of the last year. TLDR: run your own software factories on GitHub Actions
Previous page was vibed by agents and backend developers. Took me a day to redo it.
GitHub Next retweeted
Had a wonderful chat with @GergelyOrosz - always nice to go deep on ideas in a proper long chat. Got to show off some notebook sketches and design jigs with agents too.
What can us, engineers else learn from designers and design engineers? Turns out there’s lots, based on talking with one of the best design engineers in the industry, @Mappletons.
Timestamps:
00:00 Intro
03:24 From anthropology to tech
10:18 What does a designer do?
18:23 How Maggie works
24:55 The case for planning with physical tools
31:53 Why Maggie is learning woodworking
33:13 Design engineers and engineering constraints
38:49 How Maggie uses Figma
40:30 Design at GitHub Next
45:12 How has AI changed design
50:37 When models design and why humans are still needed
53:30 UX and UI
58:29 Capability gaslighting
1:00:33 One Developer, Two Dozen Agents, Zero Alignment
1:07:21 Craft and AI tells
1:14:17 Visual gardens, home-cooked software, and barefoot developers
1:21:02 Advice for engineers and lessons from anthropology
1:25:34 Book recommendation
Brought to you by:
• @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. turbopuffer.com/pragmatic
• @AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. antithesis.com/pragmatic
• @EntireHQ – every agent prompt, tool call, stored in your repo, and mirrored. Set up with one click: entire.io/pragmatic
Hope you enjoy this unusually visual episode - thanks again, Maggie!
GitHub Next retweeted
hot take: code has been commoditised but access to do code hasn’t yet
ai transformation at software companies is mainly about removing gate keepering and enablement of anyone from anywhere to contribute ideas (even if they get thrown away. it’s better than a slack message!)
GitHub Next retweeted
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-0…
GitHub Next retweeted
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 teapawt.net/ghchangelog/status/206… and believe me that this is a game changer cause the previous way on minting tokens was impossible
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-preview
ALT New release: Agentic workflows are now in public preview
GitHub Next retweeted
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-0…
GitHub Next retweeted
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-preview
ALT New release: Agentic workflows are now in public preview
GitHub Next retweeted
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
GitHub Next retweeted
We have a draft of new report from GitHub Next! 🚀
github.com/githubnext/repo-a…
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/repo-a…
GitHub Next retweeted
Got to talk at @aiDotEngineer conf last week about the need for collaborative AI engineering.
All our current coding agents are single player. We're trying to scale up individual productivity, but creating tons of alignment problems in the process.
We have no good tools for...
