lingtai-update

Routes install, update, detection, and diagnosis tasks for lingtai-tui and lingtai-portal binaries.

692|60|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lingtai-update
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-update
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Updating, installing, or debugging the lingtai-tui and lingtai-portal Go binaries involves multiple install paths (native installer, Homebrew, source builds) and failure modes; this Skill routes each problem to the correct focused reference instead of guessing.

Core Features & Use Cases

  • Install and Build Guidance: Covers the public install.sh installer, release assets, source fallback builds, and manual Go/Node builds for both binaries.
  • Update Command Semantics: Documents /update-tui and lingtai-tui self-update behavior, including Homebrew-to-native migration, PATH resolution checks, and consent-gated Homebrew removal.
  • Install-Method Detection and Diagnosis: Explains install.json-based detection, Homebrew/symlink/unknown classification, and triage steps for failed updates, builds, or migrations.
  • Use Case: When /update-tui reports an unknown install method or a Homebrew migration stalls because /opt/homebrew/bin shadows the native binary on PATH, use this Skill to identify the exact state and the correct recovery command.

Quick Start

Ask the agent to diagnose why lingtai-tui still runs the old Homebrew binary after a successful native migration and what command resolves it.

Frequently Asked Questions about lingtai-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update lingtai-tui to the latest release?

Run /update-tui inside the TUI or lingtai-tui self-update from the shell. Both compare the running binary against the latest GitHub release, detect the install method, and require explicit confirmation before replacing the binary; relaunch the TUI afterward.

How do I install lingtai-tui and lingtai-portal from source?

Run make build in the tui directory, then build the portal frontend with npm ci and npm run build under portal/web before running make build in portal. Go and Node are build prerequisites only, not runtime dependencies.

Why does lingtai-tui still run the old Homebrew version after migration?

On Apple Silicon, /opt/homebrew/bin precedes the native installer's default bin directory on PATH, so the shell still resolves the Homebrew binary. Answer y to the interactive startup prompt to remove the Homebrew formula, or reorder PATH so the native bin dir resolves first.

Does /update-tui upgrade a Homebrew install with brew upgrade?

No. A detected Homebrew install is migrated to LingTai's native installer using the version-pinned install.sh script with --update --non-interactive. self-update and doctor never run brew upgrade or brew uninstall; they only report the manual commands.

How does the installer choose a PyPI index in mainland China?

A non-empty LINGTAI_PYPI_INDEX_URL always wins; otherwise the provider that served the bundle manifest decides, using the Tsinghua TUNA mirror for Gitee and pypi.org for GitHub. Exactly one index is used, and the lingtai package itself is always installed from a checksum-verified local artifact.

What are the limitations of the lingtai-update guidance?

It covers only the TUI and portal Go binaries; Python runtime, kernel install, and kernel update behavior belong to the kernel's system-manual. Windows install.ps1 and --latest main-from-source builds are outside the verified-bundle index-selection behavior.