Bringing Atuin to the desktop (Interview)
Episode
56 min
Read time
2 min
Topics
Software Development, Psychology & Behavior, Science & Discovery
AI-Generated Summary
Key Takeaways
- ✓Runbook execution architecture: Atuin Desktop embeds executable terminal blocks and scripts within documentation, allowing teams to run multi-step workflows directly from docs rather than maintaining stale Confluence pages that require constant manual updates and verification.
- ✓Open source monetization strategy: The desktop app uses Apache 2 license for local software while keeping the sync hub closed source temporarily, avoiding premature license decisions. Individual users access features free while organizations pay for collaborative team features.
- ✓Development stack choices: Built with Tauri instead of Electron, resulting in 20MB downloads versus 500-700MB, using system WebKit on each platform. All backend logic runs in Rust for performance, enabling future CLI runtime execution of runbooks.
- ✓Shell history integration: Users can pull commands from years of Atuin CLI history directly into desktop runbooks, bridging the gap between local experimentation and team documentation. The CLI records every shell command, making workflow documentation retroactive and accurate.
What It Covers
Ellie Huxtable discusses Atuin Desktop, a new runbook editor that makes team workflows repeatable and shareable, building on the success of Atuin CLI's shell history syncing tool used by 26,000 developers.
Key Questions Answered
- •Runbook execution architecture: Atuin Desktop embeds executable terminal blocks and scripts within documentation, allowing teams to run multi-step workflows directly from docs rather than maintaining stale Confluence pages that require constant manual updates and verification.
- •Open source monetization strategy: The desktop app uses Apache 2 license for local software while keeping the sync hub closed source temporarily, avoiding premature license decisions. Individual users access features free while organizations pay for collaborative team features.
- •Development stack choices: Built with Tauri instead of Electron, resulting in 20MB downloads versus 500-700MB, using system WebKit on each platform. All backend logic runs in Rust for performance, enabling future CLI runtime execution of runbooks.
- •Shell history integration: Users can pull commands from years of Atuin CLI history directly into desktop runbooks, bridging the gap between local experimentation and team documentation. The CLI records every shell command, making workflow documentation retroactive and accurate.
Notable Moment
Huxtable reveals that only around 100 of 26,000 CLI users would likely pay for shell history syncing, making it economically unviable as a standalone business despite strong user enthusiasm and minimal infrastructure costs on self-hosted Postgres.
Episode Transcript
All right. Welcome. You are listening to the change log, where each week we interview the hackers, the leaders, and the innovators of the software world. We pick their brains. We learn from their failures. We get inspired by their accomplishments, and we have a lot of fun along the way. On this episode, I'm joined by Ellie Huxtable whose magical shell syncing, searching, and backing up our shell history with ease. Now Eli is tackling the desktop with a tower based app built to help teams make their workflows repeatable, shareable, and reliable. But first, a big thank you to our partners at fly.io, the public cloud built for developers who'd like to ship. We love Fly. You might too. Learn more about it at fly.io. Okay. Eli Huxtable back on the change log. Let's do it. Well, friends, I am here with a new friend of mine, Scott Deaton, CEO of Augment Code. I'm excited about this. Augment taps into your team's collective knowledge, your code base, your documentation, your dependencies. It is the most context aware developer AI, so you won't just code faster. You also build smarter. It's an ask me anything for your code. It's your deep thinking buddy. It's your stand flow antidote. Okay, Scott. So for the foreseeable future, AI assisted is here to stay. It's just a matter of getting the AI to be a better assistant. And in particular, I want help on the thinking part, not not necessarily the coding part. Can you speak to the thinking problem versus the coding problem and the potential false dichotomy there? Couple of different points to make. You know, AIs have gotten good at making incremental changes at least when they understand customer software. So first, and the biggest limitation that these AI's have today, they really don't understand anything about your code base. If you take GitHub Copilot, for example, it's like a fresh college graduate, understands some programming languages and algorithms, but doesn't understand what you're trying to do. And as a result of that, something like two thirds of the community on average drops off of the product, especially the expert developers. Augment is different. We use retrieval augmented generation to deeply mine the knowledge that's inherent inside your code base. So we are a Copilot that is an expert, and they can help you navigate a code base, help you find issues, and fix them, and resolve them over time much more quickly than you can, trying to tutor up a novice on your software. So you're often compared to GitHub Copilot. I gotta imagine that you have a hot take. What's your hot take on GitHub Copilot? I think it was a great one dot o product, and I think they've done a a huge, service in promoting AI, but I think the game has changed. We have moved from AIs that are new college graduates to, in effect, AIs that are now among you the best developers …
Get the full transcript (10,926 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 53-minute episode.
Get The Changelog summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
- Atuin DesktopBy guest
“Ellie Huxtable discusses Atuin Desktop, a new runbook editor that makes team workflows repeatable and shareable, building on the success of Atuin CLI's shell history syncing tool used by 26,000 developers.”
“Built with Tauri instead of Electron, resulting in 20MB downloads versus 500-700MB, using system WebKit on each platform.”
“minimal infrastructure costs on self-hosted Postgres.”
- Atuin CLIBy guest
“building on the success of Atuin CLI's shell history syncing tool used by 26,000 developers.”
“Built with Tauri instead of Electron, resulting in 20MB downloads versus 500-700MB, using system WebKit on each platform.”
More from The Changelog
We summarize every new episode. Want them in your inbox?
Forking Cal.com to closed source (Interview)
Postgres at PlanetScale (Interview)
Canary tokens and digital tripwires (Interview)
From open source hits to OpenAI (Interview)
MCP on Code Mode (Interview)
Similar Episodes
Related episodes from other podcasts
The Vergecast
Jul 3
Our favorite tips for logging off
The Startup Ideas Podcast
Jan 23
Claude Code's Creator Reveals "Claude Cowork"'s Setup
The Bike Shed
Jan 13
489: What makes a codebase welcoming
Stacking Benjamins
Jan 9
Our Annual Magic 8 Ball Predictions for 2026 (SB1788)
The RTW Podcast
Oct 6
14 Months to Treatment: Breaking Records in Rare Disease Therapy
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into The Changelog.
Every Monday, we deliver AI summaries of the latest episodes from The Changelog and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime