Connect VS Code

This first installation task connects one language server and verifies diagnostics. An explicit beskid.lsp.server.path has priority. Without it, the extension checks each fallback in a fixed order.

Prerequisites

Install VS Code and complete Install Beskid. Keep the Main.bd file from the first-program task.

Actions

1. Install the stable extension from Open VSX:

   code --install-extension beskid.beskid-vscode

2. Open the directory that contains Main.bd in VS Code.

3. Leave beskid.lsp.server.path empty to use automatic selection. The extension checks a managed binary first. It then checks a preferred bundled binary and a CLI-backed server.

4. To select a specific server, set beskid.lsp.server.path to the absolute path of beskid_lsp or beskid_lsp.exe.

5. Save Main.bd. The Problems panel must show the current analysis result.

6. Change return 0; to return missingValue;. The saved file must produce a diagnostic.

7. Restore return 0;. The saved file must clear the diagnostic.

flowchart TD
  accTitle: Editor and language server
  accDescr: Follow the extension fallback order until one language server starts or selection stops with an error.
  A[Open a .bd file] --> B[Extension activates]
  B --> C{Explicit path?}
  C -->|Yes| Z[Start selected server]
  C -->|No| D{Managed binary?}
  D -->|No| E{Bundled binary preferred and present?}
  E -->|No| F{CLI-backed server available?}
  F -->|No| G{Automatic bootstrap enabled and development mode off?}
  G -->|Yes| H[Install and retry managed or CLI-backed server]
  H --> L{Retry found a server?}
  L -->|Yes| Z
  L -->|No| I{Compiler workspace release binary?}
  G -->|No| I
  I -->|Yes| Z
  I -->|No| J[Compiler workspace development fallback or stop]
  D -->|Yes| Z
  E -->|Yes| Z
  F -->|Yes| Z
  Z --> K[Show diagnostics]

Diagram text

1. Opening a .bd file activates the extension. An explicit path selects that server.
2. Without an explicit path, the extension checks the managed binary and then the preferred bundled binary.
3. Next, it checks for a CLI-backed server. When development mode is off, enabled automatic bootstrap can install a toolchain. It then retries the managed and CLI-backed paths.
4. A compiler-workspace release binary is the next fallback. The compiler-workspace fallback can then use configured development mode. These paths apply only when their required workspace or development configuration exists.
5. The selected server analyzes the document and sends diagnostics to VS Code. If no supported path applies, selection stops with an actionable error.

Expected result

The Problems panel shows a diagnostic after the invalid edit and clears it after you restore Main. Only one selected language-server process supplies the document diagnostics.

Recovery

If the extension cannot start a server, run Beskid: Install LSP or repeat beskid lsp install --release-tag <selected-lsp-tag>. Use the LSP tag that corresponds to the selected CLI channel or immutable version. See Install Beskid for the matching tags. If multiple installations cause ambiguity, set the absolute beskid.lsp.server.path. Use the extension output channel to find the selected command and path.

Next task

Use first-day troubleshooting if a check still fails. After the first installation succeeds, continue to the daily VS Code project workflow.