القائمة
Use when operating /update-tui or lingtai-tui self-update.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Anything you need to know about LingTai TUI. Read this first for the stable mental model, major-feature map, interface and slash-command help, or the correct source/manual route for a TUI question. It stays thin: exact command prose lives in the localized help assets, precise Go structure lives in `lingtai-tui-anatomy` plus the repository ANATOMY graph, and independent domains such as presets, Portal, tutorials, updates, and addons keep their own top-level skills.
Use when updating, installing, building, or debugging lingtai-tui or lingtai-portal, including /update-tui, install-method detection, Homebrew, source builds, tap inspection, or mainland-China connectivity.
Nested lingtai-dev-guide reference for contribution workflow: issue/worktree/PR discipline, worktree inventory and exact-object approval gates, daemon decomposition, portfolio sweeps, repo-specific build/test commands, skill changes, and anatomy maintenance.
Router for contributing to the LingTai project. Use this when you are about to change LingTai code or docs, set up a dev environment, navigate the Go TUI/portal repo or Python kernel, develop MCP addons, troubleshoot a running network, audit security, run a runtime self-check, get a PR review-ready, or steward a new skill. This is for developers and contributors; for end-user lessons, use tutorial-guide.
Official-source-led manual for the TUI `codex-pool` template, including the codex-auth-pool.json format and manual-edit protocol.
How a saved preset becomes the running default, first-run/setup choice semantics, propagation, and what /refresh actually switches.
| name | lingtai-update-command |
| description | Use when operating /update-tui or lingtai-tui self-update. |
| version | 1.0.0 |
| last_changed_at | 2026-07-18T00:00:00Z |
| maintenance | If you find stale or incorrect information here, use the lingtai-issue-report skill to assemble evidence and obtain per-issue human consent before filing an issue. Never include secrets, credentials, tokens, or private paths. |
/update-tuiNested lingtai-update reference. /update-tui compares the running TUI with
the latest GitHub release, detects the install method, and requires explicit
confirmation before changing the TUI binary; the selected distribution may also
refresh the co-installed portal binary. It never updates the Python kernel,
presets, or utility library, and never auto-restarts the current TUI — relaunch
after a successful update.
https://raw.githubusercontent.com/Lingtai-AI/lingtai/<tag>/install.sh
with --update --prefix <native-prefix> --version <tag> --non-interactive,
accepting and updating existing managed runtime/receipt state in place while preserving the exact target tag
rather than using ordinary first-install mode.
then verifies the new install.json source metadata, the binary version at
the new bin_dir, and the Python runtime. On any migration failure the old
Homebrew formula/keg remains exactly as usable as before the attempt — the
migration step itself never runs brew.
Before reporting success, the migration also resolves lingtai-tui on PATH
and checks it against the freshly installed binary — on a standard
Apple-Silicon Homebrew host, /opt/homebrew/bin is earlier on PATH than
install.sh's default native bin dir, so a fresh native install alone does
not make the shell start running it. When PATH still resolves to
Homebrew, the migration reports "native installed, migration not complete"
instead of "Migrated!", and every update entry point (startup prompt,
self-update, doctor) re-detects and re-reports that same truthful state
on every subsequent run — it does not re-run the installer and does not
claim success until PATH actually resolves the native binary. Only once
that is confirmed does detectTUIInstallMethod report the install as
source/user-local going forward, so subsequent updates use the source path
below instead of brew.install.sh --update --prefix ... --version <tag> --non-interactive path and verifies the result.Homebrew removal is a separate, interactive-only decision. Once a native
install is verified — either right after a fresh migration's PATH takeover
succeeds, or on a later launch that redetects an existing verified-but-shadowed
install — the interactive startup prompt (not /update-tui's Bubble Tea
view, not self-update, not doctor) asks a concrete second question:
"Remove the old Homebrew installation now? [y/N]" (default No). Only an
explicit "y" runs the single injected uninstall
(brew uninstall lingtai-ai/lingtai/lingtai-tui, exactly this formula), then
re-resolves lingtai-tui on ordinary PATH and requires it to match the
verified native binary before reporting cleanup complete — the currently
running Homebrew process is never treated as proof. A declined prompt, a
failed uninstall, or PATH still not resolving to the native binary afterward
all leave removal reported as pending, and the same question is asked again
on the next interactive launch. self-update, doctor, and /update-tui
never ask this question and never run brew uninstall — they only report
both the native and Homebrew paths/versions and the exact manual command.
lingtai-tui self-update is the shell command for the same manual update
surface when the interactive TUI is unavailable. lingtai-tui doctor is a
broader repair/report path that can also run the detected TUI backend; use this
skill only for its TUI/portal side and defer Python-runtime decisions to the
kernel system-manual runtime/kernel update manual.