feat: support ZO-scoped Claude settings at ~/.zo/settings.json - #105
Open
arjvn wants to merge 1 commit into
Open
feat: support ZO-scoped Claude settings at ~/.zo/settings.json#105arjvn wants to merge 1 commit into
arjvn wants to merge 1 commit into
Conversation
Avoid requiring users to edit their global ~/.claude/settings.json to enable agent teams. If ~/.zo/settings.json exists (overridable via ZO_CLAUDE_SETTINGS), the wrapper passes it to every spawned Claude session via --settings, in both the tmux and headless launch paths. setup.sh now accepts the flag in either location and its auto-fixer writes the ZO-scoped file instead of modifying global settings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the install-time requirement to edit the user's global
~/.claude/settings.jsonto enable agent teams. ZO-specific Claude settings now live in a dedicated~/.zo/settings.json.How
src/zo/wrapper.py: newzo_user_settings_path()helper resolves~/.zo/settings.json(path overridable via theZO_CLAUDE_SETTINGSenv var, returnsNonewhen the file is absent). Both launch paths — the tmux interactive command and the headless--printsubprocess — pass it to the Claude CLI via--settings <file>, which loads it as additional settings on top of user/project settings.setup.sh: check 4 now passes ifCLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSis set in either~/.zo/settings.jsonor the global settings file. The auto-fixer creates (or merges into) the ZO-scoped file instead of modifying~/.claude/settings.json; the global-settings fixer arms are removed.Why
--settingsalso travels with the session regardless of cwd, so it covers sessions launched in delivery repos where the ZO project-level.claude/settings.jsondoesn't apply.Testing
ruff check src/zo/wrapper.pycleanbash -n setup.shcleanNonefor missing/override paths🤖 Generated with Claude Code