Skip to main content
Use these commands to bootstrap setup, validate resolved runtime config, and safely edit configuration. For the full settings reference see Configuration Reference.

​
Quick command map

notewise setup
notewise config
notewise process "https://youtube.com/watch?v=VIDEO_ID"

​
notewise setup

Run the interactive setup wizard. Prompts for your LLM provider and API key, then writes ~/.notewise/config.env. 
notewise setup
notewise setup --force    # re-run even when config already exists
notewise setup --show     # display current config and exit
OptionDescription
--force / -fRe-run wizard even when config already exists
--showDisplay current config and exit

​
notewise config

Show the fully resolved runtime configuration. API keys are masked. 
notewise config

​
notewise config-path

Print the config file path and whether it exists. 
notewise config-path

​
notewise edit-config

Open config.env in your $EDITOR. On Windows, Notepad is used when EDITOR is not set. 
notewise edit-config

​
Key files

FilePurpose
~/.notewise/config.envPrimary config file
~/.notewise/.notewise_cache.dbSQLite cache
~/.notewise/logs/Session log files
Override the state directory: 
export NOTEWISE_HOME=/custom/path

​
Common setup issues

Re-run with force:
notewise setup --force

notewise config-path
If NOTEWISE_HOME is set, notewise resolves config from that directory.
Confirm model/key pairing in resolved config:
notewise config
Verify DEFAULT_MODEL and the matching provider API key are both present.