Skip to main content
lager 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

​
Options

The lager dut group takes only --help. Pass --box to each subcommand.

​
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.
The editable block accepts these fields:

​
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.
Options: You must supply at least one of --url, --repo-path, --external-id or --external-url. 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 watches /etc/lager/bench.json, /etc/lager/saved_nets.json and /etc/lager/box_id. When one of them changes on disk, the server reloads on the next request, so agents see your changes with no manual step. To force a reload at once, have a connected agent call the box_manage tool with action="reload". You can also restart the box service.