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
openmybot pair telegram --workspace /absolute/path/to/project --run-deadline 300
openmybot bindings host crabcode --workspace /absolute/path/to/project --run-deadline 300openmybot pair telegram --workspace /absolute/path/to/project --run-deadline 300
openmybot bindings host crabcode --workspace /absolute/path/to/project --run-deadline 300The 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
openmybot status --run RUN_ID --json
openmybot bindings reset-thread BINDING_ID --ack-unknown RUN_IDopenmybot status --run RUN_ID --json
openmybot bindings reset-thread BINDING_ID --ack-unknown RUN_IDInspect 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.