diff --git a/.github/workflows/lsp.yml b/.github/workflows/lsp.yml
index d58f81b6ce46f..371fa4fd27fd7 100644
--- a/.github/workflows/lsp.yml
+++ b/.github/workflows/lsp.yml
@@ -87,6 +87,9 @@ jobs:
           github-token: ${{ github.token }}
           targets: ${{ matrix.settings.target }}
 
+      - name: Setup Zig
+        uses: ./.github/actions/setup-zig
+
       - name: Build Setup
         shell: bash
         if: ${{ matrix.settings.setup }}
diff --git a/AGENTS.md b/AGENTS.md
index 8ece7755a30ee..f00ec73bea724 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -63,4 +63,4 @@ docs: Update installation instructions
 - Canary VS Code extension packages use `--pre-release`.
 - Non-dry-run releases publish the VS Code extension through the `LSP` workflow using `publish=true`, `dry_run=false`, and a `VSCE_PAT` secret on the protected `vscode-marketplace` environment. This publish path must not block release PR creation or cleanup published npm release state.
 - The `Release` workflow signs and notarizes macOS `turbo` binaries during `build-rust` using static GitHub secrets and `apple-codesign`/`rcodesign`.
-- The `Release` workflow installs Zig during `build-rust` because `turbo` links vendored `libghostty-vt` through `turborepo-ghostty-sys`.
+- The `Release` and `LSP` workflows install Zig during `build-rust` because `turbo` and `turborepo-lsp` link vendored `libghostty-vt` through `turborepo-ghostty-sys`.