---
name: lingtai-ai/lingtai-update-homebrew
source: https://app.decimal.ai/s/lingtai-ai-lingtai-update-homebrew@1/SKILL.md
source_sha256: 8a97a29186e4
---

# Homebrew path and tap exploration

Nested `lingtai-update` reference. The supported formula is
`lingtai-ai/lingtai/lingtai-tui`. `brew install` still works for a first
install, but `/update-tui`, `lingtai-tui self-update`, and `lingtai-tui
doctor` no longer run `brew upgrade` against it — a detected Homebrew install
now migrates (with explicit consent) to LingTai's native installer instead;
see the `update-tui` reference. The commands below remain useful for manual
exploration of an existing Homebrew install. The migration step itself never
touches the old formula/keg; removing it is a separate, interactive-only
consent step (the startup "Remove the old Homebrew installation now? [y/N]"
prompt, see `update-tui`) — `self-update` and `doctor` never run `brew
uninstall` and only report the manual command:

```bash
brew install lingtai-ai/lingtai/lingtai-tui
brew update
brew upgrade lingtai-ai/lingtai/lingtai-tui
brew info lingtai-ai/lingtai/lingtai-tui
brew --repository
```

The release workflow writes `Lingtai-AI/homebrew-lingtai/lingtai-tui.rb` from
the tagged source tarball, builds `tui` and `portal`, and runs the TUI version
smoke test. To inspect the installed formula and its origin, pair `brew info`
above with `brew cat lingtai-ai/lingtai/lingtai-tui`; `brew --repository`
locates the checkout, so inspect the reported tap directory. Treat manual tap
edits as debugging only; release automation owns normal formula updates.

The formula builds Go and the embedded portal frontend and runs its own
connectivity probes. The mainland reference owns the `HOMEBREW_*` proxy and
registry overrides and their non-guaranteed mirror behavior.