Tools guide
AI tools stay local
Amistio coordinates work, but the local runner uses the AI coding tools you install and authenticate on your own machine. That keeps repository execution close to your checkout, credentials, package managers, and review process.
The tool model
Amistio does not install or log into third-party coding tools for you. During runner setup, you choose the provider or command the runner should use. The runner checks what is available locally, reports non-secret capability information, and claims only approved work for the paired repository.
Your provider authentication, source checkout, package manager credentials, shell profile, and machine-specific setup stay on your machine. The web app should only need safe status and reviewable project-brain records.
Supported choices
auto
Let the runner choose from available configured tools based on project and runner preferences.
opencode
Use opencode from the local runner when it is installed, authenticated, and selected for the paired project.
Claude
Use Claude from the local runner when it is installed, authenticated, and selected for the paired project.
Codex
Use Codex from the local runner when it is installed, authenticated, and selected for the paired project.
GitHub Copilot
Use GitHub Copilot from the local runner when it is installed, authenticated, and selected for the paired project.
Gemini
Use Gemini from the local runner when it is installed, authenticated, and selected for the paired project.
Aider
Use Aider from the local runner when it is installed, authenticated, and selected for the paired project.
Cursor Agent
Use Cursor Agent from the local runner when it is installed, authenticated, and selected for the paired project.
Runner setup checklist
- Install the Amistio CLI runner and confirm `amistio --help` works.
- Install and authenticate at least one supported local AI coding tool.
- Run `amistio tools` to see which supported tools the runner detects.
- Pair or import the repository so work is scoped to the correct project.
- Use runner lifecycle controls only for runners you paired, unless you are acting as an organization admin.
- Choose the effective tool/model in the app or runner preferences when multiple choices are available.
- Use custom local commands only when you understand how that command handles prompts, files, logs, and credentials.
Custom command escape hatch
Custom local commands are useful when your team has an internal wrapper, a specific model gateway, or an experimental tool that Amistio does not support directly yet. Treat custom commands as powerful: they run on your machine, so you own their installation, behavior, updates, logs, and credentials.
Good fit
A stable internal tool that reads a work prompt, works inside the current checkout, returns clear status, and respects your repository rules.
Bad fit
A command that uploads broad source context, requires manual prompts every run, hides failures, or stores secrets in project files.
How tools connect to the project brain
The project brain gives local tools better starting context: ADRs explain why, plans explain sequence, feature specs explain behavior, prompts describe the work unit, memory captures lessons, and workflows keep repeated operations consistent. The tool is the executor; the brain is the durable operating layer around it.