@thorstenball I think I struggle with this with spaces because they feel more like slack channels almost. Like they’re meant to be longer lived? Is that not how you all think about them?
@sqs I think then I’d expect that my “personal” stuff is basically just its own workspace that I pay for. And my work stuff gets bucketed into my work billing (assign the orb, token usage to whatever workspace the project is in)
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.
https://t.co/Lo13Er8KEH
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!
https://t.co/lNc9gMjEas
@sqs 4 (I still have a lot of challenges around wanting my personal stuff more split from my work stuff), 8, 1, maybe 2 (just unsure how this differs from the current account switcher) are my top ones!
@richardartoul Check out @rwx! Never run the same thing twice, reuse work you already did across many parallel machines, and all with a very developer (and agent) friendly UX!
@RamV2003@rwx The same bits that enable that also enable automatic caching (if you already ran something, don't run it again) based on the contents of your filesystem and the hash of the other inputs (no more `shasum(list, of, files)`, no false positives)
@RamV2003@rwx Instead of running a bunch of duplicate work on multiple VMs when you need to parallelize, you run it once because we can re-use the execution of a command (e.g. clone once, npm install once, setup your db once, then run your tests across 50 parallel workers reusing that work).
It’s kinda crazy that Amp’s GitHub subscriptions are maybe the first time I felt like I’ve had actionable GitHub notifications (via Amp thread notifications). Nice work @AmpCode team!
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: https://t.co/SGCToc1GXw