Rebind
Documentation(opens in a new tab)

Use case

Your local tools can drive your scripts.

Trigger Rebind scripts from local tools over loopback HTTP, or use an authenticated WebSocket listener when network access is required.

Install v3.5.1Documentation(opens in a new tab)

use cases / local control

Rebind scripts can expose HTTP and WebSocket handlers. Net.Listen binds to 127.0.0.1, so its HTTP server stays on the machine. Net.WSListen currently binds every network interface. A WebSocket listener needs script-level authentication and firewall restriction even when its intended client is local.

The shapes this takes

  • A local test runner triggers a hardware-backed input sequence.
  • A desktop control panel calls a script over loopback HTTP.
  • A local AI sidecar sends commands over loopback HTTP or shared-memory Pipe IPC on Windows.
  • A home-automation bridge running on the same machine triggers a macro.

With Rebind Link, script output leaves dedicated hardware as standard USB HID.

Where to start

Use case

Connect local software to physical output.

Install v3.5.1RebindGPT