tlive
tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex.
Connecting the steps of a workflow
What it does
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).
Read more
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 re
Use for configuring or diagnosing tlive, connecting IM platforms, printing session links, or explaining approval behavior
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the one file in the skill’s folder on GitHub; none is a script or program.
Installs other software
Following it will install packages (npm, pip, brew or similar). Those come from their own publishers, not from this skill.
How we know
The SKILL.md contains package-install commands.
No known risk pattern found
Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit d9a10af by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to y49/tlive: 2026-09-09 (26 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end