Atuin Desktop: Runbooks That Run

Summary

News Atuin Desktop: Runbooks that Run Atuin Desktop looks like a doc, but runs like your terminal. Script blocks, embedded terminals, database clients and prometheus charts - all in one place. Most infrastructure is held together by five commands someone remembers when shit breaks. Docs are out of date, if they exist. The real answers? Buried in Slack threads, rotting in Notion, or trapped in someone's shell history.Atuin CLI fixed part of this, with synced, searchable shell history. But teams need more than history. They need workflows that don't live in someone's head (or their shell).Set up. SSH in. Export some variables. Run some commands. Hope nothing breaks. Stuff we do every day, but still have to piece together from fragments of the past, or copy paste from some document somewhere.That's why we built the next step.Introducing Atuin DesktopA local-first, executable runbook editor for real terminal workflowsBuilt to make workflows repeatable, shareable, and reliable.Runbooks should run. Workflows shouldn't live in someone's head. Docs shouldn't rot the moment you write them.Atuin Desktop looks like a doc, but runs like your terminal. Script blocks, embedded terminals, database clients and prometheus charts - all in one place.Kill context switching: chain shell commands, database queries and HTTP requestsDocs that don't rot: execute directly + stay relevantReusable automation: dynamic runbooks with Jinja-style templatingInstant recall: autocomplete from your real shell historyLocal-first, CRDT-powered: if it runs in your terminal, it runs in a runbookSync and share with Atuin Hub: up to date, across devices and teamsHow we use it todayWe’re already running real-world workflows in Atuin Desktop:Releasing Atuin CLI (no more checklist hell)Migrating infra safely between environmentsSpinning up staging or prod with confidenceManaging and collaborating on live database queriesThis is how we ship, manage infra, and collaborate.What’s nextTeam accounts: true collabora...