I must be holding this thing wrong

[luckman212]

• macOS 26.1 26.2
• Atuin Desktop (ARM) v0.2.3 (20251126.213144) 0.2.11 (20251211.225100)

I opened the "Welcome to Atuin" runbook and pressed "play"... a shell opened to an interactive prompt, but nothing else. The echo commands were not executed?

[ellie]

could you tell me a little more about your setup please?

what shell are you using? what config does it have?

[luckman212]

Thanks @ellie

I run macOS 26.1, on two different M4 machines (MacBook Air, Mac Mini). I use Bash (currently v5.3.9 from Homebrew) as my primary shell. Since reporting this problem, I've updated Atuin to the current v0.2.11.

I have a fairly complex ~/.bash_profile with lots of custom functions, aliases, initializers, etc - BUT...

I avoid executing all of that using an "allowlist" based on the parent app's bundleID (__CFBundleIdentifier) or other env vars like XPC_SERVICE_NAME, TERM_PROGRAM, LC_TERMINAL etc. So, Atuin shouldn't be running any of the code beyond the first few lines of my profile. To test and confirm this, I added a simple return statement to the very top, so the shell just bails out immediately.

Strangely, even with that modification, the shells and Terminal blocks in Atuin were still not executing.

On a whim, I added a short delay:

sleep 1
return

After this, things started working! I tested progressively shorter and shorter delays, down to about 0.12 sec. Any shorter than that and Atuin started failing again.

I have no idea WHY this is happening (yet) only that it IS happening.

I made a small screen recording showing this oddity...

atuin1.mp4

[luckman212]

Happy holidays 🌲

Just noting that nothing here has changed as of macOS 26.2.