No commands recorded on immutable Linux OS (Fedora Atomic)

Environment

OS: Fedora 43 (immutable/atomic variant)
Kernel: 6.17.7-ba25.fc43.x86_64
Shell: /bin/bash
wake-mcp location: ~/.local/bin/wake-mcp
Home directory: /var/home/user1 (not /home/User1)

Problem

Wake starts a session successfully but no commands are ever recorded. wake_list_commands and wake_log always return "No commands recorded yet", even after running commands in the terminal.

wake_status output

Session: c3221c04-927b-4e53-81f2-84b633853d44 (active)
Started: 2026-01-31 20:16:33
Shell: /bin/bash
Commands: 0

Steps to reproduce

Install wake on an immutable Fedora OS (Silverblue, Kinoite, Bazzite, etc.)
Add shell hook to .bashrc: eval "$(wake init bash)"
Register MCP server
Start wake shell or a new terminal
Run some commands
Check wake_log — no commands recorded

On immutable Fedora variants, home directories live under /var/home/username. /home is a symlink to /var/home.

My best guess it the shell hooks aren't firing or are failing silently. Let me think about how I can repro your environment and also test the bash setup a bit more (i'm primarily on zsh).

Will post any learnings/findings along the way.

Can you run the following inside of a wake shell:

1. Is the hook defined?

type __wake_preexec 2>/dev/null || echo "HOOK NOT DEFINED"

2. Where is the wake init line?

grep -l "wake init" ~/.bashrc ~/.bash_profile 2>/dev/null || echo "NOT FOUND IN EITHER"

3. What path does the hook use vs where wake actually is?

wake init bash | grep -o '"[^"]*wake"'
which wake

4. Check the actual binary path

readlink -f "$(which wake)"

My best guess from spinning up a container that mimics your environment is that SHELL is set as a shell variable but not exported to the environment which would mean this line result in incorrect behavior by falling back to /bin/sh which doesn't source .bashrc afaik.

Before starting a wake shell if you run the following, what's the output

printenv SHELL || echo "SHELL not in environment"

If it prints "SHELL not in environment", that confirms my hypothesis and I'll need to update the line linked above to be more defensive and probably fall back to /etc/passwd.

If it prints /bin/bash, then i'm not entirely sure what's going wrong.

To confirm my hypothesis, you could try the following:

export SHELL                                                                                                                                                                                                                               
wake shell                                                                                                                                                                                                                                 
# run a command                                                                                                                                                                                                                 
wake log

Here's my reproduction setup #11

fix: read user shell from /etc/passwd when SHELL env var not set

k, the repro branch (#11) now has a fix for what I believe is the issue. The scripts/repro-issue-10.sh confirms the fix.

I'll merge that once you respond with confirmation of my hypothesis and push a new version/release.

Hello,

thanks for your help here are the commands output

before wake shell

printenv SHELL || echo "SHELL not in environment"
/bin/bash

inside wake shell

printenv SHELL || echo "SHELL not in environment"
HOOK NOT DEFINED

grep -l "wake init" ~/.bashrc ~/.bash_profile 2>/dev/null || echo "NOT FOUND IN EITHER"
NOT FOUND IN EITHER

wake init bash | grep -o '"[^"]*wake"'
"/var/home/jey/.local/bin/wake"

readlink -f "$(which wake)"
/var/home/jey/.local/bin/wake

K, this command/output is telling

grep -l "wake init" ~/.bashrc ~/.bash_profile 2>/dev/null || echo "NOT FOUND IN EITHER"
NOT FOUND IN EITHER

So while I see in your "Steps to reproduce" step 2 you are adding the hooks to your shell, they don't appear to be there per the grep.

So, concretely, you are missing eval "$(wake init bash)" in your .bashrc (see Setup instructions)

To confirm, what's the output of

cat ~/.bashrc | grep -i wake

Either:

It's not there (my money is here)
It IS there and my grep cmd failed? (seems unlikely)

Just run echo 'eval "$(wake init bash)"' >> ~/.bashrc and then wake shell (which spawns bash, sourcing the ~/.bashrc automatically). You should be good to go.

Ahh you are right, sorry for the confusion a big PEBKAC -_- Regards, Jeremy RONK

…

On Sunday, February 1st, 2026 at 20:11, Joe McKenney ***@***.***> wrote: joemckenney left a comment [(joemckenney/wake#10)](#10 (comment)) Just run echo 'eval "$(wake init bash)"' >> ~/.bashrc and then wake shell (which spawns bash, sourcing the ~/.bashrc automatically). You should be good to go. — Reply to this email directly, [view it on GitHub](#10 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AGCJKNHY2I5UV32CBBQJ4B34JZFVTAVCNFSM6AAAAACTRWOEWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMZRG44DKMZXGU). You are receiving this because you authored the thread.Message ID: ***@***.***>

Navigation Menu

Repository navigation

No commands recorded on immutable Linux OS (Fedora Atomic) #10