bstack is bercail's opinionated opencode. opencode signs in with a Claude plan (Claude Agent), a ChatGPT plan, and an X subscription, so one harness runs all three, on subscriptions you already pay for. bstack sets opencode up the way bercail works: the job is a beads issue, agents stage and leave changes uncommitted for tuicr, and each kind of work goes to the model that is best at it.
It borrows from pstack (rigor, playbooks, roles by model strength, how/why/unslop), cursor-team-kit (babysit-pr and CI loops, which became autopilot), tstack (a council of providers), and gstack, on top of Shep's handoff workflow.
New installs run bstack. Claude Code, Codex CLI, and cursor-agent stay equal harnesses beside it. Bercail does not prefer one for a handoff, pick one, or fall back from one to another.
bercail bstack setup # installs opencode, connects your plans; models are picked for you
bercail bstack status # what is connected, which model each role uses
dev # the desk starts opencode as the bstack agentThe bstack guide is the full story, with prompts to copy. Each fact lives on one page:
| Topic | Page |
|---|---|
setup, sign-ins, how models are picked, status, /bstack-setup, turning it on |
Set up bstack |
| The playbooks, the roles (lead, build, judge, council, autopilot), what a prompt holds | Work with the bstack agent |
/how, /why, taking over a branch |
Understand the code |
The build playbooks, /unslop |
Build and clean the change |
/council, /ready |
Review it |
/autopilot and what bstack-autopilot may do |
Ship with autopilot |
/handoff, stages bstack and autopilot |
Run jobs in parallel |
Pinning models, effort, role fallback, the files bstack writes, bercail bstack off |
Make it yours |
| Prompts and pitfalls | Recipes and pitfalls |
The skills (bstack, how, why, unslop, council, autopilot) are listed in commands, the [bstack] defaults in config, and the headless stages in handoff.