lager box dut manages the DUT context stored in /etc/lager/bench.json on
a Lager Box. This context tells AI agents (via the MCP
server) what the box tests: purpose, MCU, key
peripherals, subsystem groupings, and references to schematics and datasheets.
See Authoring DUT Context for the concepts
and workflow.
Syntax
Global Options
Commands
Command Reference
Show
Print the current DUT context as JSON.Edit
Round-trip the DUT context through$EDITOR (falls back to nano, then vi).
On save, the new JSON is validated and written back to /etc/lager/bench.json.
Add Doc
Attach a single document reference to the active DUT without hand-editing JSON. The box records only a pointer — it does not store the file. The agent fetches and analyses it with its own tools.
You must supply at least one of
--url or --repo-path. The reference is
appended to the list matching --kind (schematic → schematic_refs,
datasheet → datasheet_refs, firmware → firmware_refs; everything else →
extra_docs).
After editing
The MCP server reads the bench config at startup. So agents see your changes, either have a connected agent call thebox_manage tool with action="reload"
(re-reads /etc/lager/bench.json and rebuilds the capability graph), or restart
the box service.
