config
fialr config [action] [key] [value]View and manage the fialr configuration file. Supports reading values, setting values with comment preservation, and validating the configuration against the schema.
Actions
Section titled “Actions”| Action | Description |
|---|---|
show | Display active configuration (default) |
path | Show paths to config, database, sensitivity, schema, and jobs |
validate | Check configuration for errors |
schema | Show schema categories from schema.yaml |
sensitivity | Show sensitivity rule counts from sensitivity.yaml |
get <key> | Retrieve a value by dotted key (e.g. enrichment.provider) |
set <key> <value> | Set a value, preserving comments. Validates before writing. |
ai | Configure the AI enrichment provider and credentials |
Examples
Section titled “Examples”# Show active configurationfialr config
# Show all pathsfialr config path
# Validate configurationfialr config validate
# Get a specific valuefialr config get enrichment.provider
# Set a valuefialr config set enrichment.provider claude
# Show schema categoriesfialr config schema
# Show sensitivity rule countsfialr config sensitivity
# Run AI provider setup wizard (interactive)fialr config ai
# Set up Claude with API keyfialr config ai --provider claude --key sk-ant-...
# Switch to local Ollamafialr config ai --provider ollama
# Show current AI provider configurationfialr config ai --showAI provider configuration
Section titled “AI provider configuration”fialr config ai runs the AI enrichment provider setup wizard. This replaces the standalone fialr configure command.
Options
Section titled “Options”| Option | Description |
|---|---|
--show | Display current provider and API key status |
--provider NAME | Set provider: ollama (local) or claude (cloud) |
--key KEY | Set API key for cloud provider (must start with sk-ant-) |
When no flags are provided, runs in interactive mode.
API keys are stored in the system keychain via the keyring library, never in config files. See configure for full details on providers and key storage.
Configuration file
Section titled “Configuration file”The primary configuration file is config/fialr.toml. fialr resolves the config path using a multi-level fallback:
--configCLI flag (explicit path)./config/fialr.toml(current working directory)~/.config/fialr/fialr.toml(user config directory)- Bundled package default
- Argparse default (hardcoded fallback)
The same resolution applies to --db, --sensitivity-rules, and --schema paths.
Key sections:
| Section | Purpose |
|---|---|
[general] | Hash algorithm, secondary hash |
[inventory] | Buffer size, checkpoint interval |
[exclusions] | Directories and patterns to exclude |
[naming] | Naming pattern, separators, case, date format |
[enrichment] | Provider, model, endpoint, confidence threshold |
[embeddings] | Enabled, model, dimensions, similarity threshold |
[vault] | Backend, path, encryption settings |
[sensitivity] | Path to sensitivity rules file |
Set behavior
Section titled “Set behavior”fialr config set uses line-based editing to preserve comments and formatting. The edit is validated against the configuration schema before writing. An atomic write (temp file + rename) prevents corruption.
Required sections that must always be present: [general], [inventory], [exclusions].
See also
Section titled “See also”- Enrichment guide — provider selection and configuration walkthrough
- enrich — run enrichment with the configured provider
- process — full pipeline using current configuration