oysterun-telegram

name	oysterun-telegram
description	Use for Oysterun Telegram status and per-session Telegram setup commands through the P86 CLI without depending on a global Telegram product flag.
metadata	{"short-description":"Manage Oysterun Telegram setup"}

Oysterun Telegram

Canonical product skill source lives at skills/oysterun-telegram/. Generated mirrors live at .codex/skills/Oysterun/modules/oysterun-telegram/, host-service/assets/product-skills/oysterun-telegram/, and host-service/assets/product-skills/Oysterun/modules/oysterun-telegram/. Run node tool_scripts/sync_product_skills_to_codex.mjs after changing this skill and node tool_scripts/check_product_skill_mirrors.mjs before review.

Use this module skill for normal product Telegram status and per-session setup. It wraps the P86 product CLI contract:

oysterun telegram <action> [options]
oysterun sessions telegram <action> [options]

The module helper is current-session aware. In a live Host session with OYSTERUN_HOST_ORIGIN, OYSTERUN_CAPABILITY_TOKEN, and OYSTERUN_SESSION_ID, status resolves the current session's Telegram state through scoped runtime capability auth; it must not ask the in-session agent to run dashboard login:

node .codex/skills/Oysterun/modules/oysterun-telegram/scripts/oysterun_telegram.mjs status

For per-session setup, use the product CLI directly. Inside a live Host session, omit --session-id for the current session. When the user names another visible live session, pass it with --session-ref or --session, not --session-id. External operator shells may pass --session-id and dashboard auth:

oysterun sessions telegram get
oysterun sessions telegram enable --update-config
oysterun sessions telegram disable
oysterun sessions telegram update --telegram-enabled true --update-config
oysterun sessions telegram get --session-ref <display_name>
oysterun sessions telegram get --session-id <session_id>
oysterun sessions telegram enable --session-id <session_id> --update-config
oysterun sessions telegram disable --session-id <session_id>
oysterun sessions telegram update --session-id <session_id> --telegram-enabled true --update-config

Setup / Enable Flow

When the Owner asks to set up Telegram, do real setup through the CLI instead of only describing the skill path.

1. Check status first:

oysterun sessions telegram get

2. If Telegram already has local config but is disabled, enable it and persist the shared config:

oysterun sessions telegram enable --update-config

3. If setup values are missing, ask the Owner for:

TELEGRAM_BOT_TOKEN
TELEGRAM_ALLOWED_USERS

TELEGRAM_ALLOWED_USERS=. means allow all Telegram users.

4. Persist setup values through Oysterun local/shared config:

oysterun sessions telegram update \
  --telegram-enabled true \
  --telegram-bot-token "$TELEGRAM_BOT_TOKEN" \
  --telegram-allowed-users "$TELEGRAM_ALLOWED_USERS" \
  --update-config

Do not claim that a bot token pasted by the Owner is automatically exposed or force a token rotation gate. The Host is Owner-controlled. Write the provided token through the Oysterun CLI so it lands in .oysterun/local.json, not in cloneable source files.

Commands

• telegram status
• sessions telegram get
• sessions telegram enable
• sessions telegram disable
• sessions telegram update

P183/P307 Runtime Authority

P183/P307 runtime authority alignment preserves this skill's per-session Telegram setup path while making all installed product skill commands usable from a live Host session through Host-injected product runtime environment: OYSTERUN_HOST_ORIGIN, OYSTERUN_CAPABILITY_TOKEN, OYSTERUN_SESSION_ID, OYSTERUN_AGENT_ID, and OYSTERUN_CLI_BIN. Inside a live Host session, helper scripts and direct command examples must execute the injected CLI from OYSTERUN_CLI_BIN; do not call bare oysterun, because it may resolve to a globally installed package with older command behavior. That authority is Host-wide for installed Oysterun product skills, so one live session may target another live session's Telegram setup by --session-ref when the user asks. Do not ask an in-session agent to run dashboard login for these commands. Explicit --token is the operator override; external operator shells may still use dashboard CLI auth.

Guardrails

• Telegram setup is per-session and telegram.enabled defaults off.
• Use --update-config when the Owner wants Telegram setup to persist in the current agent folder.
• Normal product behavior must not depend on a global Telegram product flag.
• Live Host sessions use Host-injected product runtime env for current-session Telegram status/setup; do not ask the agent to perform oysterun auth login for those in-session checks.
• External operator shells may still use dashboard CLI auth, saved profiles, or explicit --token for dashboard/global status.
• Do not expose telegram feature enable, telegram feature disable, or telegram send as normal product commands.
• Do not call Telegram Host endpoints directly from this skill.
• Do not print bot tokens, allowed-user secrets, dashboard tokens, cookies, passwords, auth headers, or raw profile files.