Skip to content

Serial monitor

Ditch minicom and screen. Hydron opens a persistent, interactive serial monitor directly inside your session.

Hydron Monitor is a dedicated panel at the bottom of your VS Code layout. Stream, filter, and send data to your device without leaving the editor.

/serial runs inside a Hydron session. Use /sessions to select or resume one, then connect with /serial.

In the panel

  • Connect, disconnect, or reconnect to a port
  • Pick a port from the detected list
  • Add or remove a saved port
  • Cycle baud rate
  • Clear the buffer
  • Filter input
  • Send input to the connected device

Serial monitor summarizer

  • Posts a short digest of your device's serial output into chat every 30 seconds, so you can follow what is happening without scrolling the raw monitor.
  • Covers only new lines, and highlights only what matters: errors, warnings, state changes such as boot and reset, and notable values.
  • Works for ports the agent opens and for ports you connect manually, and stays silent when there is nothing worth reporting.

What an agentic monitor makes possible

The monitor is not only a window onto the port. The agent reads and drives it as part of a task, which opens up work a passive terminal cannot do:

  • Interpret fault codes, stack traces, and sensor readings against your project's MCU specs and source, instead of leaving you to decode them.
  • Capture boot output from the first byte after a reset, rather than joining a stream already in progress.
  • Wait for a specific line before sending the next command, so a scripted interaction does not race the device.
  • Stop a capture when a known message appears instead of guessing at a duration.
  • Watch several boards on one shared timeline, to see whether a message sent by one arrives at the other.
  • Keep buffering between turns, so output produced while the agent is building or editing files is still there when it reads.
  • Close the loop on a change: build, flash, reset, capture, and report whether the fix held.

Troubleshoot

  • Output is garbled. Wrong baud rate. Cycle it in the panel, or let the agent auto-detect. The default is 115200.
  • No ports listed. The board is not enumerating. Check the cable, which is often charge-only, and confirm the device appears in your OS device list.
  • The port is busy. Another program holds it. Close other monitors, and disconnect before flashing with a tool that needs exclusive access.

Next