fix(server): use CLAUDE_CONFIG_DIR instead of HOME for Claude instanc… - #4017
juliusmarminge merged 5 commits into
Effect Service Conventions: No issues found
All clear
Details
Note
Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.
The PR renames the Claude isolation environment variable from HOME to CLAUDE_CONFIG_DIR (to avoid relocating the macOS keychain lookup) and updates the associated tests and settings schema title/description. The touched service module (ClaudeHome.ts) continues to follow Effect conventions: subpath namespace imports (effect/Effect, effect/Path), Effect.fn constructors, and no service/error/layer refactoring is involved. No Effect service convention violations were introduced or retained in the changed scope.
🔍 Agent activity — reasoning, no tool calls
💭 I'm looking at a PR that renames HOME to CLAUDE_CONFIG_DIR in the Claude environment configuration. The changes appear to be mostly in test files and a small update in ClaudeHome.ts along with a settings schema change, so there shouldn't be any Effect service convention violations to worry about. The code follows Effect conventions properly with the right namespace imports and uses Effect.fn correctly, so there are no service convention violations here. The behavioral change is just renaming the environment variable to CLAUDE_CONFIG_DIR. I need to make sure the response follows the JSON schema format as specified in the instructions, though the check body seems to be cut off mid-sentence.