Install language servers (gopls, typescript-language-server, pyright, rust-analyzer) and their prerequisite toolchains (Go, Node/npm, rustup) so the lsp tool works. Use when the user asks to enable or install LSP / language-server support, when lsp_enable reports a missing toolchain, or when the lsp tool reports no language server is installed.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Enable the lsp tool for a language by installing its language server — and,
when the server install needs it, the underlying toolchain.
lsp_enable with {"language": "<language>", "action": "dismiss"}.lsp_enable tool over bash whenever the toolchain already
exists; reach for bash only for the prerequisites lsp_enable refuses to
install itself.Work the ladder for each language the user wants:
gopls,
typescript-language-server, pyright-langserver (or
basedpyright-langserver), rust-analyzer — also look in ~/go/bin and
~/.cargo/bin, which the lsp tool searches even when they are off PATH.
Toolchains: go, npm, rustup.lsp_enable with
{"language": "<go|typescript|python|rust>"} and you are done; it runs the
right server install and verifies the binary resolves.lsp query (documentSymbol on an actual source
file). The first query per workspace can take up to a minute while the
server indexes; that is normal.Go (for gopls):
brew install go # macOS
sudo apt-get install -y golang-go # Debian/Ubuntu; or dnf install golang
Or the official downloads at https://go.dev/dl for anything else.
Node/npm (for typescript-language-server and pyright):
brew install node # macOS
sudo apt-get install -y nodejs npm # Debian/Ubuntu
Or nvm (https://github.com/nvm-sh/nvm) when the user prefers per-user installs.
rustup (for rust-analyzer):
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
This is the official rust installer; show the user the command before running it and follow its printed PATH instructions afterwards.
go install drops gopls in ~/go/bin and rustup drops rust-analyzer in
~/.cargo/bin. The lsp tool finds both without PATH changes; other tools
may still want a PATH entry.npx @weave-os/router --pi --lsp go,typescript,python,rust.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Investigate a specific Claude Code session by session ID — correlate the local transcript (`~/.claude/projects/...jsonl`) with the router's production logs to understand what the client rendered vs. what the upstream served. Use when given a session ID and asked "why did X render?" for a Claude Code conversation routed through the router.
中文简介正在准备中。当前显示原文说明。
Investigate a specific Codex CLI session by session ID — correlate the local rollout transcript (`~/.codex/sessions/YYYY/MM/DD/rollout-*-<SESSION_ID>.jsonl`) with the router's production logs to understand what Codex rendered vs. what the upstream served on the /v1/responses path. Use when given a session ID and asked "why did X render?" (missing thinking, missing routing marker, wrong model, tool-call weirdness) for a Codex conversation routed through the router.
中文简介正在准备中。当前显示原文说明。
Switch Codex back to its normal provider for future sessions.
中文简介正在准备中。当前显示原文说明。
Alias for force-model — pin this Codex session to a specific model through the Weave Router.
中文简介正在准备中。当前显示原文说明。
Pin this Codex session to a specific model through the Weave Router.
中文简介正在准备中。当前显示原文说明。
Recipes for the lsp tool — resolving where a symbol is defined, every place it is used, type signatures and docs, file outlines, and compiler/type errors through a real language server (Go, TypeScript/JavaScript, Python, Rust). Use when navigating or explaining code by symbol, finding callers or usages, checking what broke after an edit, or deciding between lsp and text search.
中文简介正在准备中。当前显示原文说明。