Alexis Bouchez
@alexisbchz
Software engineer @depotdev
Your code is fine. Your GitHub runner isn’t. Most “mystery” CI failures = resource constraints: 👉 Memory killed 👉 CPU throttled 👉 Disk full Full guide to debugging GitHub Actions in 🧵
For the tech writers in my Twittersphere: If I hadn’t just started at @lingodotdev, I’d be applying for this @depotdev role. ycombinator.com/companies/depo…
Ouhhh... Husbandt... You wasted time waiting for CI instead of creating shareholder value. And now we are homeress...
My dream Slack replacement: IRC
My dream Slack replacement: 1. Simple, clean design 2. Feed of key discussions (summarized) across orgs 3. Natural language prompts, no commands 4. Perplexity-like search in and across orgs 5. Agents instead of bots 6. Universal usernames 7. Notifications for DMs, mentions, or…
"This is exactly what I needed" - every developer who's ever stared at a failed GitHub Actions job wondering what the hell happened. We shipped proper observability for CI jobs because apparently showing logs uncollapsed is revolutionary in 2025. The bar was on the floor.
it's ready. lmk if you want access demo + full launch on monday
Claude Code had amnesia. Every time you closed your laptop or switched machines, it forgot everything. So we gave it a memory. depot claude lets you save and resume sessions across machines, teammates, and CI. Finally. link in 🧵
TIL that Docker is working on a proper public Go SDK. github.com/docker/go-sdk
GitHub Actions job logs are where dreams go to die. Collapsed by default, no resource metrics, and when jobs fail you're left playing detective. We just shipped GitHub Actions job details to fix this nightmare and actually show you what happened in your job 🧵
@depotdev just dropped Claude Code sessions. Run depot claude --session-id feature and your AI session runs IN THE CLOUD. No local compute needed. Persistent state. Resume from anywhere. Your laptop just became a supercomputer 💻→☁️
We aim to make builds exponentially faster with as little work as possible. So we're excited to make this feature generally available. Autoscaling is there when you need it, invisible when you don't. Full blog post 👉 depot.dev/blog/build-aut…
Most teams don't need build autoscaling. Single builders with good cache sharing usually win. But when you're drowning in concurrent builds, the math changes completely. We just dropped autoscaling for those moments 🚀 🧵