lingtai-update-diagnosis

Diagnose failed TUI and portal installs, updates, builds, and restarts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a LingTai TUI or portal install, update, build, or restart fails, it is hard to know whether the problem is a PATH conflict, a broken source build, or an incomplete Homebrew-to-native migration. This Skill provides a structured, read-only diagnostic procedure to identify the exact failure point before attempting any fix.

Core Features & Use Cases

  • Read-only identity checks: Runs lingtai-tui doctor, lingtai-tui version, and command -v to establish which binaries are actually resolved on PATH.
  • Migration failure triage: Interprets Homebrew-to-native migration failure lines, distinguishing installer errors, install.json verification failures, binary version mismatches, and Python runtime issues, while confirming the original Homebrew install remains untouched.
  • PATH conflict detection: Explains the recurring 'native install ready but migration not complete' state caused by Homebrew's bin dir preceding the native bin dir on PATH.
  • Use Case: After lingtai-tui self-update reports a failed migration, use this Skill to read the reported failure line, fix the specific native-installer error, and retry without ever running brew uninstall prematurely.

Quick Start

Ask the assistant to diagnose why my lingtai-tui update failed using the lingtai-update diagnosis procedure.

Frequently Asked Questions about lingtai-update-diagnosis

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

FAQPage Schema
How do I diagnose a failed lingtai-tui update?▼

Start with read-only checks: run lingtai-tui doctor, lingtai-tui version, and command -v lingtai-tui lingtai-portal. These reveal which binary is resolved on PATH and whether the install state matches expectations before attempting any fix.

Why does the TUI say migration is not complete after a successful native install?▼

The resolved lingtai-tui on PATH is still the Homebrew binary because Homebrew's bin dir precedes the native bin dir. Answer yes to the removal prompt, run brew uninstall lingtai-ai/lingtai/lingtai-tui manually, or reorder PATH so the native bin dir resolves first.

Should I run brew uninstall after a failed Homebrew-to-native migration?▼

No. A failed migration never touches the Homebrew formula or keg, so there is nothing to clean up. Read the reported failure line, fix the native-installer error it names, then retry with lingtai-tui self-update.

What should I check when a lingtai source build fails?▼

Separate Go module fetch errors from the portal's npm ci and frontend build errors. Confirm the prefix/bin directory exists and the requested tag is a strict vX.Y.Z release, and record the release tag, OS/architecture, and first actionable error.

Does this diagnosis cover Python or kernel runtime errors?▼

No. Python import, venv, or kernel errors are outside this Skill's scope. Those should be handled by following the kernel's system-manual runtime and kernel update manual instead.