Reference
For the complete documentation index optimized for AI agents, see llms.txt.This page documents the configuration files the Helix CLI reads and writes:
helix.toml— per-project configuration in your project root.~/.helix/config— user-global state, currently the selected workspace.~/.helix/credentials— Helix Cloud credentials written byhelix auth login.
helix.toml
helix init creates helix.toml in your project root. Everything the CLI knows about your project lives here.
[local.*] or [enterprise.*] instance is required. The CLI rejects an empty helix.toml.
[project]
[local.<instance>]
One block per local instance. The instance name is the table key (e.g. [local.dev]).
You can define as many local instances as you want, each on a different port:
helix start <instance> --disk as a one-off disk-mode run without changing helix.toml.
[enterprise.<instance>]
One block per Helix Cloud instance. Most fields here are populated automatically by helix sync.
If
gateway_url is missing, helix query <instance> fails with:
~/.helix/config
User-global configuration written by helix workspace switch.
~/.helix/credentials
Written by helix auth login. Plain key=value format:
helix auth logout. Never commit this file.
Environment variables
Troubleshooting
- Port conflict on
helix start— change the port in[local.<instance>] port, or passhelix start <instance> --port <port>to override for a single run. Missing instances—helix.tomlhas no[local.*]or[enterprise.*]blocks. Add one withhelix add.Authentication required— runhelix auth loginfor Helix Cloud commands.gateway_url is still missingafterhelix sync— the cloud-side configuration has not been published yet. Re-runhelix synclater, or setgateway_urlmanually under[enterprise.<instance>].
Next Steps
Local workflow
The local init/run/query loop
Troubleshooting
Solve common CLI issues