Status: compatibility and agent-curated setup path. For manual install, prefer apx install claude or apx install claude --full. This document describes what apx setup claude-code still does; it is not an official Claude Code integration claim.
apx setup claude-code supports three modes via --mode:
| Mode | Assets installed | Use when |
|---|---|---|
minimal |
6 bootstrap skills + 2 commands | Bootstrap awareness only |
recommended |
Core skills + dev-loop plugins | Main agent setup (recommended) |
full |
All skills, commands, plugin bundles, hooks, MCP configs (staged) | Broad agent-assembled environment |
Default (--yes alone) is minimal. MCP configs are staged in full mode but never enabled automatically.
# Dry-run (default — no files written)
apx setup claude-code
# Apply minimal
apx setup claude-code --yes
# Apply recommended (main agent setup)
apx setup claude-code --mode recommended --yes
# Apply full
apx setup claude-code --mode full --yesFor agents: Prefer --mode recommended --yes. Use apx profiles list to see available skill sets after setup.
Default root:
%USERPROFILE%\.claude
Override with:
apx setup claude-code --agent-root <path> --dry-runIf CLAUDE_CONFIG_DIR or CLAUDE_HOME is set, setup uses the first value found.
Directories created depend on the selected mode.
minimal and recommended modes create:
agent-powerups/
agent-powerups/skills/
agent-powerups/commands/
agent-powerups/instructions/
recommended also creates agent-powerups/plugins/.
full mode additionally creates:
agent-powerups/mcp/
agent-powerups/agents-md/
agent-powerups/hooks/
agent-powerups/workflows/
If the target directory does not exist, --yes creates it. --dry-run only reports it.
Files copied depend on the selected mode. See Setup Modes above.
In full mode (default for --yes in previous versions), setup copies:
skills/toagent-powerups/skills/commands/generic/toagent-powerups/commands/generic/commands/claude-code/toagent-powerups/commands/claude-code/mcp/generic/toagent-powerups/mcp/generic/mcp/claude-code/toagent-powerups/mcp/claude-code/agents-md/toagent-powerups/agents-md/hooks/toagent-powerups/hooks/workflows/toagent-powerups/workflows/docs/setup/toagent-powerups/docs/setup/
Setup also generates:
agent-powerups/instructions/agent-powerups.md
Existing copied files are not overwritten. Identical files are skipped. Different existing files are skipped and reported for manual review.
Default instruction candidate:
<claude-root>/CLAUDE.md
If the file exists, --yes appends or refreshes one marked block:
<!-- BEGIN agent-powerups -->
...
<!-- END agent-powerups -->
If the file does not exist, setup does not guess-create global instructions. It writes the block to agent-powerups/instructions/agent-powerups.md and reports the manual step.
Use a specific file with:
apx setup claude-code --instructions-file <path> --yesDefault behavior is dry-run:
apx setup claude-code
apx setup claude-code --dry-runDry-run reports planned directories, copied files, skipped files, instruction changes, backups, and manual steps. It changes no files.
Non-dry-run requires:
apx setup claude-code --yes--dry-run and --yes cannot be combined.
Before editing an existing instruction file, setup creates:
<instruction-file>.<UTC timestamp>.bak
No backup is created when the instruction block is already present and no edit is needed.
- Remove the
agent-powerups/directory under the Claude Code root. - If an instruction file was modified, restore the
.bakfile over the edited file. - Remove the
github-localserver entry from.mcp.jsonif you enabled it.
- GitHub MCP is copied for review; enable it with
apx mcp check,apx mcp smoke, andapx mcp install github-local --target claude-code --yesonly after approval. - Shell profiles are not changed.
- External tools are not installed.
- Compatibility is limited to local files and user-reviewed instructions.
- Do not write secrets into copied MCP config.
- Set tokens such as
GITHUB_TOKENorGITHUB_PATin the local shell/session only. - Review all copied skills and hooks before trusting them in privileged workspaces.