per-step CLI runtime assignment

[smp4]

Hi there,
I've been searching for a declarative, reproducible workflow solution for some time, excited to find berstein.

On a first pass, it seems cli runtime can be assigned at the workflow level only. Is that correct? Ideally I'd like to be able to apply different CLIs to different stages in the workflow (eg. opencode to red/green/refactor, then claude code to code review). I guess i can work around that by having a workflow for just r/g/r with opencode, and follow on with another workflow for just the claude step, but this arbitrarily splits the whole workflow as a result of a tool limitation, rather than user-side logic.

is that possible?
cheers!

[chernistry]

Quick update. Pulling the direct cli: field on a plan step right now. Tracking in #964, PR up shortly. I'll ping back when it's merged.

Stopgap until then is role_model_policy in bernstein.yaml (one CLI per role, steps reference roles). It overloads role: though, so the proper fix is what lands in this release.

[chernistry]

@smp4 shipped in v1.9.2. Plan steps now take a cli: field directly:

stages:
  - name: red-green-refactor
    steps:
      - { title: Red,      role: backend,  cli: opencode }
      - { title: Green,    role: backend,  cli: opencode }
      - { title: Refactor, role: backend,  cli: opencode }
  - name: review
    steps:
      - { title: Code review, role: reviewer, cli: claude }

Precedence: per-step cli: → role_model_policy.<role>.provider → top-level cli: → default adapter. The role-shaped workaround from my earlier comment still works, but you can ignore it now.

pipx install --upgrade bernstein   # or pip install --upgrade

Thanks. The framing in the OP — splitting the workflow as a tool limitation rather than user-side logic — was the right way to put it. Tracked as #964 → PR #965, see the v1.9.2 release notes.