Theme 1: Firecracker as the common underlying VM
Many commenters note that the agent platforms run on Firecracker lightweight VMs.
- “TLDR is they use firecracker with memory in git.” – RohanAdwankar
- “It's always, firecracker all the way down!” – hypendev
Theme 2: State persistence via Git (markdown files)
The discussion highlights how these platforms store agent “memory” and filesystem state directly in a Git repository, often as simple markdown files.
- “I'm a big fan of the memory in git part it would be cool to see how the git history looks after I use it for a longer period of time.” – RohanAdwankar
- “did you notice meaningful differences in how the platforms handle filesystem persistence between sessions?” – quietraster
- “What was surprising to me was that instinct was just 'agent slapped on top of markdown files in git'… its just three markdowns in a trenchcoat.” – hypendev
Theme 3: Expectation vs. reality – perceived simplicity/under‑engineering
Several participants express that the platforms feel less sophisticated than anticipated, expecting databases or graph‑based stores but finding only plain Git‑based markdown.
- “I expected at least a database or a graph or something 'smart', but alas, its just three markdowns in a trenchcoat.” – hypendev
- “Enjoyed the breakdown, honestly most of the things weren't really surprising.” – hypendev (acknowledges the lack of novelty)
These three themes—Firecracker infrastructure, Git‑based persistence, and the surprise at the platforms’ apparent simplicity—dominate the conversation.