foreman/agent-watcher
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Fix env var: CLAUDE_CONFIG_DIR not CLAUDE_HOME

Browse source 
Foreman verified by 'strings' on the claude binary that the
sandbox-isolation env var is CLAUDE_CONFIG_DIR, not CLAUDE_HOME
(2026-05-06 sandbox spike).

identity.ts now resolves in this order:
  1. PING_AGENT_IDENTITY
  2. $CLAUDE_CONFIG_DIR/ping-agent  (preferred — what Claude Code reads)
  3. $CLAUDE_HOME/ping-agent         (compat for the previously-documented var)
  4. ~/.ping-agent

Two new tests cover the precedence (CLAUDE_CONFIG_DIR > CLAUDE_HOME)
and the fallback path (CLAUDE_HOME still works when CLAUDE_CONFIG_DIR
is unset). Existing tests updated to use CLAUDE_CONFIG_DIR. 37 tests
pass.

README + install.sh: sandbox launch examples updated to set
CLAUDE_CONFIG_DIR.

Note: agent-ping's identity-resolution PR (#1, merged) has the same
bug and should also be patched. Filing a follow-up.
This commit is contained in:
bob 2026-05-06 18:05:22 -03:00
parent c22558c67a
commit c757af3909
4 changed files with 50 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

2
mcp-watcher/install.sh
View file

@ -106,7 +106,7 @@ Then start Claude Code with the development flag (research preview):
To use a sandbox identity instead of the default ~/.ping-agent:
CLAUDE_HOME=~/.claude-sandbox claude --dangerously-load-development-channels server:agent-watcher
CLAUDE_CONFIG_DIR=~/.claude-sandbox claude --dangerously-load-development-channels server:agent-watcher
(Drop a 'ping-agent' file in ~/.claude-sandbox containing the sandbox name first.)