Files and privacy
Where SoreQen keeps things on your computer, what leaves it, and how to start completely fresh.
On your computer
Everything SoreQen Code keeps is in one folder in your home directory: ~/.soreqen on a Mac or Linux, %USERPROFILE%\.soreqen on Windows.
| Path | What it holds |
|---|---|
.env | Your own API keys. |
mcp.json | Your MCP servers. |
mcp-trust.json | The project MCP configurations you allowed. |
skills/ | Your own skills. |
sessions/ | Each folder's saved session. |
projects/<project>/memory/ | What SoreQen remembers about each project. |
audit/ | The audit trail of what it did. /audit says which file. |
In your project
SoreQen reads these if a project has them:
| Path | What it is |
|---|---|
.soreqenrules, SOREQEN.md, .soreqen/rules.md or .cursorrules | The project rulebook. |
.soreqen/skills/ | The project's own skills. |
.mcp.json | The project's MCP servers, which run only once you allow them. |
What leaves your computer
What you send in a session, and the parts of your project SoreQen reads to answer it, go to the model that does the work: your provider, when you use your own key, or SoreQen's service and the provider serving the model, when you use the hosted models. When SoreQen researches or uses its browser, it visits the pages it needs, as any browser does.
Your keys stay in ~/.soreqen/.env and are used only for requests to their provider. Memory never holds passwords or keys. A /feedback report stays on your computer until you send it, and it has keys and tokens removed and none of your code.
Starting fresh
Close SoreQen, then delete the .soreqen folder. That removes your keys, sessions, memory, skills and MCP servers from this computer. It does not touch your projects or your SoreQen account.