[BUG] Custom shell setting not working

[Daeraxa]

Bug Description

Setting a custom shell does not seem to take effect in any terminal blocks

Steps to Reproduce

1. Set Settings > Runbooks > Terminal > Custom shell to another terminal on the system (e.g. /usr/bin/fish or /usr/bin/zsh)
2. Check setting has applied (and is present in kv.db)
3. Run a terminal block and check which shell is running

Expected Behavior

Terminal should be in the chosen shell

Actual Behavior

Original default shell runs

Environment

• OS: Fedora 43
• Atuin Desktop Version: 0.2.20
• Atuin CLI Version: atuin 18.13.6 (e0d97af547ccbe4bcfdae64b97746ac2eecdf6fb)
• Shell: fish (also tested with zsh)
• Terminal: Ghostty

Screenshots/Logs

Terminal block:

ps
sqlite3 ~/.config/sh.atuin.app/kv.db "select value from kv where key = 'settings.runbooks.terminal.shell'"
/usr/bin/fish
ps

Output:

dae@yoga-fedora:~$ ps
    PID TTY          TIME CMD
 129996 pts/4    00:00:00 bash
 130370 pts/4    00:00:00 ps
dae@yoga-fedora:~$ sqlite3 ~/.config/sh.atuin.app/kv.db "select value from kv where key = 'settings.runbooks.terminal.shell'"
"/usr/bin/fish"
dae@yoga-fedora:~$ /usr/bin/fish

-> dae ~
❯ ps
    PID TTY          TIME CMD
 129996 pts/4    00:00:00 bash
 130408 pts/4    00:00:00 fish
 130707 pts/4    00:00:00 ps

-> dae ~
❯ 

Additional Context

First time I've used the desktop app I'm afraid and I well could be making a mistake or not understanding something here. My default shell is still bash which correctly loads but it just doesn't seem to respect a custom shell added to the settings. It isn't a fault with fish as I get identical behaviour with zsh. Setting the script default shell option does seem to work without any issues, just not the terminal.

I have also tried it with and without the Ghostty terminal option and it doesn't seem to change anything.

Workaround

None, other than adding the shell to the top of the terminal block code