futpib / slopd / 26833813132

86%

Build Type

push

github

Committed by futpib

Commit Message

feat: support multiple Claude accounts in slopd

Run panes under different Claude config dirs. Accounts are named under [accounts] (a bare config dir, or a table for future per-account options); the reserved "default" account is backed by the top-level claude_config_dir (or ~/.claude), so existing single-account configs keep working.

Select an account per pane with `slopctl run --account <name>`. Without the flag the pane inherits the parent pane's account (read from its @slopd_account tmux option — no extra env var), then slopd's default_account, then "default". The account is shown in `slopctl ps`.

Hooks are injected into the resolved account's settings.json, and each pane records its account, so a slopd restart re-injects the right hooks and resumes transcript tailing from the account's relocated JSONL. Startup recovery falls back to the reserved default account when a pane's account can't be resolved (a removed account, or a misconfigured default_account), so a bad default_account fails individual runs without crashing the daemon. An unknown account fails the run (listing configured accounts) before any pane is spawned.

Covered by unit tests (resolution, ~/$VAR expansion, default mapping, dedup, reserved-default invariant) and integration tests: account in ps, default mapping, parent-pane inheritance, flag override, unknown account, per-account hook isolation, transcript discovery/tailing/streaming/read + restart recovery, concurrent panes on different accounts, recovery re-injection into the account dir, shutdown cleanup across accounts, SIGHUP picking up a new account, bad default_account, and uninject-hooks across accounts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Coverage Stats

294 of 300 new or added lines in 4 files covered. (98.0%)

11 existing lines in 3 files now uncovered.

3976 of 4603 relevant lines covered (86.38%)

2332920.23 hits per line