Repository navigation
v0.22.2 — MCP failures say why; navbar shows the workspace
v0.22.2 — MCP failures that say why, and a navbar that says where
A dead MCP server used to report nothing but "error — server exited
(code 1)": the reason it died (npm network error, old Node, a launcher
that isn't installed) was thrown away because stderr was never read. Now
the full story is captured and surfaced — and a missing npx transparently
falls back to bunx on machines that have bun. The navbar also grew a
workspace segment so you always know which folder the agent is in.
❯ tagent doctor · v0.22.2
✘ mcp context7: error — server exited (code 1): npm ERR! code
ENOTFOUND — full reason above; /mcp reload retries after fixing
╭─ ✻ Tagent v0.22.2 ── 💬 porting the API ────────╮
╰─ 🤖 build · 📂 tagent-proyek · glm-4.7 · 🔌 2✓ 31 · 4m ─╯
MCP: the failure says why
- server stderr is captured — the exit error carries the last lines of
it, so "code 1" becomes "code 1: npm ERR! code ENOTFOUND" - a missing launcher is named ("cannot start 'npx' — not found on
PATH") with install advice instead of a bare exit code - doctor and the /mcp menu show 160 chars of the reason; calls made
after a death include it too
MCP: npx → bunx fallback
- binary installs ship no Node.js — a configured npx may simply not
exist. When bun is installed, tagent transparently launches the
server with bunx (runs the very same npm packages) - the fallback shows as a note ("npx not on PATH — using bunx")
instead of three dead servers; custom launchers are untouched
Navbar: workspace segment
- the facts row now reads 🤖 build · 📂 my-project · glm-4.7 · 🔌 2✓ 31
— you always know which folder the agent is working in - truncated to 18 cells so long folder names never push the model or
MCP status off the bar
Single-file binaries: download, run, done
One self-contained executable per platform — like the Node.js/Python
downloads. No runtime, no install, no clone: grab the file for your OS,
run it, and both the TUI and the browser GUI just work (the web GUI is
embedded inside the binary and self-extracts on first run).
| File | Platform |
|---|---|
tagent-v0.22.2-windows-x64.exe |
Windows 10+ (64-bit) |
tagent-v0.22.2-windows-arm64.exe |
Windows 10+ on ARM |
tagent-v0.22.2-linux-x64 |
Linux (glibc, 64-bit) |
tagent-v0.22.2-linux-arm64 |
Linux ARM64 (incl. Raspberry Pi 5) |
tagent-v0.22.2-macos-x64 |
macOS Intel |
tagent-v0.22.2-macos-arm64 |
macOS Apple silicon |
| SHA256SUMS.txt | checksums for everything above |
Also linked from the website's download page,
which auto-detects your platform.
Native Windows — no WSL needed
- The builds run the full stack natively: TUI, daemon, web GUI, relay, the 40-provider catalog
- The bash tool uses Git for Windows' bash.exe (auto-detected, override with
TAGENT_BASH);tagent doctortells you if it's missing - Home/config/sessions live in the real Windows user profile (
~/.tagentvia USERPROFILE) - Windows 10+ 64-bit is required (Windows 7/8 and 32-bit are no longer covered)
Install / upgrade
# Linux / macOS
chmod +x tagent-v0.22.2-linux-x64 && ./tagent-v0.22.2-linux-x64 doctor
# Windows (PowerShell) — the .exe runs as-is
.\tagent-v0.22.2-windows-x64.exe doctorVerify a download
sha256sum --check SHA256SUMS.txt # certutil -hashfile <file> SHA256 on Windows