Claude Code Templates explained: configuration catalog, not a model runtime
Claude Code Templates architecture: CLI options route to different subsystems
Trace Commander options into installation, dashboards and host execution.
What you will learn
- Start at the executable mapping
- Read dispatch order
- Separate configuration and execution
Before you start
- Basic npm and Git knowledge
- Disposable project and preserved configuration
Track provenance and file changes without executing the installed instructions.
Key takeaways
- Several aliases share one executable.
- Option combinations affect routing.
- A dispatch review is not a full subsystem audit.
Start at the executable mapping
package.json maps several command aliases to bin/create-claude-config.js. That entry point declares options with Commander and passes the parsed object to createClaudeConfig. Multiple names do not imply separate implementations.
The entry point also catches errors, prints a message and invokes error reporting. This series does not audit that reporting transport; review its data policy before using sensitive project context.
Read dispatch order
createClaudeConfig determines the target directory, checks tunnel option combinations, then handles Studio and sandbox paths before component installation. Specific component flags route to installMultipleComponents and return.
A workflow flag combined with component flags is assigned to options.yaml for that branch; a workflow without those flags takes a different installer path. Flag combinations can therefore change meaning, not just add independent features.
Separate configuration and execution
Other paths launch analytics, chat views, diagnostics or global-agent management. The --prompt option can request host execution after installation or in a sandbox path. Do not confuse browsing a catalog with executing a task.
This is a dispatch-level review, not a complete audit of all installers, dashboards or sandbox providers. Check the exact branch used by your command before relying on its safety or output contract.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Follow aliases to the shared entry point.
- 2
Identify the branch selected by your options.
- 3
Separate installation from dashboards and execution.
Copy-ready example
command alias -> Commander -> createClaudeConfig
component flags -> installMultipleComponents
workflow alone -> installWorkflow
dashboard flags -> separate UI subsystemsFrequently asked questions
Does --workflow always mean the same input?
The inspected router treats it differently when specific component flags are also present.
Were all dashboards audited?
No. Only their dispatch paths were inspected.
Sources
- Claude Code Templates / cli-tool/package.jsonSource checked 2026-09-23
- Claude Code Templates / cli-tool/bin/create-claude-config.jsSource checked 2026-09-23
- Claude Code Templates / cli-tool/src/index.jsSource checked 2026-09-23