Skip to content

tooling-setup.md

Latest commit

 

History

History
115 lines (86 loc) · 3.79 KB

tooling-setup.md

File metadata and controls

115 lines (86 loc) · 3.79 KB
Raw

Tooling Setup

AWF can now help you inspect, bootstrap, and configure only the adapters and MCP sources you actually have.

First-run flow

Use bootstrap-repo when you want one command to initialize .wi/, detect installed CLIs, configure the repo, and run a doctor pass:

./bin/awf.ps1 bootstrap-repo --repo C:\repo --enable-installed

Use tooling-status when you want a read-only check of detected CLIs, Jira MCP readiness, and repo hints:

./bin/awf.ps1 tooling-status --repo C:\repo

What the setup helper does

configure-tooling updates .wi/config.json for:

  • enabled or disabled adapters
  • the repo default adapter
  • optional recommended launch commands for supported CLIs, including current model selection flags
  • Jira MCP enablement through story_sources.jira.enabled

PowerShell

./installers/configure-tooling.ps1 -RepoPath C:\repo -EnableInstalled

Bash

./installers/configure-tooling.sh --repo /repo --enable-installed

Common examples

Enable only the tools already installed on the machine:

./bin/awf.ps1 configure-tooling --repo C:\repo --enable-installed

Enable Codex and Claude explicitly, make Claude the default, and disable Jira MCP:

./bin/awf.ps1 configure-tooling --repo C:\repo --enable-adapter codex --enable-adapter claude --default-adapter claude --disable-jira

Enable Copilot with the default direct launch command:

./bin/awf.ps1 configure-tooling --repo C:\repo --enable-adapter copilot

Notes

  • tooling-status works even before a repo is initialized, which makes it a good first diagnostic step.
  • bootstrap-repo is the recommended first-run command for new repos because it combines init, setup, and validation.
  • Claude works with the built-in adapter path, so enabling it mainly records your intent in config.
  • Codex gets a recommended launch template automatically when enabled through the setup helper.
  • Copilot now uses the standalone copilot command, not gh.
  • Copilot gets a recommended interactive launch command automatically when enabled through the setup helper or the shell adapter wizard.
  • The recommended Copilot launch grants tool access and the repo working directory up front so the run does not stall on permission prompts.
  • If a CLI can list models in your environment, set adapters.<name>.models_command in .wi/config.json so AWF can load those models dynamically into tooling status and the shell wizard.
  • If you disable Jira MCP, start-story --jira-url ... will fail fast instead of silently trying to use it.
  • If you disable an adapter in .wi/config.json, AWF will reject attempts to use it.

Model discovery examples

The generated .wi/config.json now includes a models_command placeholder for each built-in adapter. Replace null with a local command only when that CLI supports model listing in your environment.

Example patterns:

{
  "adapters": {
    "codex": {
      "models_command": ["<codex-command-that-lists-models>"]
    },
    "copilot": {
      "models_command": ["<copilot-command-that-lists-models>"]
    },
    "claude": {
      "models_command": ["<claude-command-that-lists-models>"]
    },
    "gemini": {
      "models_command": ["<gemini-command-that-lists-models>"]
    }
  }
}

AWF accepts either of these output shapes from models_command:

  • JSON array such as ["claude-sonnet-4","claude-opus-4"]
  • plain text with one model id per line

If your CLI does not provide a stable model-list command, leave models_command as null and either:

  • rely on AWF's built-in suggested model catalog
  • set available_models directly in the adapter config

Example with a static override:

{
  "adapters": {
    "codex": {
      "available_models": ["gpt-5.4", "o3", "o4-mini"]
    }
  }
}