tlive

# 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 `notify` tlive only watches + notifies (the shim never holds an approval — prompts stay 100% native); `tlive mode full` turns on remote approval (Allow/Deny from IM/desktop/dashboard); `off` makes every hook a no-op. 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` — set posture (see intro). Persisted to config, takes effect on the next hook; `notify` is the default, `full` = remote approval on. - `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 ...