All plugins

printwatch

Control 3D printers over the local network from your agent: fleet status (temps, progress, layers), file listing, print start/pause/resume/cancel, file upload with automatic dialect packaging (printer_upload), and camera snapshots delivered into chat. Dual protocol — Anycubic Kobra printers over their built-in stock LAN Mode (clean-room reverse-engineered handshake + MQTT; no cloud, no rooting, nothing flashed) and Klipper/Moonraker over HTTP, and Bambu Lab printers over their local MQTT/FTPS interface (user's LAN access code; X1/P1/A1 family). Includes a headless slice-to-print pipeline: any raw .gcode is repackaged into the exact Anycubic .gcode.3mf dialect the stock firmware requires (header blocks, M75, uppercase-MD5 sidecar, X-ACNext slice info) and started remotely. Disclosure — connects only to the printer hosts the user configures (PRINTWATCH_PRINTERS / PRINTWATCH_BAMBU / PRINTWATCH_MOONRAKER_URL via agent.secret_scope); printer_print, printer_upload, printer_pause_resume and printer_cancel move physical hardware and ask for Hermes approval on every call (refused when no human is present); printer_upload sends a local .gcode/.3mf file the model names to the configured printer; printer_snapshot shells out to ffmpeg, and for Bambu printers the LAN access code is visible in ffmpeg's process arguments for the ~2s capture; Anycubic MQTT and Bambu FTPS/MQTT accept the printer's self-signed certificate (CERT_NONE) on the local network; no telemetry, no external services, no credentials persisted.

clawsyndicate3Toolsv0.4.3Updated 5 days ago

About

Control 3D printers over the local network from your agent: fleet status (temps, progress, layers), file listing, print start/pause/resume/cancel, file upload with automatic dialect packaging (printer_upload), and camera snapshots delivered into chat. Dual protocol — Anycubic Kobra printers over their built-in stock LAN Mode (clean-room reverse-engineered handshake + MQTT; no cloud, no rooting, nothing flashed) and Klipper/Moonraker over HTTP, and Bambu Lab printers over their local MQTT/FTPS interface (user's LAN access code; X1/P1/A1 family). Includes a headless slice-to-print pipeline: any raw .gcode is repackaged into the exact Anycubic .gcode.3mf dialect the stock firmware requires (header blocks, M75, uppercase-MD5 sidecar, X-ACNext slice info) and started remotely. Disclosure — connects only to the printer hosts the user configures (PRINTWATCH_PRINTERS / PRINTWATCH_BAMBU / PRINTWATCH_MOONRAKER_URL via agent.secret_scope); printer_print, printer_upload, printer_pause_resume and printer_cancel move physical hardware and ask for Hermes approval on every call (refused when no human is present); printer_upload sends a local .gcode/.3mf file the model names to the configured printer; printer_snapshot shells out to ffmpeg, and for Bambu printers the LAN access code is visible in ffmpeg's process arguments for the ~2s capture; Anycubic MQTT and Bambu FTPS/MQTT accept the printer's self-signed certificate (CERT_NONE) on the local network; no telemetry, no external services, no credentials persisted.

PrintWatch

A Hermes Agent plugin for controlling 3D printers over the local network — no cloud,
no rooting, stock firmware.

Three protocol families:

  • Anycubic Kobra printers via the built-in LAN Mode API (reverse-engineered,
    clean-room implementation — handshake, MQTT telemetry, file management, print control,
    camera snapshots, and a full headless slice-to-print pipeline)
  • Bambu Lab printers (X1/P1/A1 family) via their local MQTT/FTPS interface —
    status, control, file upload, RTSP snapshots; just host + serial + LAN access code
  • Klipper/Moonraker printers via HTTP (standard open protocol)

Why

Printer control shouldn't require a vendor cloud account. PrintWatch talks to your
printers the way your slicer does — over your own LAN — so an agent can answer
"how are the printers?", start a print from a file you send it, and push you a
photo when something needs eyes.

Tools

ToolWhat it does
printer_statusLive status: temps, progress, layer, state across the fleet
printer_filesList files on printer storage
printer_printStart a print by filename (as listed by printer_files)
printer_uploadSend a local .gcode to the printer (auto-packaged into the printer's dialect) and optionally start it
printer_cancelCancel the running job (asks for your approval in chat first)
printer_pause_resumePause / resume
printer_snapshotGrab a camera frame and drop it in your chat

Headless slice-to-print (the fun part)

printer_upload takes a raw .gcode from any slicer and repackages it into the exact
.gcode.3mf dialect Anycubic's firmware requires (see kobra_dialect.py) — header
blocks, M75, uppercase-MD5 sidecar, X-ACNext slice info — then uploads it over
LAN and starts the print. Bambu .gcode files are packed into a 3mf the same way.
No Anycubic account, no Slicer Next, no hands.

Security posture

  • Stock firmware only — LAN Mode is a built-in feature; nothing is flashed or rooted
  • Local network only — no cloud relay, no telemetry
  • Hardware actions are approval-gated — print/upload/pause/resume/cancel route through a pre_tool_call hook into Hermes's own human-approval gate (once/session/always/deny; fails closed when no human is present, e.g. under cron)
  • Credentials via agent.secret_scope — config values are read through Hermes's
    scoped secret layer, never os.environ
  • Session tokens are per-session, in-memory, never logged or persisted
  • Bambu RTSP snapshots run ffmpeg with the access code in the local process argv for
    the ~2s capture window (local-only exposure; documented, error output scrubbed)

Install

hermes plugins install <this-repo>

Requires Python 3.10+. Dependencies: paho-mqtt, requests, cryptography.

License

MIT

README from the reviewed commit 1919e95; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section