Initialize the scheme-langserver connection.

Must be called before any other LSP tool. Provides the project root directory so the language server can resolve imports and analyze the codebase.

Args: root_dir: Project root directory. langserver_path: Optional path to a specific scheme-langserver executable. If provided, it overrides environment variables and project config. This is useful for switching between scheme-langserver builds at runtime, e.g. when debugging a local development build.

Export a debug report for scheme-langserver upstream issue reporting.

The report contains the LSP traffic log, open project files, environment info, and server stderr. Review before sharing publicly — it includes source code.

When to use: scheme-langserver crashed or returned clearly wrong results, and you want to help debug by generating a report for the upstream issue tracker (https://github.com/ufo5260987423/scheme-langserver/issues).

Gracefully shut down the scheme-langserver connection.

Restart the scheme-langserver connection and reopen tracked documents.

Use this when you want scheme-langserver to pick up configuration changes (e.g. a new cache_path), switch to a different executable, or recover from a stuck server. After restarting, all currently open files are re-opened automatically so the server state is restored.

Args: root_dir: Project root directory. If omitted, the previously used root_dir is reused; if there is none, it is inferred from open documents or the current working directory. langserver_path: Optional path to a specific scheme-langserver executable. If provided, it overrides environment variables and project config. This lets you instantly switch to a local build for debugging or comparison.

Open a file in the language server (like opening a tab in an editor).

The server needs to know file contents before it can provide hover, completion, or diagnostics for that file.

When to use: When you start working on a Scheme file. Keep the file open for the duration of the session; do NOT open and close repeatedly.

Notify the language server that a file has changed (like pressing Save).

Send the new full text of the file. This keeps the server's internal state in sync with the actual file contents.

When to use: IMMEDIATELY after you modify a Scheme file via filesystem tools (WriteFile/StrReplaceFile). If you skip this step, subsequent diagnostics and queries will operate on stale content.

Close a file in the language server.

When to use: When you are completely done with a file or at session end. Do NOT close files just because you paused editing; frequent open/close wastes server resources.

Show hover tooltip (type, docs) for the symbol under the cursor.

Like hovering the mouse over an identifier in an IDE.

Confidence: MEDIUM. Type inference is experimental; info about macro-expanded identifiers may be inaccurate. Cross-check with your knowledge.

Args: file_path: Absolute path to the file. line: Zero-based line number. character: Zero-based character (column) position.

Trigger auto-completion at the cursor position.

Like pressing Ctrl+Space in an IDE. Returns identifiers available in the current scope, including local bindings (let, lambda parameters) that may not be obvious from a simple text search.

Confidence: MEDIUM. The list may miss identifiers generated by macros.

Go to Definition: jump to where the symbol is defined.

Like pressing F12 in an IDE. Returns file URI, line, and column.

Confidence: HIGH. Reliable for locating definitions across files.

Find All References: list every usage of the symbol across the workspace.

Like Shift+F12 in an IDE.

Confidence: HIGH. Reliable for assessing impact before refactoring.

Args: include_declaration: Whether to include the definition site in the results.

Compute workspace edits to rename a symbol.

Returns a set of text document edits that can be applied to safely rename the symbol across all files.

Limitation: rename is on the scheme-langserver roadmap and may return -32601 "method not found". If so, fall back to manual renaming.

Get signature help for a function call.

Shows parameter names and types for the function being called at the given position.

Limitation: signatureHelp is on the scheme-langserver roadmap and may return -32601 "method not found". If so, fall back to your own knowledge.

Show the file's symbol outline (functions, variables, macros).

Like the Outline / Structure panel in an IDE.

Confidence: MEDIUM. Symbols generated by macros may be missing.

Search symbols across the entire workspace.

Like Ctrl+T / Go to Symbol in an IDE. Returns all symbols matching the query string across all indexed files.

Confidence: MEDIUM. Accuracy depends on index completeness. Requires scheme-langserver >= 2.1.0.

Get code actions (quick fixes, refactorings) for a range.

Limitation: codeAction is on the scheme-langserver roadmap and may return -32601 "method not found" or behave incompletely.

Get diagnostic messages (errors, warnings) from the language server.

When to use: After lsp_change to check for errors, like IDE real-time linting. Also useful before finishing a task to ensure no errors were introduced.

Why this matters for Scheme: S-expressions are catastrophically sensitive to bracket balance. A single missing or extra parenthesis can render the entire file unparseable. Diagnostics will catch unmatched brackets, tokenizer errors, and structural syntax failures with high reliability — things LLMs often miss by eye. scheme-langserver 2.1.2+ restored clear bracket-mismatch diagnostics (unclosed parenthesis, unexpected close bracket) in the fault-tolerant tokenizer. Always pull diagnostics after significant edits.

Confidence: HIGH for basic syntax (brackets, undefined ids). MEDIUM/LOW for semantic errors and implementation-specific extensions (Chez-specific forms may be falsely flagged).

Args: file_path: If provided, returns diagnostics for that file only. If omitted, returns diagnostics for all open files.