- Docs
- Guides
- Cross-cutting
- How-to
- Configure your agent adapter
Configure your agent adapter
Pin or override the target adapter so installations consistently project into the intended agent environment.
Use this when: You work across several IDEs or want to pin a non-default adapter instead of relying on auto-detection.
Prerequisites: agentbundle CLI on your PATH.
Result: A pinned default adapter (or per-install --adapter override) so every install targets the correct IDE without re-specifying the flag.
Installs auto-detect the agent you’re working in and fall back to Claude Code when there’s nothing to detect. To work across several IDEs — or to pin a different default — configure the adapter explicitly.
Pin a default adapter
Section titled “Pin a default adapter”agentbundle config set adapter cursorThis is user-global: set it once and it applies whether you install into a repo or at user scope. Every later install targets the pinned adapter.
Override for a single install
Section titled “Override for a single install”# Repo scopeagentbundle install --pack core --adapter codex
# User scopeagentbundle install --pack desk-research --scope user --adapter codexPer-install --adapter beats the pinned default, which beats auto-detect. Re-running an install keeps whatever adapter that install already uses — an upgrade won’t reset it.
Supported agents
Section titled “Supported agents”claude-code, cursor, codex, copilot, gemini, kiro-ide, kiro-cli
See the adapter support matrix for a breakdown of which agent supports skills, subagents, commands, and hooks — and where each gracefully degrades.