For anyone emacs-curious, you can do a similar thing with org-babel

You can have a plaintext file which is also the program which is also the documentation/notebook/website/etc. It's extremely powerful, and is a compelling example of literate programming.

A good take on it here: https://osem.seagl.org/conferences/seagl2019/program/proposa...

I took a stab at this ~7 years ago - https://nurtch.com/

The idea has a lot of merit. We even gave a talk about it in JupyterCon Paris 2023 - https://www.youtube.com/watch?v=TUYY2kHrTzs

When you have executable code in the documentation, folks want to follow PR-review workflow with the docs as well - which is a bit more team investment than editing a wiki.

Good luck!

This is exactly what I wanted for our team when I was at AWS. There are so many versions of operations which are just slightly too dangerous to automate, and this provides a path to iteratively building that up. Congratulations!

If it's local-first then it's already subject to rot. Unless they're running it all in containers? In which case local doesn't matter.

If you want to record a runbook, then record a runbook. You can do that a million ways. Text file, confluence doc, screen recording, shell script, etc. People already don't do that; they're not gonna suddenly start doing it more because your UI is fancier.

Personally, I don't want to sit around all day writing code (or docs) to try to get the system to be like X state. I want to manually make it have X state, and then run a tool to dump the state, and later re-run the tool to create (or enforce) that state again. I do not want to write code to try to tell the computer how to get to that state. Nor do I want to write "declarative configuration", which is just more code with a different name. I want to do the thing manually, then snapshot it, then replay it. And I want this to work on any system, anywhere, without dependence on monitoring a Bash shell for commands or something. Just dump state and later reapply state.

How is this different from a local Jupyter notebook? Can we not do this with ! or % in a .ipynb?

Genuine question. Not familiar with this company or the CLI product.

Looks interesting!

We recently started using https://marimo.io/ as a replacement for Jupyter notebooks, as it has a number of great improvements, and this seems like a movement in a similar direction.

This looks super similar to https://runme.dev

I can't say I see the point in this. Can someone explain what I'm missing? Why would I use this over a simple shell script?

Will this be open source like Atuin CLI and the sync server are? Is this going to be productized?

It's kind of sad the direction they took. The last thing I want is my runbooks being held hostage by my desktop with proprietary and possibly paid software.

i think lots of tools try to solve the same mess and i always end up just wanting my stuff all in one place with less hassle, so seeing more takes on this is cool

My dream tooling is for every tool to have an terminal interface so that I can create comprehensive megabooks to get all the context that lives in my head. i.e. jira, datadog, github etc, all in one pane.

This reminds me of xiki which seems to have kind of died on the vine.

Is it opensource?

pretty sure obsidian already has an extension for this

Congratulations on the launch! I've been following Atuin for a bit and, while I'm not necessarily the intended audience for this runbook feature, love seeing people build fun new things.

Looks neat. What tech stack is used for this? Is it open source by chance?

Have been following along with the development, glad to see it announced!

Our team used polyglot notebooks https://marketplace.visualstudio.com/items?itemName=ms-dotne...

Using C# as main language this allowed us to have runbooks using code shared as nuget package and so being able to interact with our own APIs and applications as any other code that runs in production.

Not the best experience to review but it worked for us.

+1 for the Sir Terry reference!

This sort of slogan says nothing about what actually makes it worth looking into.

This makes me think of using org mode to build runbooks.

Oh, that's really neat! Thanks for sharing!

Cool name, a reference to well known books

the waitlist social media jump the list mechanic is kinda sus, regardless joined the waitlist

This looks so dope!

I'm really confused by products like this and Warp Drive[0]. What does this add over a shell script?

There is a response elsewhere in comments[1] which claims that this is trying to fix the problem of bad documentation, but this has the same fundamental problem. If you a) are responsible for fixing something, b) are unfamiliar with it, and c) the "fixing resources" - whether those are scripts, documentation, or a Runbook/Workflow - you were provided with by the experts are out-of-date; you're SOL and are going to have to get to investigating _anyway_. A runbook and a script are just different points along the spectrum of "how much of this is automated and how much do I have to copy-paste myself?"[2] - both are vulnerable to accuracy-rot.

[0]: https://www.warp.dev/warp-drive

[1]: https://news.ycombinator.com/item?id=43766842

[2]: https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-...

Kinda related but just the other day I was thinking of the notebook/runbook workflow and wonder if there is a tool like this that also incorporates git checkpoints (either commit or stash) into it. Like top to bottom, associate all the blocks and resulting artifacts with a commit hash. Might be something to vibe code over the weekend.

All the problems of reproducibility in Python notebooks (https://arxiv.org/abs/2308.07333, https://leomurta.github.io/papers/pimentel2019a.pdf) with the power of a terminal.

[dead]