DeepSeek TUI config file location problems usually look like broken settings, not missing files

Users often edit the wrong file, expect settings to load from a different directory, or assume environment changes automatically override every stored config path.

Why this becomes a real search

People search for config file location after they already tried the obvious fixes. At that point the issue is often not what to put in the config, but where DeepSeek TUI is actually reading from.

What to verify first

Are you editing the file used by the current install route?
Did you copy an example path from another platform or shell?
Are environment variables overriding what you expect from file-based config?