Skip to main content
Define your custom hardware procedures that agents can run during implementation.
Where: Platform → Testing page (/testing). Hardware bridges also require seb connect running on the host with the hardware attached.

Procedures

A procedure is a named verification step saved on the project. Agents run them during implementation to validate their work, giving you confidence in the code they produce. Common shapes:
  • Smoke test — boot the firmware, check the expected strings on serial.
  • Calibration check — run a routine, compare results against expected ranges.
  • Regression — replay a captured CAN sequence, assert no unexpected frames.

Add a procedure

Testing page → procedure list → + Add procedure. An editor opens. Saving adds the procedure to the project; it appears immediately for every member.

Run a procedure

Click Run on a procedure card. If it takes inputs, a dialog asks for them; live output streams in a side pane. Each run is recorded with timestamp, outcome, and operator. A bridge is a live stream from a device connected to your host machine.
BridgeUse
Serial ConsoleUART monitor
CAN BusLive CAN traffic, decoded against project DBC files
GDB ProbeOn-target debug (ST-Link, J-Link, CMSIS-DAP)
Saleae LogicStream digital + analog signals
Ethernet CaptureCapture and inspect frames
UDP ReceiverReceive UDP log streams
Add a bridge from the Testing page → bridge list → + Add. The Connection status pill in Platform’s header shows whether a host is online. Without an active host, bridges can’t stream and procedures that touch hardware won’t run.

How agents use this

Agents call procedures while writing code, ensuring proper implementation of the given task. Software-only procedures run on the agent’s cloud machine; hardware procedures reach your host machine through the bridges configured here.

Next

Guide → 5. Review in the CLI.