speci init

Initialise speci in an existing project. Creates speci.config.json, sets up copilot.models from the live Copilot model list, and copies the built-in agent templates into .github/agents/.

Usage

speci init [-u] [-v] [-m]

Options

Model selection

On first init (or when running with -m, --reconfigure-models), speci fetches the live Copilot model list, validates the current copilot.models entries, and presents an interactive menu to configure them:

? Choose a model configuration:
  1. Best-in-Class
  2. Balanced (default)
  3. Budget-Friendly
  4. Custom (one-by-one)

• Presets (1-3) — assign the best available model to each role automatically according to your preference.
• Custom (4) — prompts you to pick a model for each of the seven roles: plan, task, refactor, impl, review, fix, and tidy.
• Startup validation — if a saved model is no longer available from the live Copilot list, speci warns and offers remediation: replace the offending roles, apply the Balanced preset, or skip and continue.

When reconfiguring with -m, your current model assignments are displayed before prompting. In non-interactive (CI) environments the Balanced preset is applied automatically.

Local/self-hosted model routing

If your project includes a copilot.localModel config, the custom model picker adds the local model as an extra choice per role. A role routes to the local endpoint only when its copilot.models.<role> value matches copilot.localModel.model. In that case, speci injects COPILOT_PROVIDER_BASE_URL, COPILOT_MODEL, COPILOT_PROVIDER_TYPE, and COPILOT_PROVIDER_API_KEY for just that single invocation, while the rest of the roles keep their normal cloud model selection and live validation.

What it creates