fishnet policy

​

Synopsis

fishnet policy edit

​

Subcommands

​

edit

fishnet policy edit

​

Examples

​

Edit with default editor

fishnet policy edit

Policy file updated: ~/.config/fishnet/fishnet.toml

​

Edit with specific editor

EDITOR=nano fishnet policy edit

EDITOR=code fishnet policy edit  # VS Code

EDITOR=emacs fishnet policy edit

​

Edit custom config location

fishnet --config /path/to/custom.toml policy edit

​

Behavior

• Locates the configuration file (default or custom path)
• Creates a default configuration file if it doesn’t exist
• Opens the file in $EDITOR (falls back to vi if not set)
• Waits for the editor to exit
• The server watches for file changes and reloads automatically

​

Configuration file structure

[llm]
daily_budget_usd = 10.0
rate_limit_per_minute = 60

[llm.prompt_drift]
enabled = true
reset_baseline_on_restart = false
hash_chars = 512
ignore_whitespace = true
hash_algorithm = "blake3"

[alerts]
retention_days = 90

[http]
connect_timeout_ms = 5000
request_timeout_ms = 120000
pool_idle_timeout_secs = 90
pool_max_idle_per_host = 32

​

Error messages

failed to launch editor: <error>

editor exited with status: exit status 1

could not determine config path

​

Exit codes

• 0 - Configuration file edited successfully
• 1 - Error occurred (editor failed, config path not found, etc.)

​

Tips

• Changes take effect immediately if Fishnet is running (config file is watched)
• Invalid configuration will be rejected on reload with an error message
• Use fishnet doctor to verify configuration changes
• Comment lines start with #
• Restart Fishnet if configuration changes are not applied

​

Environment variables

• EDITOR - Text editor to use (default: vi)
• VISUAL - Alternative editor variable (EDITOR takes precedence)

​

Related commands

• fishnet init - Initialize configuration during first-time setup
• fishnet doctor - Validate configuration
• fishnet start - Start server with configuration