What an amazing week for the team at @atomicdotdev. atomic query, atomic vault, atomic team, https://t.co/RMLnfnQgHg! Well on our way to building the developer inner loop! Next up, cb workflows with @binsquares smolvm’s!
Happy to announce a dedicated desktop app for smolvm (@binsquares)!
At @atomicdotdev, we believe lightweight VMs will be a core piece of infrastructure in the age of agents.
It's still early, but I'd love for people to try it out and let me know what you think. Link in thread.
@BradleyDotDev@binsquares@atomicdotdev All your favorite OCI layers in a VM that is native to your Mac. With GPU pass-thru, building a local LLM stack has never been easier.
@ibuildthecloud@BHolmesDev Working with the Electron team during my early days at GitHub, I will say I prefer Tauri. It also depends on what you are building. We love what @binsquares is building so our team built https://t.co/RhXQX6eTXe on Tauri.
@aloisdeniel My setup is similar but for isolation I use @binsquares SmolVM. I stopped using git and started using @atomicdotdev for its code intelligence which is saving me 70% on token consumption through its semantic call graph
@GergelyOrosz@mitchellh I agree. I’ve been posting since I left GitLab explaining what I was seeing from executives to IC. This is why we are building @atomicdotdev to help companies and developers understand the AI output as a graph that is searchable and reviewable. Not just the generated slop
@astuyve The import thing is audit ability. Can you trace that to a git commit that just got squash merged? We are tackling that problem at @atomicdotdev. Realizing that just surfacing the trace isn’t enough, we build a semantic call graph around the trace so you can query “bash rm”
@binsquares@corbin_braun We got our release out this week! I’m ready to start integrating SmolVM into Circuit Breaker. Together we can own the inner loop!
@ibuildthecloud There may be a better way: https://t.co/VPIYv5njNa. Add agent skills for atomic and you don’t need GitHub anymore. Their whole revenue model requires users to accept an outer loop mentality when agent harnesses are forcing developers into an inner loop mentality
@colinarms@conductor_build This is a common issue with git and worktrees. You either need to use a global node_modules or create a shared node_modules outside your working directory and have symlinks for the work tree. You could try something that isn’t git try https://t.co/OIQril3cpd
@mitchellh Are they now running their servers on Windows and having to restart every morning due to another critical update that was vibe coded with CoPilot?
@ashtom@GergelyOrosz@EntireHQ The question for me is git fails at scale. Large monorepos are becoming the norm so agents don’t have to span many repos. So now adding additional refs to already swamped repos will create contention from the customers I am talking to. They want better git
@mitchellh I’m working on it. I have an OpenCode plugin that integrates with Atomic VCS so you can use the credit system for a line by line but also an attribution system for change record provenance. https://t.co/VPIYv5njNa