acp-provider
Configure or troubleshoot ACP agent discovery, custom models, skills, and compaction in BB.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 3859
- Лиценз
- MIT
- Последна проверка на записа
- 23.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add get-bb/bbСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
ACP providers
Known agents can be discovered automatically when their CLI is installed on the
host: opencode, omp, grok, and hermes appear as acp-opencode, acp-omp,
acp-grok, and acp-hermes-agent. Inspect the target host's catalog with
bb provider list and bb provider models <provider-id> using its environment
or machine selector.
To hide a detected ACP agent, use bb provider disable acp-opencode, or Disable
on Settings → Providers. Restore it with bb provider enable acp-opencode.
This leaves other ACP agents and the host CLI intact. Disabled agents skip
background capability probing. bb provider list --all includes disabled agents.
Cursor project skills come from .cursor/skills, which can link to
.agents/skills. BB lists these linked skills as read-only under cursor-project.
ACP agents report their own models and may reject unlisted model IDs.
For acp-opencode the list mirrors the OpenCode catalog, so add a model to
the OpenCode config rather than bb's customModels:
bb provider models acp-opencode --environment "$BB_ENVIRONMENT_ID"
bb thread spawn --provider acp-opencode --model <provider/model>
OpenCode agents are session modes, not models selectable through BB's model
field. OpenCode reports its primary agents as the mode session option,
including custom agents from the OpenCode config directory and from the
project's .opencode/ directory, so project agents appear when the list is
read for that project or environment:
bb provider models acp-opencode --project "$BB_PROJECT_ID"
bb thread spawn --provider acp-opencode --option mode=<agent>
bb lists only the agents OpenCode itself loads, and OpenCode does not read
agent files from other folders such as .agents/agents/. To use such a folder,
set OPENCODE_CONFIG_DIR as a machine variable or in a custom agent's env; a
relative value is resolved in each workspace, so .agents lists every
project's own .agents/agents/*.md:
printf '.agents' | bb machine env set OPENCODE_CONFIG_DIR
Every file in that folder must be a valid OpenCode agent file; OpenCode refuses
to start on one it cannot parse, such as tools written as a comma-separated
list.
Grok Build advertises models and thought_level options over ACP, so the
picker follows the connected agent (including xhigh on grok-4.6).