Claude Code
Claude Code is the default provider (`claude-code`). Setup is unchanged from v1 and v2: install it, sign in with your own account, and point the factory at the executable. The factory does not copy Claude Code's install steps and does not ask for credentials or a model.
Claude Code is the default provider (claude-code). Setup is unchanged from v1 and v2: install it, sign in with your own account, and point the factory at the executable. The factory does not copy Claude Code's install steps and does not ask for credentials or a model.
Install Claude Code from its own docs. Confirm it is on PATH:
claude --versionIn kusaw.yaml, claude.command defaults to claude. claude.extra_args are extra flags. claude.env_passthrough defaults to CLAUDE_*. The factory never stores credentials; it uses the session you already have.
Where it lives in the runner
Built-in agent steps call Claude Code through the shared runner. The provider name is claude-code. A factory that omits provider and every steps.<id>.provider runs those steps on Claude Code, as in v1 and v2.
Intake always uses Claude Code in this version, including grill. pricing is still Claude Code token prices. Cursor prices go in cursor.pricing if you enable Cursor.
The argv the runner builds is the same surface as v1 and v2.
What Claude Code can enforce versus Cursor is in the capability matrix.
Providers
A step's [provider](../glossary.md#provider) is the agent CLI that runs it. `claude-code`, the user's configured Claude Code, is the default. `cursor` is optional. Each provider's [capabilities](../glossary.md#capability) say what a step can require.
Cursor
Cursor is an optional provider. It stays off until you enable it on the machine. Use it only for personal and demo code, never a restricted setup.