feat(cli): add user-scoped host setup#23
Open
OpenAIBot1 wants to merge 1 commit into
Open
Conversation
Add a backwards-compatible --scope user mode for Claude Code and Codex. Register Zenith in each host's user config, install managed host assets and a personal /zenith skill, and preserve model, effort, sandbox, feature, and unrelated MCP settings.\n\nKeep project scope as the default, document both modes, and cover config compatibility, idempotency, cross-host ordering, failure safety, and runtime launch.
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
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.
Summary
zenith init --scope userfor deterministic cross-workspace setup in Claude Code and Codex/zenithskill while preserving unrelated user configurationUser scope deliberately does not select or persist a model, reasoning effort, sandbox mode, feature preference, or ambient API/model environment variable. Existing project-scope behavior is unchanged.
This turns the global-skill direction introduced in #5 into a tested CLI workflow. Hermes remains available through project scope until its authoritative user-scope paths are established.
Closes #22.
Compatibility
~/.claude.jsonor$CLAUDE_CONFIG_DIR/.claude.json$CODEX_HOME/config.toml(default~/.codex/config.toml)Validation
uv run ruff check .uv run mypy srcuv run pytest -q— 217 passed, 7 skippedclaude mcp get zenithreported user scope and connectedcodex mcp get zenithreported the server enabledChecklist
uv run ruff check .passesuv run mypy srcpassesuv run pytest -qpasses