Rebind

Remote Control

@rebind / remote-controlv0.6.1Public

Connect your programs to Rebind over WebSocket using the documented remote-control server. Works with the client libraries and MCP.

Files

Older release. Installs get 0.6.1.

README.md2.9 KB

# Remote Control

Let compatible programs send keyboard and mouse input, read supported information such as window details, and react to events on this computer. Connect using Rebind's [client libraries](https://docs.rebind.gg/remote-control/client-libraries) or [MCP setup for AI tools](https://docs.rebind.gg/remote-control/mcp).

Requires Rebind Engine 3.5.0 or newer. Rebind Link is optional. Available controls differ on Windows, macOS, and Linux; check [platform support](https://docs.rebind.gg/concepts/platforms) for what you need.

## Set up

1. Open the installed package's `main.luau` in Rebind and select **Options**.
2. Set a strong, unique **Auth token before starting**. This is the secret your connecting program must provide. Leaving it blank allows anyone who can connect to control the computer.
3. Leave **WS port** at **19561**, or choose an unused port. Start from the editor toolbar. Restart after changing the port.
4. Give your program the address `ws://127.0.0.1:19561` and your token. From another trusted computer, replace `127.0.0.1` with this computer's network address. Use your chosen port if you changed it.

For MCP, these values are called `REBIND_URL` and `REBIND_TOKEN`. Follow the linked client instructions to connect; the [protocol reference](https://docs.rebind.gg/remote-control/protocol) covers custom programs.

## Access and privacy

The server accepts connections through every network connection on this computer. There is no setting to limit it to this computer alone. Connections are not encrypted. Restrict access with your firewall and use a trusted network or an encrypted tunnel.

Changing the token does not disconnect existing users. Stop and restart the script to revoke their access. Stop it whenever remote control is not needed.

## Advanced controls

Running system commands, accessing package files, changing Windows registry entries, and running custom Luau code are off by default. Enabling them requires editing the corresponding `ALLOW_EXEC`, `ALLOW_FILE`, `ALLOW_REGISTRY`, or `ALLOW_LUA_EXEC` value in `main.luau`, then restarting. These are not switches in Options. Some MCP tools need `ALLOW_LUA_EXEC`; follow the MCP guide before enabling it.

Leaving these controls off does not make access read-only. Connected users can still send input and use supported clipboard, window, and other controls. The package's permission to run commands does not enable `ALLOW_EXEC` by itself.

Updating the package replaces `main.luau`, so set these values again after each update.

## Stop

Stop from the editor toolbar. **Left Ctrl + Left Alt + K** stops all scripts and releases held input. Stopping Remote Control also closes its network listener and ends its timers and audio playback.

Every command has not been tested on every platform. Windows and Linux use and actual input delivery still need verification.

4 files, 41.4 KB. 1 has no text preview.