Skip to content

acq: intercept --kit <ref> on run/create and translate it (currently passed raw to the backend, breaking neutral kits) #222

Closed

Description

@mogul

Summary

acq run/acq create do not intercept a user-supplied --kit <path> flag.
The flag falls through to the backend (acq_backend_provision only strips
--name), so it reaches sbx create --kit <path> untranslated. Since a
neutral hybrid/v1 kit is a different schema than sbx-v2, sbx rejects it:

$ acq run opencode --kit ../agentic-coding-patterns/integrations/isolation/acq-kits/openchamber .
ERROR: resolve kits: kit "...": artifact: invalid spec.yaml: yaml: unmarshal errors:
  line NN: field files not found in type spec.SpecFile
  line NN: cannot unmarshal !!seq into spec.CommandsPolicy
  line NN: field backend_extras not found in type spec.SpecFile

Expected

--kit <ref> (repeatable) on acq run / acq create should be treated like an
entry in ACQ_EXTRA_KITS: added to the kit list so it goes through the neutral→
backend translation (_acq_sbx_translate_kit for sbx), and not forwarded to
the backend CLI as a raw flag.

Workaround (today)

Pass the kit via the env var, which IS translated:

ACQ_EXTRA_KITS="/abs/path/to/kit" acq run opencode .

Notes / scope

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions