Problem
zenith init currently stages MCP configuration, prompts, agents, and skills inside one target workspace. Users who want Zenith across many workspaces must repeat initialization and restart each host for every workspace.
Proposal
Add an explicit user-scoped setup mode:
uv run zenith init --scope user --agent claude
uv run zenith init --scope user --agent codex
The existing project-scoped behavior remains the default for compatibility.
User scope registers the host's user-level MCP server and managed Zenith assets, honors CLAUDE_CONFIG_DIR and CODEX_HOME, preserves unrelated user configuration, and never selects or overwrites model/reasoning/sandbox/feature preferences or persists ambient API/model environment variables. It is idempotent and supports installing both hosts in either order.
Hermes retains project scope until its authoritative user-scope paths are established.
Problem
zenith initcurrently stages MCP configuration, prompts, agents, and skills inside one target workspace. Users who want Zenith across many workspaces must repeat initialization and restart each host for every workspace.Proposal
Add an explicit user-scoped setup mode:
The existing project-scoped behavior remains the default for compatibility.
User scope registers the host's user-level MCP server and managed Zenith assets, honors
CLAUDE_CONFIG_DIRandCODEX_HOME, preserves unrelated user configuration, and never selects or overwrites model/reasoning/sandbox/feature preferences or persists ambient API/model environment variables. It is idempotent and supports installing both hosts in either order.Hermes retains project scope until its authoritative user-scope paths are established.