Claude Code Cli Builder
Claude Code Cli Builder tool
About Claude Code CLI Builder
A visual composer for `claude` (Claude Code) command-line invocations. Instead of memorizing flags, you browse the full CLI parameter catalog (with descriptions and type-aware inputs), toggle flags on or off, drag them into the order you want, optionally attach a subcommand and a prompt, and read the assembled command in a live preview. You can also apply one of several presets and persist your composed commands to browser-local storage for later reuse.
How to Use
1. (Optional) Click a Preset button at the top — e.g. Quick Debug, Safe Mode, Auto Approve, Minimal, or Continue Last — to seed a ready-made parameter set. 2. In the Parameter Browser (left), use the search box and the category dropdown (session, model, permissions, tools, prompt, io, debug, integration, worktree, other) to find a flag, then click it to add it to Selected Parameters on the right. 3. In Selected Parameters, set each flag's value using its type-aware control (checkbox for boolean, dropdown for enum, number input for number, textarea for json/array, text input for string). Drag the grip handle to reorder flags; click the trash icon to remove one. 4. (Optional) Pick a Subcommand (agents, auth, auto-mode, doctor, install, etc.) from the dropdown. 5. (Optional) Type a Prompt into its card; it will be wrapped in double quotes at the end of the command. 6. Use Copy Command to copy the assembled string, or Save to name and store it locally. Saved commands appear under Saved History with Load / Copy / Delete actions and a Clear All option.
Command Generation Rules
The generated string is built as: `claude [subcommand] [subcommand-params] [selected-params] "prompt"`, joined by spaces, in the exact order of your selected-params list (which is why drag-to-reorder matters). - Boolean flags render as a bare token when enabled (e.g. `--debug`), and are omitted when disabled. - Enum, number, string, json, and array params render as `--flag value` (value coerced to a string). Empty-string and false values are skipped entirely. - The prompt, if non-empty, is appended last and wrapped in double quotes. Examples: `claude --debug --verbose "fix the login bug"` (Quick Debug preset + prompt); `claude --permission-mode dontAsk "refactor utils"` (Safe Mode preset + prompt); `claude doctor` (subcommand only).
▶Where are my saved commands stored?
▶Why does nothing happen when I click Save with an empty configuration?
▶Does the tool execute the generated command for me?
▶Is my data sent to a server?
If this tool has been helpful to you, consider buying me a coffee.
Buy me a coffee