NeuroBrix has no user configuration file. Behaviour comes from the settings bundled with the engine, from the flags of each command (CLI Reference), and from the few variables below.
| Variable | Effect |
|---|---|
NEUROBRIX_REGISTRY |
Registry used by hub and import. Default https://neurobrix.org (0.6.x: https://neurobrix.es, still served). The --registry flag overrides it per command |
NBX_ACCEPT_LICENSE=1 |
Accept gated licences without a prompt (for scripts and CI). Same as --accept-license |
NBX_DEBUG |
More verbose diagnostics |
CUDA_VISIBLE_DEVICES |
Restrict the GPUs NeuroBrix sees. Set it empty to force CPU |
OMP_NUM_THREADS, MKL_NUM_THREADS |
CPU thread counts. If unset, NeuroBrix sets both to the number of CPU cores |
Other NBX_* and NEUROBRIX_* variables are internal diagnostics and are not part of the public interface.
CUDA_VISIBLE_DEVICES=0,1 neurobrix serve --model <name>
~/.neurobrix/
├── store/ # downloaded .nbx archives (and .part files while downloading)
├── cache/<name>/ # extracted models; the runtime reads from here
├── license_acceptances.json # licences you accepted in the terminal
└── daemon.sock, .pid, .log # the serving daemon (see "neurobrix serve")
The location is fixed under your home directory. A way to relocate it is not documented yet. Free space with neurobrix clean or neurobrix remove.
Defaults of a model (steps, guidance, temperature) can be changed for one run:
neurobrix run --model <name> --prompt "test" --set KEY=VALUE
Which keys exist depends on the model; the common ones have their own flag (--steps, --cfg, --seed, --temperature, ...).
| Flag | Meaning |
|---|---|
--compiled (default) |
The standard engine |
--sequential |
Step-by-step execution, slower, for diagnosing problems |
--triton, --triton-sequential |
Triton kernels. Triton is optional and not installed with NeuroBrix; neurobrix doctor tells you if it is missing |
--hardware <profile> |
Pick a bundled hardware profile instead of auto-detection |
Run neurobrix info --hardware for what was detected. Details: Install by hardware.
Next: Troubleshooting