Does not detect claude instances if claude's directory is a custom path

[hmenzagh]

Context

I use two separate Claude Code configurations:

• ~/.claude for my personal plan
• ~/.claude-pro for my enterprise plan

I switch between them using aliases like:

alias claude-pro='CLAUDE_CONFIG_DIR=~/.claude-pro claude'

Problem

abtop seams to hardcode the sessions and projects directories to ~/.claude/sessions and ~/.claude/projects.

When I launch Claude from my enterprise configuration (CLAUDE_CONFIG_DIR=~/.claude-pro), abtop does not detect the running sessions because it keeps looking in ~/.claude/ instead of ~/.claude-pro/.

Expected behavior

abtop should respect the CLAUDE_CONFIG_DIR environment variable — which is the official Claude Code mechanism for overriding the config directory — and use it to resolve the sessions and projects paths at startup.

For example, if CLAUDE_CONFIG_DIR=~/.claude-pro is set, abtop should look in ~/.claude-pro/sessions and ~/.claude-pro/projects.

Suggested fix

In src/collector/claude.rs, the ClaudeCollector::new() function currently does:

let home = dirs::home_dir().unwrap_or_default();
Self {
    sessions_dir: home.join(".claude").join("sessions"),
    projects_dir: home.join(".claude").join("projects"),
    ...
}

It could be updated to check for CLAUDE_CONFIG_DIR first:

let base = std::env::var("CLAUDE_CONFIG_DIR")
    .map(PathBuf::from)
    .unwrap_or_else(|_| dirs::home_dir().unwrap_or_default().join(".claude"));
Self {
    sessions_dir: base.join("sessions"),
    projects_dir: base.join("projects"),
    ...
}

This would make abtop consistent with how Claude Code itself handles multi-account setups.

[graykode]

Thanks for the detailed report and suggested fix! This makes total sense — CLAUDE_CONFIG_DIR is the official mechanism for overriding the config directory, and abtop should respect it.

I'll get a fix out for this shortly.

[graykode]

@hmenzagh release @ v0.2.6!

[hmenzagh]

@graykode

Works great, thanks for the quick fix! 🎉

One remaining issue though: running CLAUDE_CONFIG_DIR=~/.claude-pro abtop --setup appears to complete successfully (with the provided dirrectory), but the QUOTA column stays unavailable in the UI afterwards.

The session detection now works correctly with CLAUDE_CONFIG_DIR — only the quota fetching via --setup seems unaffected by the env var. Could it be that --setup still reads/writes credentials from the default ~/.claude path instead of the custom one?

EDIT: I just took a look at your PR, this should work, weird

[graykode]

Thanks! I reopened this issue

[graykode]

@hmenzagh I took another look at this — the code paths all correctly respect CLAUDE_CONFIG_DIR for both writing and reading the rate limit file. Could you double check:

1. Is CLAUDE_CONFIG_DIR set in the shell where Claude Code is actually running (not just the shell where you ran abtop --setup)?
2. After a Claude response, does ~/.claude-pro/abtop-rate-limits.json exist and have recent data?
3. Is CLAUDE_CONFIG_DIR also set in the shell where you run abtop?

All three need to see the same CLAUDE_CONFIG_DIR for quota to show up. If you can confirm these, we can dig deeper. Otherwise happy to close this if it's working now!