Troubleshooting
Configuration file not found
Section titled “Configuration file not found”Run validation from the repository root and pass --config with the path to the
file. Check that the file exists and that you have permission to read it.
cargo run -p litegate-cli -- config validate --config tests/fixtures/config/valid-phase1.tomlThe validator rejects the file
Section titled “The validator rejects the file”Check the field named in the error and compare it with the repository example. Configuration is strict: check the schema version, field names and that each model refers to a declared provider.
The daemon exits immediately
Section titled “The daemon exits immediately”This is the initial implementation’s behavior: it loads configuration and prepares state, but it does not yet keep an HTTP server listening.
status says the API is not implemented
Section titled “status says the API is not implemented”The command is provisional. It is not a real connectivity check and does not mean your machine is configured incorrectly.
Report an issue
Section titled “Report an issue”Open an issue with your operating system, commit, command and observed error. Remove keys, tokens, prompts and other private data before sharing output or files. For vulnerabilities, see the security policy.