Skip to main content

Remote skill

Remote From Telegram Skill

Connect the current agent session to an available Telegram channel bridge.

On this page

Install command

AI DevKit installs its built-in skills as one curated set. Run this once to install remote-from-telegram with the rest of the built-in workflow skills.

bash
npx ai-devkit@latest skill add --built-in

What it does

Use remote-from-telegram when you want to control or chat with the current session from Telegram. It checks AI DevKit readiness, selects an available Telegram channel, starts the bridge in daemon mode, and avoids stopping existing bridges without confirmation.

When to use it

  • Bridge the current agent session to Telegram
  • Reuse an existing configured Telegram bot channel
  • Start a background channel bridge with a clear stop command

Supported agents

  • Claude Code
  • Codex
  • opencode
  • Pi

The SKILL.md file

This is what your agent reads when the skill runs. View it on GitHub (opens in a new tab)

Use this skill when the user wants to control or chat with the current session from Telegram.

Prefer the installed ai-devkit binary; if unavailable, use npx ai-devkit@latest. Run AI DevKit commands outside filesystem sandboxes because they inspect host-level agent and channel state.

Workflow#

  1. Check readiness:

    bash
    ai-devkit status --json

    If AI DevKit is not ready, use ai-devkit-setup skill first. Stop if setup leaves manual actions.

  2. Inspect channels and agents:

    bash
    ai-devkit channel list
ai-devkit agent list --json

  3. Identify the current agent by matching this session to an agent list --json entry. If unclear, ask for the agent name.

  4. Find configured Telegram channels. If none exist, tell the user to run:

    bash
    ai-devkit channel connect telegram

    Stop after giving that action.

  5. Choose a channel. Use the requested channel or the only available Telegram channel. If multiple Telegram channels are available, ask the user which one to use. Available means Telegram, enabled, configured with bot credentials, and not already running. Do not reject a Telegram channel only because it is not authorized yet; Telegram authorization cannot complete until after the bridge is started and the user sends a message to the bot.

  6. If no Telegram channel is available because bridges are already running, ask before stopping one. After confirmation:

    bash
    ai-devkit channel stop <channel>

  7. Start the bridge in the background:

    bash
    ai-devkit channel start <channel> --agent <agent-name> --daemon

  8. Report the connected channel, agent name, and how to stop it: ai-devkit channel stop <channel>. If the channel was not authorized before start, explicitly tell the user the bridge is running and they must now send any message to the Telegram bot to authorize that chat before using it.

Boundaries#

  • Do not create or connect a Telegram channel for the user; only point them to channel connect.
  • Do not stop a running bridge without explicit confirmation.
  • Do not guess when both agent or channel selection are ambiguous.
esc