This content describes the most recent release of the CodeQL CLI. For more information about this release, see https://github.com/github/codeql-cli-binaries/releases.
To see details of the options available for this command in an earlier release, run the command with the
--help option in your terminal.
codeql execute language-server --check-errors=<checkErrors> <options>...
[Plumbing] On-line support for the QL language in IDEs.
This command is only relevant for authors of QL language extensions for IDEs. It is started by the IDE extension in the background and communicates with it through a special protocol on its standard input and output streams.
[Mandatory] How to check errors. One of: ON_CHANGE, EXPLICIT.
This works like the similar option to codeql query compile (q.v.).
There are no
--library-path options, as the
corresponding values are provided online by the IDE extension through
the language server protocol.
(Note: On Windows the path separator is
Carry out actions a single main thread rather than in a threaded executor.
Show this help text.
[Advanced] Give option to the JVM running the command.
(Beware that options containing spaces will not be handled correctly.)
Incrementally increase the number of progress messages printed.
Incrementally decrease the number of progress messages printed.
[Advanced] Explicitly set the verbosity level to one of errors,
warnings, progress, progress+, progress++, progress+++. Overrides
[Advanced] Write detailed logs to one or more files in the given directory, with generated names that include timestamps and the name of the running subcommand.
(To write a log file with a name you have full control over, instead
--log-to-stderr and redirect stderr as desired.)
[Advanced] Controls the location of cached data on disk that will
persist between several runs of the CLI, such as downloaded QL packs and
compiled query plans. If not set explicitly, this defaults to a
.codeql in the user's home directory; it will be
created if it doesn't already exist.