Tomas Reimers is a co-founder of Graphite and head of Origin, Cursor’s new Git platform. He builds tools that help engineering teams review, organize, and ship increasingly large volumes of code without sacrificing quality.
Reimers first learned to program because he wanted to build video games his parents would not buy him. Before founding Graphite, he worked on developer tools at Facebook in New York, developing a framework used by more than 200 product teams and 1,000 developers. The contrast between sophisticated internal engineering infrastructure and the tools available to smaller companies helped define his subsequent work.
Alongside Merrill Lutsky and Greg Foster, Reimers turned an internal productivity tool into Graphite, bringing stacked pull requests to Git and GitHub. The approach breaks dependent work into smaller, reviewable changes, allowing developers to continue building while earlier changes await approval. His technical writing explains both why stacked changes accelerate collaboration and how Graphite stores branch relationships inside Git. In May 2022, Graphite announced a $20 million Series A.
As coding assistants increased software output, Reimers focused on the resulting strain on review and delivery. Graphite developed Graphite Diamond, an automated reviewer designed to catch consequential bugs without overwhelming developers with unreliable or pedantic feedback. After Graphite agreed to join Cursor in December 2025, Reimers began leading Origin, extending his work from pull-request workflows into a new Git platform.
- The outer-loop bottleneck: AI accelerates coding, but every additional change still requires review, testing, merging, and deployment. Reimers argues that teams must modernize the entire software-delivery workflow, including pull-request prioritization, continuous integration, and merge queues.
- High-signal AI code review: Effective automated feedback must satisfy two separate conditions: the model can identify the problem reliably, and developers actually welcome the intervention. Crash-causing logic errors may clear both thresholds; generic suggestions to add comments, extract functions, or write tests frequently do not.
- Undocumented team knowledge: Important architectural decisions and abandoned approaches often survive only in experienced developers’ memories. Repository history and documented conventions improve automated review, but cannot supply context that was never recorded.
- Actionable review as the real metric: Reimers evaluates comments partly by whether they produce changes within the same pull request. Graphite’s internally reported results put Diamond’s action rate around 52 percent, compared with roughly half for human reviewers, with downvotes below 4 percent; these figures were not independently audited.
