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

Telegram and Feishu plugins

Install channel plugins, configure receiver credentials and inspect connection state.

Install a plugin

Initialize and start the daemon, then install a first-party plugin:

bash
openmybot plugins add --built-in telegram
openmybot plugins add --built-in feishu
openmybot plugins list --json
openmybot plugins add --built-in telegram
openmybot plugins add --built-in feishu
openmybot plugins list --json

A trusted local plugin directory can be installed with openmybot plugins add /absolute/path/to/plugin. Built-in installation uses binaries beside the main executable; it is not an online download. Install before pairing a channel.

Configure receiver credentials

bash
openmybot bindings receiver telegram
openmybot bindings receiver feishu
openmybot bindings receiver telegram
openmybot bindings receiver feishu

The command reads the plugin's declared fields from standard input. Secret fields are hidden in an interactive terminal. Follow the installed plugin's prompts; do not put secrets in arguments, chat or screenshots. Piped input uses one line per declared field in declaration order.

The platform bot also needs appropriate configuration and permissions. Follow the installed plugin and platform's current settings; a normal web login is not a bot credential.

Pair a workspace

bash
openmybot pair telegram --workspace /absolute/path/to/workspace
openmybot bindings list --json
openmybot pair telegram --workspace /absolute/path/to/workspace
openmybot bindings list --json

Use feishu for Feishu. Complete the channel-side pairing instructions, check the target and workspace, and try a low-risk message. The owner handles permissions; see runs.

Inspect or remove

Use plugins list and status. Receiving a message, executing a task and delivering its result are separate stages.

Use openmybot plugins remove telegram to remove that plugin after checking bindings and active work. Real-channel rechecks remain pending; local tests are not blanket production acceptance.