November 28, 2025
Bashbooks: hype or help?
Atuin’s New Runbook Execution Engine
Runbooks that remember your place—power users swoon, others ask 'why?'
TLDR: Atuin rebuilt Desktop runbooks to keep progress and act consistently, paving the way for shared, real-time execution. The crowd is split: power users gush over automating repeat chores, while others don’t see the need and joke it’s “Jupyter-for-bash,” with questions about Markdown and note-app integration.
Atuin just flipped the switch on a redesigned engine for its Desktop “runbooks” — think step‑by‑step playbooks you can run — and comments lit up. Fans like theoldgreybeard are in love, calling it “wonderful” and turning onboarding and one‑off data chores into shareable checklists. But skeptics like piqufoh shrug: they adore Atuin’s command memory, yet don’t see a problem this solves. And imiric delivers the spiciest line, saying it “sounds completely alien”, like a Jupyter notebook for shell scripts.
Here’s the non‑nerd version of what changed: runbooks now remember where you left off even if you close the app. Steps behave predictably (what you change only affects steps below), and there are templates everywhere — you can even make variables refer to themselves for clever cleanup tricks. There’s “passive” setup (like folders, environment, and connections) and “active” results (the stuff you saw when you ran commands), both saved so teams can aim for real‑time collaboration in the future. Cue drama: some worry older habits may need tweaks, while CLI loyalists like jdorfman still live happily in the terminal. Meanwhile, quasigod’s vibe is “will it marry my Markdown and Obsidian?” The meme: Is this Notion for terminals or a lifesaver?
Key Points
- •Atuin Desktop’s runbook execution engine has been redesigned to provide persistent, predictable execution state.
- •Runbook context now persists across app restarts and tab closures, reducing the need to re-run blocks.
- •Blocks can only influence those below them, enforcing reproducible execution and preventing upward variable effects.
- •All user inputs are templated, enabling self-referential variables and broader template usage across blocks and contexts.
- •Two context types—Passive and Active—are introduced, with controls to clear active context and groundwork for future collaborative execution.