The config command lets you inspect and modify your squirrel.toml configuration file without editing it manually.
Subcommands
show
Display the current configuration with the resolved file path:
Output:
Config file: /path/to/squirrel.toml
[project]
domains = []
[crawler]
max_pages = 50
...
set
Update a configuration value using dot notation:
squirrel config set crawler.max_pages 100
squirrel config set rules.disable '["ai/*"]'
Comments and formatting in your TOML file are not preserved when using config set. If you need to maintain comments, edit the file manually.
Options
| Option | Description |
|---|
--dry-run | Preview the change without writing to disk |
squirrel config set crawler.max_pages 100 --dry-run
Would set crawler.max_pages = 100
[project]
domains = []
[crawler]
max_pages = 100
...
path
Print the path to the active config file:
Output:
/Users/you/project/squirrel.toml
validate
Check that your config file is valid TOML and passes schema validation:
Output on success:
Config valid: /path/to/squirrel.toml
Invalid config: crawler.max_pages: Expected number, received string
Examples
Check current settings
Increase crawl limit
squirrel config set crawler.max_pages 200
Preview a change
squirrel config set crawler.concurrency 10 --dry-run
Disable AI rules
squirrel config set rules.disable '["ai/*", "content/quality"]'
Verify config before deploy
squirrel config validate && echo "Config OK"
Config File Resolution
squirrelscan searches for squirrel.toml starting from the current directory and walking up to your home directory. The first config file found is used.
If no config file exists, commands that require one will prompt you to run squirrel init.
See Also
