Docs
Refer a friend. Get a weekly-quota reset.Friend signs up and uses it → +1 reset (valid 30 days) · up to 10% cash back on their spend.
+1 resetGenerate link

Bindings and workspaces

Control a channel or host workspace, revoke or reconfirm access and handle unknown runs.

Inspect bindings

Run openmybot bindings list --json and identify the returned binding ID, channel/host and workspace. Similar names are not interchangeable IDs.

Create a binding

bash
openmybot pair telegram --workspace /absolute/path/to/project --run-deadline 300
openmybot bindings host crabcode --workspace /absolute/path/to/project --run-deadline 300
openmybot pair telegram --workspace /absolute/path/to/project --run-deadline 300
openmybot bindings host crabcode --workspace /absolute/path/to/project --run-deadline 300

The deadline is in seconds; 300 is only an example. The workspace must be absolute. The supported host identifier remains crabcode even though the desktop product is named wrokCode.

Reconfirm or revoke

After checking the user, directory and scope, run openmybot bindings reconfirm BINDING_ID for a suspended binding. Do not create a duplicate to bypass it.

Use openmybot bindings revoke BINDING_ID to revoke access. This does not retract messages or remove files already produced. Inspect and cancel a specific active run when necessary.

Handle an unknown run

bash
openmybot status --run RUN_ID --json
openmybot bindings reset-thread BINDING_ID --ack-unknown RUN_ID
openmybot status --run RUN_ID --json
openmybot bindings reset-thread BINDING_ID --ack-unknown RUN_ID

Inspect actual effects before acknowledging an unknown run and resetting its thread. Unknown does not mean no effects occurred. Do not delete state or replay an external action merely to clear the status.