Where Does Qwen Code Store Settings and Sessions?
Qwen Code keeps user settings in a .qwen folder at home and per-project settings in a .qwen folder at the repo root.
Last updated
Qwen Code config is JSON in predictable places. User settings live at ~/.qwen/settings.json (%USERPROFILE%\.qwen\settings.json on Windows) and apply to every session. Project settings sit at .qwen/settings.json in the repo root and override the user file. System admins get a third layer in a platform settings path.
Sessions and plans accumulate nearby. Chat transcripts land under the global .qwen directory keyed by project, and plans default there too unless the project sets its own plans directory. Copying the home .qwen folder to a new machine carries keys, providers, and history in one move.
Where Qwen Code stores this, by platform
~/.qwen
settings.json, plans, OAuth tokens, and per-project chat transcripts. Project overrides live in .qwen/settings.json at each repo root. QWEN_HOME and QWEN_RUNTIME_DIR relocate it.
~/.qwen
Same layout as macOS. System-wide defaults go in /etc/qwen-code/settings.json.
%USERPROFILE%\.qwen
Same layout under your home folder. System-wide defaults go in C:\ProgramData\qwen-code\settings.json.
Frequently asked questions
Where are my Qwen Code chat sessions stored?
Under the global .qwen folder in per-project chat directories. Open the folder for the project and pick the session file. Deleting one forgets that conversation only.
How do I pin settings for every user on a machine?
Use the system settings file: /etc/qwen-code/settings.json on Linux, /Library/Application Support/QwenCode/settings.json on macOS, C:\ProgramData\qwen-code\settings.json on Windows. It overrides user and project files.
Notice an outdated path? Let us know.