skills.rest
Lingtai-AI
Lingtai-AIOFFICIAL
Explore all skills by this author →
GitHub

lingtai-update-command

Updates the lingtai-tui binary by comparing GitHub releases and migrating Homebrew installs to native installers.

692|60|Updated Mar 15, 2026
Search Tags:#installer#update#tui#Homebrew#self-update#Migration#GitHub Release
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-update-command
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lingtai-update-command
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-update/reference/update-tui
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-update-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping the lingtai-tui terminal client current is error-prone: installs may come from Homebrew or a native installer, PATH shadowing can hide a fresh binary, and partial migrations can leave the system in a misleading state. This Skill governs the /update-tui and self-update flows so updates are verified, truthful, and never destructive.

Core Features & Use Cases

  • Release comparison and install-method detection: Compares the running TUI against the latest GitHub release and detects whether the install is Homebrew, source/user-local, or unknown before acting.
  • Homebrew-to-native migration: Runs the version-pinned install.sh script with --update and --non-interactive, verifies the receipt, binary version, and Python runtime, and honestly reports when PATH still resolves to the old Homebrew binary.
  • Guarded cleanup and recovery: Homebrew removal happens only through an explicit interactive prompt, legacy runtimes are preserved via --skip-python recovery, and unknown or dev versions receive guidance instead of guesses.
  • Use Case: A user on an Apple-Silicon Mac originally installed lingtai-tui via Homebrew. Running /update-tui migrates to the native installer, detects that /opt/homebrew/bin still shadows the new binary on PATH, and reports the truthful pending state until the native binary actually resolves.

Quick Start

Ask the agent to run /update-tui to check the current lingtai-tui version against the latest GitHub release and perform a verified update.

Frequently Asked Questions about lingtai-update-command

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

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

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

How does the Homebrew to native installer migration work?▼

The update runs the version-pinned install.sh script with --update, --non-interactive, and the target tag, then verifies the install receipt, binary version, and Python runtime. The migration never runs brew itself, and the old Homebrew installation remains usable if anything fails.

Why does lingtai-tui still run the old version after a native install?▼

On Apple-Silicon Homebrew hosts, /opt/homebrew/bin appears earlier on PATH than the native install directory, so the shell keeps resolving the old binary. The update reports this as native installed but migration not complete until PATH actually resolves the native binary.

Does /update-tui remove the old Homebrew installation automatically?▼

No. Homebrew removal only happens through a separate interactive startup prompt that defaults to No, and only an explicit yes runs brew uninstall for the exact formula. self-update, doctor, and /update-tui never run the uninstall themselves.

What happens to a legacy ~/.lingtai-tui/runtime during update?▼

The documented recovery path is a TUI-only install with --skip-python or --skip-venv, which preserves the legacy runtime unchanged and publishes native binaries beside it. The standalone fix.sh creates a parallel runtime and never overwrites the legacy one.

Does /update-tui update the Python kernel or presets?▼

No. The update only touches the TUI binary and optionally the co-installed portal binary. Python kernel and runtime decisions are deferred to the kernel system-manual update path, and the running TUI is never auto-restarted.

Related Skills

Explore More Software Engineering Skills→
regenrekregenrek
131

homebrew-publish

Automate publishing CLIs/TUIs to Homebrew via a personal tap.

Community
Advanced
HugoAlmeidaMoreiraHugoAlmeidaMoreira

debugging-hermes-tui-commands

Diagnose and fix cross-layer command issues across Python backend, TUI gateway, and Ink frontend.

Community
Intermediate
alibabaalibaba
327

upgrade-alinux-kernel

Upgrade Alinux kernel versions on Alibaba Cloud ECS instances with pre-flight checks and post-upgrade validation.

Official
Intermediate
JoeCP17JoeCP17
8

daily-upgrade

Upgrade Homebrew packages, sync the Brewfile, and verify RTK hooks.

Community
Intermediate