ferrox-config

name	ferrox-config
description	You want to change how Ferrox behaves. Workflow toggles, advanced knobs, integrations
argument-hint	[--advanced | --integrations | --profile <name>]
allowed-tools	["Read","Write","Bash","AskUserQuestion"]

Configure Ferrox settings interactively with a single consolidated command.

Mode routing:

• default (no flag): Common-case toggles (model, research, plan_check, verifier, branching) → settings workflow
• --advanced: Power-user knobs (planning tuning, timeouts, branch templates, cross-AI execution) → settings-advanced workflow
• --integrations: Third-party API keys, code-review CLI routing, agent-skill injection → settings-integrations workflow
• --profile : Switch model profile (quality|balanced|budget|inherit) → set-profile (inline)

Flag	Action	Workflow
(none)	Interactive 5-question common-case config prompt	settings
--advanced	Power-user knobs: planning, execution, discussion, cross-AI, git, runtime	settings-advanced
--integrations	API keys (Brave/Firecrawl/Exa), review CLI routing, agent skills	settings-integrations
--profile <name>	Switch model profile without interactive prompt	ferrox-tools query config-set-model-profile

<execution_context> @/.claude/ferrox-core/workflows/settings.md @/.claude/ferrox-core/workflows/settings-advanced.md @~/.claude/ferrox-core/workflows/settings-integrations.md </execution_context>

Arguments: $ARGUMENTS

Parse the first token of $ARGUMENTS:

• If it is --advanced: strip the flag, execute settings-advanced workflow
• If it is --integrations: strip the flag, execute settings-integrations workflow
• If it starts with --profile: extract the profile name (remainder after --profile), then:
  1. Verify ferrox-tools is on PATH via command -v ferrox-tools; if absent, emit the install hint Install Ferrox via 'npm i -g ferrox-core' and stop.
  2. Run: ferrox-tools query config-set-model-profile <profile-name> --raw and display the output verbatim.
• Otherwise: execute settings workflow (no argument needed)

1. Parse the leading flag (if any) from $ARGUMENTS. 2. Load and execute the appropriate workflow end-to-end, or run the inline SDK command for --profile. 3. Preserve all workflow gates from the target workflow.