telegram-codex-linker

Telegram Codex Linker

Overview

This skill exists so the public entrypoint is only "install the skill". After that, the skill should do the bridge-core plus chosen-pack work itself.

The user should not be told to manually git clone, npm install, npm run build, or poke service managers unless local automation is genuinely blocked.

Primary Entry

Assume the user already installed this skill with a one-line GitHub command.

After that, the user should be able to say things like:

• Use $telegram-codex-linker to set up my Telegram bridge
• Install the Codex Bridge with the Telegram pack
• Repair my Telegram bridge
• Rebind the bridge to a new Telegram account

Your job is to take over from there.

Before acting, read references/install-strategy.md.

Never assume the current working directory is the skill directory. Resolve these first:

SKILL_ROOT="${CODEX_HOME:-$HOME/.codex}/skills/telegram-codex-linker"
INSTALL_SCRIPT="$SKILL_ROOT/scripts/install-bridge-from-github.sh"
ROOT_DISCOVERY_SCRIPT="$SKILL_ROOT/scripts/discover-project-scan-roots.sh"
CTB_BIN="${HOME}/.local/share/codex-telegram-bridge/bin/ctb"

Windows PowerShell equivalents:

$codexHome = if ($env:CODEX_HOME) { $env:CODEX_HOME } else { Join-Path $HOME ".codex" }
$localAppData = if ($env:LOCALAPPDATA) { $env:LOCALAPPDATA } else { Join-Path $HOME "AppData\Local" }
$skillRoot = Join-Path $codexHome "skills\telegram-codex-linker"
$installScript = Join-Path $skillRoot "scripts\install-bridge-from-github.ps1"
$rootDiscoveryScript = Join-Path $skillRoot "scripts\discover-project-scan-roots.ps1"
$ctbBin = Join-Path $localAppData "codex-telegram-bridge\bin\ctb.cmd"

For first install, use the bundled script:

bash "$INSTALL_SCRIPT" --pack telegram --telegram-token '<token>' --project-scan-roots '<path1:path2:path3>'

On Windows, use PowerShell instead:

powershell -ExecutionPolicy Bypass -File $installScript -Pack telegram -TelegramToken '<token>' -ProjectScanRoots '<path1;path2;path3>'