axon.toml — a TOML file that controls everything from the API port and authentication requirements to how aggressively the daemon scans for new processes. You can also override any setting with an AXON_* environment variable without touching the file, which is especially useful in CI pipelines and containerized environments.
Config File Locations
The daemon looks foraxon.toml in three locations and layers them in priority order — later sources override earlier ones, and environment variables always win:
The GUI installer and
axon-daemon.exe init both create the system-wide config at C:\ProgramData\Nelieo\axon.toml. This is the file to edit for most deployments.Full Configuration Reference
Below is a completeaxon.toml with every available option documented. All values shown are the defaults — you only need to include the keys you want to change.
Environment Variable Reference
Everyaxon.toml key has a corresponding environment variable. Variables follow the format AXON_<SECTION>__<KEY> with a double underscore (__) between the section and key names. Environment variables always override the config file.
Example Configurations
CI / Testing Environment
In CI, you typically want no authentication, a fresh schema registry on every run, and verbose readable logs. Set these with environment variables so your config file stays unchanged:Minimal Development Config
For local development with a single agent, use this minimalaxon.toml to get fast refresh cycles and skip authentication overhead:
