REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Self-hosted remote approvals + live monitoring for Claude Code / Codex — via Telegram, Feishu, or a web terminal. Any subscription or API key.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/y49-tlive)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 tlive | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | y49 | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 215 | 465,460 | 233,910 | 149,364 | 144,149 |
| 最近代码更新 | 2026年11月9日 | 2026年11月17日 | 2026年4月20日 | 2026年11月17日 | 2026年11月17日 |
| 许可证 | MIT | MIT | – | Apache-2.0 | MIT |
y49 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodexCursor
依据开发者 README 和 repo 中的文件夹
GitHub account y49 (person), 7 years old
★ 215 stars, few users so far · code last changed 2026年11月9日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit a2dc510 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (339). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /tlive,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 tlive 文件夹放到 ~/.agents/skills/tlive
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 tlive
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
6,931 个字符 · 在 GitHub 打开完整文件
---
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).
## 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 + chat id `oc_…`) credentials and merge into `~/.tlive/config.json`:
`{ "allowedSenders": [], "adapters": { "telegram": { "token": "…", "chatIdAllowList": ["…"] }, "feishu": { "appId": "…", "appSecret": "…", "chatId": "oc_…" } } }`
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.
提问、分享技巧或报告无法使用。按“有帮助”数量排序。