mergeway-lsp

Run the Mergeway language server over stdio and configure its logging.

Synopsis: Run the Mergeway Language Server Protocol server over stdio.

Usage

mergeway-lsp [flags]

mergeway-lsp is a standalone binary. It does not read mergeway-cli global flags such as --root or --format.

Flag	Description
`--log-file`	Write server logs to the given file path.
`--log-level`	Set the log level: `debug`, `info`, `warn`, or `error`.
`--log-stderr`	Write server logs to stderr instead of discarding them.

If you omit all logging flags, the server stays quiet and reserves stdout for JSON-RPC traffic.

Start the server and wait for framed LSP messages on stdin:

mergeway-lsp

Enable debug logging on stderr while testing a client manually:

mergeway-lsp --log-stderr --log-level=debug

Write logs to a file instead of stderr:

mergeway-lsp --log-file /tmp/mergeway-lsp.log --log-level=debug

The server accepts environment-variable equivalents for its logging settings:

Command-line flags take precedence over environment variables when both are set.

Keep stdout protocol-only. Human-readable output on stdout will break editor integration.
In normal use, your editor launches mergeway-lsp for you rather than you starting it by hand.
The server discovers Mergeway roots from the files the editor opens and uses the same validation core as mergeway-cli validate.

Run mergeway-lsp manually — startup basics and current capabilities.
Set up mergeway-lsp in VS Code and Neovim — editor wiring examples.
mergeway-cli validate — compare editor diagnostics with CLI validation output.