NoteWise stores its configuration in ~/.notewise/config.env. The commands on this page let you create, view, and edit that file without leaving your terminal.
Override the default state directory by setting the NOTEWISE_HOME environment variable:export NOTEWISE_HOME=/path/to/custom/dir
All persistent state — config, cache, and logs — will be read from and written to that directory instead.
notewise setup
Runs an interactive wizard that prompts you for API keys and preferences, then writes them to ~/.notewise/config.env. This is the recommended way to configure notewise for the first time.
Enter your API key
The wizard asks which LLM provider you want to use and prompts for the corresponding API key. The default model is Gemini 2.5 Flash — get a free key at aistudio.google.com. Confirm your settings
The wizard summarizes what it will write. Press Enter to confirm and save the config file.
Options
Force the wizard to run even if a config file already exists. Use this when you want to reconfigure a key or switch providers.Default: falseAliases: -f
Display the current configuration (with secrets masked) without launching the wizard or modifying the config file. Equivalent to running notewise config.Default: false
Examples
# First-time setup
notewise setup
# Reconfigure (overwrite existing config)
notewise setup --force
# View current config without rewriting
notewise setup --show
notewise config
Displays the current resolved configuration with all API keys and secrets masked. The output reflects the merged result of your config file and any environment variable overrides — environment variables always take precedence.
This command is read-only and never modifies your config file.
Use notewise config to verify that environment variable overrides are being picked up correctly before running a long batch job.
notewise config-path
Prints the absolute path to the active config file. If no config file exists yet, the command tells you how to create one.
notewise config-path
# Configuration file: /home/you/.notewise/config.env
notewise edit-config
Opens the config file in your OS default editor (or the editor set in $EDITOR/$VISUAL). If the file does not exist, run notewise setup first to create it.
notewise only reads recognized keys from the config file. Unknown keys are silently ignored. See the configuration schema reference for the full list of supported keys.
The config file is a plain KEY=VALUE env file. Lines beginning with # are comments and are ignored.
# LLM provider
GEMINI_API_KEY=your_key_here
DEFAULT_MODEL=gemini/gemini-2.5-flash
# Output
OUTPUT_DIR=./output
# Generation
TEMPERATURE=0.7
# MAX_TOKENS=
# Concurrency
MAX_CONCURRENT_VIDEOS=5
YOUTUBE_REQUESTS_PER_MINUTE=10
# Private videos
# YOUTUBE_COOKIE_FILE=/path/to/cookies.txt
Environment variables always take precedence over values in the config file. This makes it easy to override settings in CI or Docker without modifying the file:
GEMINI_API_KEY=ci_key DEFAULT_MODEL=gpt-4o notewise process "URL" --no-ui