Configuration and Data Directory
Configuration structures, UI settings and execution paths are different layers. A field's existence does not mean every HTTP entry uses it. Back up before editing; never commit credentials or access tokens.
Global Directory
A nonempty LINGXIZHI_HOME overrides the global directory. Otherwise it is data beside the executable, falling back to ./data if the executable path cannot be resolved. Global configuration is lxz.config.json, MCP configuration is mcp.json, and credentials, licenses and logs also use this directory. Legacy working-directory configuration has compatibility migration logic. Project .lxz indexes and memory serve separate purposes. The global directory is not ~/.lxz.
Kernel Connection
Loopback and port 3721 are defaults; the actual port may change. server.lan_pairing defaults off. Enabling it can add a LAN listener, taking effect through the current configuration after restart. Protect pairing codes and tokens; do not expose APIs through public port forwarding.
External Services
Install and configure LSP yourself; a missing-service banner indicates unavailable support. Python/Node/Java/Go debugging requires external debugpy, js-debug, jdt-java-debug and Delve (dlv) respectively, plus matching runtimes. Database configuration drives models; the actual account picker takes priority over static lists. MCP reload currently wires stdio.
Sandbox Defaults
Current sandbox defaults are enabled Docker, 60 seconds, image lxz-sandbox:latest, network none, 512 MB memory and 80% CPU. Fallback to Process is allowed, and the workspace mount is writable. Check actual backend and limits. Process command and URL/IP rules are not OS network isolation; see terminal.
Cache and Privacy
Cache structures or switches do not prove the completion HTTP path uses persistent caching; /api/fim/complete currently does not wire that lookup/writeback. Exclusion and redaction rules cannot guarantee no leaks across every path. Inspect context before sending; LLM requests transmit necessary code.
Kernel API · MCP · Completion