lsp.txt · part 1

Interact with Language Server Protocol (LSP) servers to get code intelligence fe

Source: packages/opencode/src/tool/lsp.txt, characters 0–1303, SHA-256 8f25f3ea038c4fc7.

Jev judged model-facing (confidence 0.86; role tool). This is a classifier judgment, not proof of delivery.

Readable text: Interact with Language Server Protocol (LSP) servers to get code intelligence features. Supported operations: - goToDefinition: Find where a symbol is defined - findReferences: Find all references to a symbol - hover: Get hover information…

Interact with Language Server Protocol (LSP) servers to get code intelligence features.

Supported operations:
- goToDefinition: Find where a symbol is defined
- findReferences: Find all references to a symbol
- hover: Get hover information (documentation, type info) for a symbol
- documentSymbol: Get all symbols (functions, classes, variables) in a document
- workspaceSymbol: List project-wide symbols matching a query string
- goToImplementation: Find implementations of an interface or abstract method
- prepareCallHierarchy: Get call hierarchy item at a position (functions/methods)
- incomingCalls: Find all functions/methods that call the function at a position
- outgoingCalls: Find all functions/methods called by the function at a position

All operations require:
- filePath: The file to operate on
- line: The line number (1-based, as shown in editors)
- character: The character offset (1-based, as shown in editors)

workspaceSymbol also accepts:
- query: A query string to filter symbols by. Empty string requests all symbols.

For workspaceSymbol, filePath is not sent in the LSP workspace/symbol request. It is used by opencode to select and start the matching LSP server.

Note: LSP servers must be configured for the file type. If no server is available, an error will be returned.