Stats
Actions
Tags
Set up codebase-agent dependencies. Run this once after installing the plugin.
How this command is triggered — by the user, by Claude, or both
Slash command
/codebase-agent-plugin:setupThe summary Claude sees in its command listing — used to decide when to auto-load this command
Check if `${CLAUDE_PLUGIN_ROOT}/.venv/bin/python` exists using Bash.
If it already exists:
- Tell the user: "Dependencies are already installed. You're ready to go — say 'index this project' to get started."
- Stop here.
If it does NOT exist:
- Tell the user: "I need to install Python dependencies for codebase-agent (~30 seconds). Shall I proceed?"
- Wait for user approval
- If approved, run: `bash ${CLAUDE_PLUGIN_ROOT}/hooks/setup.sh` and show the full output
- When complete, tell the user: "Setup done! Say 'index this project' to get started."Check if ${CLAUDE_PLUGIN_ROOT}/.venv/bin/python exists using Bash.
If it already exists:
If it does NOT exist:
bash ${CLAUDE_PLUGIN_ROOT}/hooks/setup.sh and show the full outputnpx claudepluginhub enviees/codebase-agent --plugin codebase-agent/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupInteractive setup wizard that detects installed AI providers, configures authentication, and optimizes token usage. Auto-runs on first install and surfaces a status dashboard on manual invocation.