# Lingtai Update Install

> Use when installing or building the lingtai-tui and lingtai-portal binaries.

- Skill: `lingtai-ai/lingtai-update-install` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lingtai-ai/lingtai-update-install`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lingtai-ai/lingtai-update-install/raw
- Safety review: WARNING
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lingtai-ai (https://skillmd.com/u/lingtai-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lingtai-ai/lingtai-update-install

---


# Install and build

Nested `lingtai-update` reference. The supported public first-install path is:

```bash
curl -fsSL https://lingtai.ai/install.sh | bash
```

`install.sh` resolves the latest release from GitHub; the source option selects
the download route, not version authority
(`--source auto|github|mirror`, default `auto`, or `LINGTAI_SOURCE`;
`--source gitee` is retired), prefers a matching `lingtai-<tag>-<os>-<arch>.tar.gz`
asset, and falls back to building the release source when no asset is
available. It installs both binaries into a selected bin directory and
prepares the TUI-managed runtime; that runtime is not a second TUI update path.

On the verified-bundle path the Python `lingtai` runtime is installed from the
bundle's pinned kernel artifact by explicit local file path after a SHA256
check — never by requesting the package name `lingtai` from an index. Only that
artifact's third-party dependencies use a package index, and exactly one:
a non-empty `LINGTAI_PYPI_INDEX_URL` always wins, otherwise the provider that
actually served the bundle manifest decides (the lingtai.ai mirror →
`https://mirrors.tuna.tsinghua.edu.cn/pypi/web/simple`, GitHub →
`https://pypi.org/simple`). There is no `--extra-index-url`. See
`reference/mainland-china/SKILL.md` for the reachability reasoning; Windows
(`install.ps1`) and `--latest` are outside this behavior.

For a deliberate source build, the current repository layout is:

```bash
cd tui && make build
cd ../portal && make build
```

The portal build first needs its checked-in web dependencies and frontend build
(`cd portal/web && npm ci && npm run build`); `portal/embed.go` then embeds the
result into `lingtai-portal`. Go and Node are build prerequisites, not runtime
dependencies of the portal binary.

The installer accepts `--version <tag>`, `--ref <ref>`, `--bin-dir <dir>` or
`--prefix <dir>`; its `--update --prefix <prefix> --version <tag>
--non-interactive` form is the source updater contract. Prefer the public
`lingtai.ai` URL for new installs. Homebrew remains a supported migration path;
bare `pip install/upgrade lingtai` is kernel development/diagnosis guidance, not
normal TUI update guidance.