config.toml inside its platform-specific local state directory.
Managed state
Coral writes source installation state toconfig.toml when you run commands such as coral source add and coral source remove.
This state includes installed-source metadata and non-secret source variables. Source secrets are stored separately within the same local trust boundary.
Prefer the
coral source commands for source state instead of editing workspace entries manually.Workspaces
Workspace metadata is stored under[workspaces]. The default workspace
exists automatically, and additional workspaces can be managed with
coral workspace.
[workspaces.<name>] table.
Installed sources for that workspace live under
[workspaces.<name>.sources.<source>].
There is no separate active-workspace key in config.toml; use
CORAL_WORKSPACE for a shell default or --workspace <NAME> for one command.
Source specs imported from files and source credential material remain scoped
to the source installation in a workspace. Reusable global source specs and
reusable credential references are not config objects today.
Runtime features
Experimental runtime features are configured under[features].
config.toml but ignored by Coral.
OpenTelemetry
External OpenTelemetry export is configured under[otel].
[trace_history].