/config commands. These persist across restarts in config.json and take effect immediately. No bot restart is required.
Using /config Commands
All
/config commands are restricted to the Bot Owner.All Configurable Keys
Values are automatically type-converted based on the default type for each key (int, float, bool, or string). Invalid values are rejected with an error message.Notes on Specific Keys
generation_rate_limit— Increase this on free-tier AI provider plans to avoid rate limit errors. The default of5works well for most paid tiers. Example:/config set generation_rate_limit 3.0.ytdlp_compress_target_mb— Keep this below Discord’s upload limit (10 MB for free servers). Reduce it if you are seeing file-too-large errors after compression. Example:/config set ytdlp_compress_target_mb 8.0.mvsep_poll_timeout— Increase this for very long audio files if the bot times out before MVSEP finishes the separation job. Example:/config set mvsep_poll_timeout 600.generation_split_min_length— If the AI produces very long responses and you want them split into smaller chunks earlier, reduce this value. Example:/config set generation_split_min_length 1500.model_temperature— Controls randomness in AI generation. Lower values (0.1–0.3) make output more deterministic; higher values (0.8–1.5) increase creativity. Default is0.7. Example:/config set model_temperature 0.9.
config.json Managed Fields
Beyond the/config keys above, config.json also stores bot state that other commands manage. You do not edit these directly — use the Discord commands listed below.
config.json is loaded fresh on every command call to avoid stale state across module reloads. Do not edit it manually while the bot is running. Use the Discord commands above so changes are validated and applied cleanly.