abtop does not recognize and use CLAUDE_CONFIG_DIR env var

[abrose]

I'm using multiple claude subscriptions - one from my current client and one personal. In order to keep the separate I'm using direnv - setting CLAUDE_CONFIG_DIR in the client's workspace to something like this

export CLAUDE_CONFIG_DIR="$HOME/.claude-profiles/clientA"

In my private workspaces this env var is set to

export CLAUDE_CONFIG_DIR="$HOME/.claude"

abtop seems to only consider the default claude config dir, not the custom ones. Would be really great if this worked too!

Alfred

[graykode]

Thanks for the report! abtop actually does respect CLAUDE_CONFIG_DIR since v0.2.5 — but it only reads the env var from its own process environment.

So this already works as a workaround:

CLAUDE_CONFIG_DIR=~/.claude-profiles/clientA abtop

This will monitor sessions in that specific profile directory.

However, what you're really asking for is multi-profile monitoring — abtop discovering and showing sessions from all active Claude profiles simultaneously. That's a bigger feature that would require either:

1. Scanning running Claude processes and detecting their CLAUDE_CONFIG_DIR from each process's environment
2. Accepting multiple config dirs via CLI flag (e.g. abtop --config-dirs ~/.claude,~/.claude-profiles/clientA)

We'll look into supporting this properly. For now, you can run abtop with the CLAUDE_CONFIG_DIR pointing to whichever profile you want to monitor.

[abrose]

btw, i reinstalled abtop using homebrew and there it recognized that I'm in a custom profile. So maybe the cargo version hasn't been up to date

[graykode]

@abrose Hey! Just wanted to check — which version of abtop are you running? The current version already reads the CLAUDE_CONFIG_DIR environment variable, so if you launch abtop from a shell where it's set, it should pick up the right config directory. If it's working for you now, we'd like to close this issue. Let us know!

[abrose]

I'm on 0.2.9 now, working now! Thank you very much!