Description
When using a non-default Claude profile (e.g. via CLAUDE_CONFIG_DIR or a .claude-* directory), the statusline does not render on first load. It remains blank until the user manually runs /status once — after which it updates normally.
Additionally, the inline stats display resolves to the literal .claude* directory name rather than the actual resolved config path, which can be confusing when multiple profiles are in use.
Steps to reproduce
- Set
CLAUDE_CONFIG_DIR to a non-default path (or have a .claude-work style directory)
- Start a new Claude Code session
- Observe the statusline is blank on the first screen render
- Type
/status — the statusline now appears and continues updating correctly
Expected behavior
The statusline should render immediately on session start without requiring a manual /status trigger.
Related
PR #34 — fixes profile detection and CLAUDE_CONFIG_DIR support, but this first-render issue persists.
Description
When using a non-default Claude profile (e.g. via
CLAUDE_CONFIG_DIRor a.claude-*directory), the statusline does not render on first load. It remains blank until the user manually runs/statusonce — after which it updates normally.Additionally, the inline stats display resolves to the literal
.claude*directory name rather than the actual resolved config path, which can be confusing when multiple profiles are in use.Steps to reproduce
CLAUDE_CONFIG_DIRto a non-default path (or have a.claude-workstyle directory)/status— the statusline now appears and continues updating correctlyExpected behavior
The statusline should render immediately on session start without requiring a manual
/statustrigger.Related
PR #34 — fixes profile detection and
CLAUDE_CONFIG_DIRsupport, but this first-render issue persists.