Kyle Thompson (@kylekthomp) header
Kyle Thompson (@kylekthomp) profile picture

Software Engineer @rwx

Babcock Ranch, FL
Joined September 2014
Photo by Kyle Thompson (@kylekthomp)
Kyle Thompson retweeted
I’m excited to announce that @GoEntire now supports running CI through @RWX. Rebuilt from the foundation up for how agents work: ➡️ RWX: a graph-based execution model with automatic caching. Far less compute needed per loop. ➡️ Entire: Trails replace the pull request, keeping context, code, and verification in one place, even across repos and agent sessions. rwx.com/blog/entire-integrat…
1
3
1
18
1,509
Kyle Thompson retweeted
Native integrations for CI build another layer of developer choice and control into the fastest Git forge on Earth. Today, we’re excited to announce our partnership with @rwx , an agent-native CI platform now built directly into the Entire plugins. Try it out! entire.com/blog/ci-with-rwx-…
8
30
2,028
Kyle Thompson retweeted
2x the builds, half the duration — that's what @honeycombio saw after switching from CircleCI to RWX in March 2026. @lizthegrey (Technical Fellow at Honeycomb) included the exhibit below in the company's blog post, "AI Amplifies Your Existing Practices: Lessons from Our Shift to an AI-First Strategy." As Liz puts it: "Fast CI is no longer a nice-to-have. It's now a precondition for AI throughput to be worth anything at all." Read Honeycomb’s full post: honeycomb.io/blog/ai-amplifi…
6
10
799
Kyle Thompson retweeted
Replying to @bonusly
@bonusly reports a 75% reduction in build times and a 65% improvement in deployment reliability since adopting RWX's dev cloud in 2025. “RWX singlehandedly changed how our team approaches the development cycle. Our engineers fully trust the platform, and our CI/CD pipeline has never been faster.” - Jeremy Thomas, SVP of Engineering at Bonusly Read the case study: rwx.com/customers/bonusly
1
7
7
655
Kyle Thompson retweeted
The limiting factor in software engineering is no longer writing code. It's validating it. Every major shift in software development has required new infrastructure, and AI-driven engineering is no different. @rwx is the dev cloud built specifically for that transition. I’m excited to announce we raised $12 million in Series A financing led by @hydeparkvp with angel investors including @theo, @bryan_johnson and Jenkins creator @kohsukekawa participating. rwx.com/blog/series-a?utm_so…
13
19
2
77
1,238,065
Kyle Thompson retweeted
GitHub just shocked engineering team budgets with a change to GitHub Actions pricing. For people using self-hosted runners, or runners provided by a third-party, GitHub previously offered their CI/CD control plane for free. This will no longer be the case. Many people using third-party runners chose that option for the cost advantages, and this changes the equation. For engineering orgs that really want to reduce costs though, there’s a better way. GitHub Actions still uses the traditional approach of running jobs on parallel VMs. However, running pipelines as a graph (DAG), while utilizing automatic, content-based caching, provides the most substantial cost reductions. This approach is the key to how the big tech companies like Google and Meta run their pipelines. We built @rwx to make this approach accessible for regular engineering teams. RWX runs pipelines faster, and more cost effectively, than any other CI/CD platform. We completed a cost comparison today where a pipeline on RWX used a total of 84,004 seconds of execution, while the identical pipeline on GitHub Actions consumed 300,787 seconds of compute, for a 70%+ reduction on RWX. If anybody wants to relieve some pressure on their engineering budget in 2026, send me a DM.
2
8
736
Kyle Thompson retweeted
Next Monday, @rwx will be launching the biggest evolution in container technology since the release of Docker’s BuildKit, which is now over 7 years old. Docker changed how applications are deployed. Containers bundle system dependencies with application code, providing a portable image that can run on any generically configured server. Unfortunately, building container images can be painfully slow and inefficient. Too many engineering teams are hindered by a CI/CD pipeline that takes 10+ minutes to build and push images before even the smallest code change can run. The sluggish performance impedes human productivity, and it stands in the way of unleashing agentic coding. Until now. We looked at the problem from first principles and built an entirely new platform for building container images. It is up to 10x faster and produces the same Docker images that everybody runs today. Join us on a Zoom call on Monday November 24th to be one of the first to see it 👇 rwx.com/launch
2
4
16
1,227
Kyle Thompson retweeted
Everyone should be checking out @rwx to replace their CI. This team is killing it!
This is useful, and fun. I like using the prompt "get the list of tests that failed in CI and write them to tests.md as a todo list"
1
2
4
418
Kyle Thompson retweeted
still blown away every time a merge into main instantly deploys because of @rwx_research Mint's cache hits.
3
6
1,525
Kyle Thompson retweeted
We agree. One reason among many that Mint provides the best developer experience in CI/CD 😎
Replying to @bradgessler
Here's what I think a reasonable CI should have: 1. Uses Docker containers so people can run locally without the `git commit -am "F-ing CI" && git push` business. 2. During setup, have an option for a failed CI to open an SSH port so devs can shell in and see what's up.
1
3
369
Kyle Thompson retweeted
Why should CI runs have to be finished before they're marked as having failed? We separated result status and execution status in Mint. Now runs are marked as failed as eagerly as possible, even if tasks are still running. @TAGraves just made it happen 🎉
3
4
1
11
1,749
Kyle Thompson retweeted
We built a breakpoint debugger into Mint to solve this problem. Call `mint-breakpoint` anywhere you want, and then run `mint debug` using the local CLI to open a shell. Shouldn’t have to push and guess at changes in CI/CD workflows.
Hey @github, here's something I'd love: the ability to launch a new codespace from a failed github action using the YAML file so I can debug it without this whole guess a fix, push, and wait dance that's so infuriating.
3
7
2,307
Kyle Thompson retweeted
When you revert a PR and CI is entirely cache hits 😎 After using Mint, I can't go back to CI without content-based caching
5
15
1,724
Kyle Thompson retweeted
We have been a long time customer of @depotdev. It's the fastest way to build Docker images, and we use it for all of our applications. We've built Mint to be the fastest CI platform, so we knew we needed to make Depot available. And now it is! rwx.com/blog/depot-mint-inte…
2
2
5
1,348
Kyle Thompson retweeted
Replying to @HamelHusain
Mint solves all of those problems! Is this the DX you're looking for?
6
15
2,554
Kyle Thompson retweeted
We’re sharing the first public preview of Mint, our new build tool, at the end of May. Join us at one of these sessions: 🗓️ Tue May 30 @ 4pm Eastern: rwx.com/events/2023-05-30-mi… 🗓️ Wed May 31 @ 10am Eastern: rwx.com/events/2023-05-31-mi…
2
5
1
8
2,633
If each of our tests have “five nines” of stability: Each test will pass 99.999% of the time and flake 0.001% of the time. Then, a build of 100,000 tests will flake and fail 64% of the time (0.99999^100000). Test stability is hard.
4
11
2
72
13,733
Kyle Thompson retweeted
Captain is now open source! It's is a CLI that can detect and quarantine flaky tests, automatically retry failed tests, partition files for parallel execution, generate comprehensive test failure summaries, and more. rwx.com/blog/captain-1-10-ge…
6
7
1,746
Kyle Thompson retweeted
Last year, we began building a universal test runner that executes test suites as distributed workloads. After a thorough beta testing period over the past several months, we’re excited to announce the generally available, open source release of ABQ. rwx.com/blog/abq-1-3-general…
1
6
2
12
170,316