odoo_ls_server.
In normal use your editor launches it automatically via the LSP extension.
You can also invoke it directly for parse-mode batch analysis or debugging.
Parse mode flags
Parse mode runs OdooLS as a one-shot diagnostic extractor: it analyzes the codebase, writes diagnostics to a JSON file, then exits. Enable it with--parse.
Short form:
-pRun in parse mode. OdooLS extracts diagnostics from the codebase and exits instead of
starting a long-running language server.Short form:
-cPath to the Odoo community source directory.
Required when running in parse mode.Short form:
-aOne or more addon directories to analyze in parse mode.
Pass the flag multiple times or space-separate values.Short form:
-tRestrict diagnostic output to files inside these directories.
By default, all Odoo source directories and addon paths are tracked.
Use this flag to limit the report to a specific subset.Path to the Python executable to use during parse mode analysis.
Short form:
-oFile path where parse mode writes diagnostic results in JSON format.Short form:
-sOne or more directories containing additional type stubs.
Each stub package must be in a subdirectory named after the package it stubs.Disable the bundled typeshed stubs for external packages.
Standard library stubs are still included — they are required for analysis.
Use this when supplying your own third-party package stubs via
--stubs.Alternative path to Python standard library stubs.
When not supplied, OdooLS uses its bundled typeshed stdlib stubs.
Server flags
These flags control how the long-running language server process behaves.Explicit path to an
odools.toml configuration file.
Overrides the default file-discovery behavior (walking up the directory tree).Process ID (PID) to watch. When the watched process stops, OdooLS exits automatically.
This is the standard LSP mechanism editors use to ensure the server is cleaned up
when the editor closes.
This flag is available on Unix only.
Connect over TCP instead of stdio.
Intended for debugging; not needed in normal editor integration.
Logging flags
Minimum log level to emit.
Lower levels produce more output. Use
error for quiet operation in CI.| Level | Description |
|---|---|
trace | Extremely verbose; logs every internal step |
debug | Detailed debugging information |
info | General operational events |
warn | Potentially unexpected conditions |
error | Failures only |
Directory where log files are written.
Defaults to a
logs/ subdirectory next to the odoo_ls_server binary.