Agent skill

Tlive

by y49 in y49/tlive

tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex.

MITAuto-check: notesProductivity & Automation

Install Tlive

skills CLI
$ npx skills add y49/tlive --skill tlive -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install y49/tlive tlive --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/y49/tlive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/codex/plugins/tlive/skills/tlive .claude/skills/tlive && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tlive
GitHub stars
214
Used in
1 other repo
Token cost
~1.7k tokens
SKILL.md length
971 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex.

  • Works in 5 steps: No IM messages: tlive status for channel… → Codex has no remote cards: check tlive… → No approval card ever arrives: check… → …
  • Diagnosing tlive
  • SKILL.md covers Commands, Diagnostics, Security model in one breath and First-time onboarding
  • Calls npm

What it does

Tlive is an agent skill from y49/tlive. tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex. Use for configuring or diagnosing tlive, connecting IM platforms, printing session links, or explaining approval behavior. Triggers "tlive", "IM bridge", "phone approvals", "remote terminal", "Telegram/Feishu notifications".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Messaging and chat bots and Web search. It works with Feishu (Lark) and Telegram. The repository describes itself as: Self-hosted remote approvals + live monitoring for Claude Code / Codex — via Telegram, Feishu, or a web terminal. Any subscription or API key. The licence is MIT.

When your agent uses it

  • Diagnosing tlive
  • Connecting IM platforms
  • Printing session links
  • Explaining approval behavior

Example prompts

  • “IM bridge”
  • “phone approvals”
  • “remote terminal”
  • “/tlive”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. No IM messages: tlive status for channel config; tlive logs -f for send
  2. Codex has no remote cards: check tlive status — the companion line must say
  3. No approval card ever arrives: check tlive status — the mode: line must
  4. Claude approval card unanswered (in full or all): the local dialog stays
  5. Web page unreachable: tlive url for the current link (token is in the URL);

What it can do on your machine

Read from SKILL.md and the folder at commit d9a10af. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tlive loads about 1.7k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 971 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:72
    (rm -rf, sudo, .env/.ssh writes…) still asks and no config can lower it.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from y49/tlive at commit d9a10af, republished under its MIT licence (© y49). 971 words, ~1,724 tokens.

Download SKILL.mdSave it as .claude/skills/tlive/SKILL.md (or your agent's skills folder).
name
tlive
description
tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex. Use for configuring or diagnosing tlive, connecting IM platforms, printing session links, or explaining approval behavior. Triggers "tlive", "IM bridge", "phone approvals", "remote terminal", "Telegram/Feishu notifications".

tlive usage guide

tlive is a self-hosted monitoring/approval layer. Claude Code sessions report through global hooks; Codex sessions are watched through an app-server companion process (no hooks, no trust step). Completions and failures land in IM (Telegram/Feishu) and the web dashboard, where you can reply-to-continue. The posture (tlive mode, default notify) decides whether approvals are held for a remote answer, in escalation order: off makes every hook a no-op; notify only watches + notifies (the shim never holds an approval — prompts stay 100% native) and reports to the machine (desktop toast + dashboard) — IM stays quiet about a dialog only the terminal can answer, except once ever per chat, when a card explains why and offers the switch to full; full is the posture that puts approvals on your phone: it turns on remote approval for the main session (Allow/Deny from IM/desktop/dashboard), in parallel with the terminal dialog — first answer wins; all holds sub-agent approvals too, with no terminal dialog for a held one until the window ends, so use it only when nobody is at the keyboard (tlive mode full goes back). Also settable from IM: /mode (a bare /mode replies with the ladder). The daemon auto-starts with new sessions (disable via daemon.autoStart: false).

Commands

  • tlive setup — configure IM credentials + register the Claude/Codex plugins (hooks ride the Claude plugin; Codex needs none). --hooks-only re-registers plugins only; add --claude / --codex to pick a vendor.
  • tlive status — daemon health, effective mode, channels, and the Codex companion state (running / degraded / off; degraded or off = Codex approvals local-only).
  • tlive mode off|notify|full|all — set posture (see intro). Persisted to config, takes effect on the next hook; notify is the default, full = remote approval on, all = also holds sub-agent approvals.
  • tlive run <cmd> — wrap a process: local terminal + live web terminal (QR to open).
  • tlive url — print the dashboard link + QR code.
  • tlive logs -f — follow the daemon log.
  • tlive start / tlive stop — explicit lifecycle (start is rarely needed; sessions lazy-start the daemon unless autoStart is off).

Diagnostics

  1. No IM messages: tlive status for channel config; tlive logs -f for send errors; confirm the daemon is up after starting a session.
  2. Codex has no remote cards: check tlive status — the companion line must say running. off means codex isn't on PATH (or Windows); degraded means codex is there but nothing is answering on the app-server socket — see ~/.tlive/codex-appserver.log. Neither is permanent: tlive keeps checking, so installing or reinstalling codex recovers on its own with no tlive restart. Either way Codex still prompts locally; nothing is ever auto-run.
  3. No approval card ever arrives: check tlive status — the mode: line must say full or all. The default notify never sends approval cards (tool prompts stay local); enable remote approval with tlive mode full.
  4. Claude approval card unanswered (in full or all): the local dialog stays live the whole time (parallel channels, first answer wins); answering locally resolves the remote card as "answered in terminal". The remote window defaults to ~24h (approvals.windowSec, shared by both vendors).
  5. Web page unreachable: tlive url for the current link (token is in the URL); phones need the same LAN (or your own reverse proxy/VPN — tlive has no publicUrl config, and cards never carry the link).
Show full SKILL.md (436 more words)Show less

Security model in one breath

  • Never auto-allow: unanswered → Claude's local dialog governs / Codex's native prompt governs. Deny always carries a reason.
  • Read-only tools (Read/Glob/Grep) pass by default. /safe on also auto-allows routine ops (non-dangerous Bash, non-sensitive edits) — the danger floor (rm -rf, sudo, .env/.ssh writes…) still asks and no config can lower it. /trust on pauses approvals entirely (high risk — pair with allowedSenders).
  • Runtime switches flip the same state from either entrance: IM commands (/mute /trust /safe on|off, /mode for the posture ladder) and the CLI (tlive mute|trust|safe on|off, tlive mode off|notify|full|all). /mute on = go quiet; it silences IM notifications ONLY. The desktop toast is independent of /mute and has no on/off switch of its own: one fires per thing that starts waiting on you (a pending approval, or the idle "waiting for your input" nudge), named with its project and call, and tlive never touches it again — it ages into the notification centre like any other app's, a log rather than live status (the dashboard is the live view). Silence it with your OS's Do Not Disturb, or tlive mode off to stop tlive entirely. A finished turn notifies the desktop too, from the Stop hook and after the same grace as the IM card; a failed tool does not, it blocks nobody.
  • Vendor-side permissions.deny always wins; tlive never overrides it.

First-time onboarding

When the user says "help me set up tlive" (or runs /tlive:setup), walk them through:

  1. tlive status to check the engine; missing → npm i -g tlive.
  2. No channels → collect Telegram (bot token + chat id) or Feishu (appId + appSecret) credentials and merge into ~/.tlive/config.json: { "allowedSenders": [], "adapters": { "telegram": { "token": "…", "chatIdAllowList": ["…"] }, "feishu": { "appId": "…", "appSecret": "…" } } }
  3. tlive start → tlive status to verify channels; tlive url for the dashboard.
  4. Offer remote approval: tlive defaults to notify (watch + notify only). If the user wants to Allow/Deny tool calls from their phone, run tlive mode full (holds each tool call for a remote answer; reversible with tlive mode notify). Leave it in notify if they only want monitoring. If they say they're stepping away and want sub-agent approvals on their phone too, that's tlive mode all — flag the trade plainly: a held sub-agent has no terminal dialog until the window ends, so it only pays off when nobody is at the keyboard (tlive mode full to come back).
  5. Codex needs no extra step — the companion connects as soon as an app-server is answering, and tlive starts one if none is. If status says off/degraded, that's diagnostic info, not a setup task, and it clears itself once codex is installed — don't tell them to restart tlive.

© y49, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/codex/plugins/tlive/skills/tlive of y49/tlive.

Open the folder on GitHubat commit d9a10af

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in y49/tlive, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Tlive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tlive compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tlive this skilly49/tlive2141 repos~1.7kAutomated safety check: NotesMIT
Easy Openclawdaheiai/easy-openclaw112—~1.7kAutomated safety check: NotesNone
Message Push0xranx/golembot323—~984Automated safety check: PassMIT
Task Manager0xranx/golembot323—~694Automated safety check: PassMIT
Cc Connectarchibate/dotfiles-opencode108—~1.2kAutomated safety check: PassNone
Claude To Imop7418/Claude-to-IM-skill2.9k—~3.4kAutomated safety check: NotesMIT

Similar skills

  • Easy Openclaw

    daheiai/easy-openclaw

    OpenClaw 配置优化向导。采用“第 0 层测试观测(可选)+ 前 3 轮优化 + 第 4 轮接入扩展”流程:基础推荐层(含联网搜索与权限模式)、渠道增强层(Discord/Feishu/Telegram 分支优化)、Skills 推荐层(可执行可跳过)、新增渠道接入引导(可跳过)。用于帮助用户快速完成 OpenClaw 初始化或优化配置。用户说到“优化…

    112 GitHub stars~1.7k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check: notes
  • Message Push

    0xranx/golembot

    Send proactive messages to IM groups or individual users via the gateway Send API.

    323 GitHub stars~984 tokensUpdated 9 days ago
    Productivity & AutomationAuto-check passed
  • Task Manager

    0xranx/golembot

    Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API.

    323 GitHub stars~694 tokensUpdated 9 days ago
    Productivity & AutomationAuto-check passed
  • Cc Connect

    archibate/dotfiles-opencode

    This skill should be used when sending images, files, or notifications back to the user via messaging platforms (Discord, Feishu, Telegram, etc.) through cc-connect.

    108 GitHub stars~1.2k tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check passed
  • Claude To Im

    op7418/Claude-to-IM-skill

    Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone.

    2.9k GitHub stars~3.4k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check: notes
  • Conversation History

    dashhuang/openclaw-chat-history-import

    A skill your agent uses when the user asks what was said earlier in a chat, wants an old decision, exact wording, prior links, or suspects the agent forgot conversation context across Telegram…

    144 GitHub stars~912 tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check passed

Questions about Tlive

What does Tlive do?

tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex. Tlive is an agent skill from y49/tlive. tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex.

When should I use Tlive?

Tlive fits situations like: diagnosing tlive; connecting IM platforms; printing session links; explaining approval behavior.

How do I install Tlive in Claude Code?

Run `npx skills add y49/tlive --skill tlive -a claude-code`. Or copy the skill folder (plugins/codex/plugins/tlive/skills/tlive in y49/tlive) into .claude/skills/tlive in your project. Claude Code loads it when a task matches its description.

How do I install Tlive in Codex?

Run `npx skills add y49/tlive --skill tlive -a codex`. Or copy the skill folder (plugins/codex/plugins/tlive/skills/tlive in y49/tlive) into .agents/skills/tlive in your project. Codex loads it when a task matches its description.

Can I use Tlive in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add y49/tlive --skill tlive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tlive, .gemini/skills/tlive, .github/skills/tlive and .opencode/skills/tlive in your project.

What does Tlive need to run?

Going by SKILL.md and its folder, Tlive needs the command-line tools its instructions call (npm). Our summary lists: Node.js.

Does Tlive access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Tlive safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Tlive use?

Tlive is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tlive use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tlive?

Skills that share tags, products or a category with Tlive: Easy Openclaw (daheiai/easy-openclaw, 112 stars), Message Push (0xranx/golembot, 323 stars), Task Manager (0xranx/golembot, 323 stars) and Cc Connect (archibate/dotfiles-opencode, 108 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tlive?

y49 (a GitHub user) maintains it in y49/tlive, which has 214 GitHub stars. The repository was last updated on September 9, 2026.

Source: y49/tlive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.