> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turen.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Data locations

> Find configuration, sessions, logs, caches, and Desktop state

TurenOS retains `forge` directory names for compatibility. Exact roots follow operating-system and XDG conventions and can be overridden for managed deployments.

## Common locations

| Data                            | Typical location                                    |
| ------------------------------- | --------------------------------------------------- |
| User configuration              | `~/.config/forge/forge.jsonc`                       |
| CLI/server data                 | `~/.local/share/forge`                              |
| CLI/server state and logs       | `~/.local/state/forge`                              |
| Project instructions and config | `.forge/` and project `forge.json(c)`               |
| macOS Desktop profile           | `~/Library/Application Support/com.turenlabs.forge` |

Windows and Linux resolve equivalent configuration, data, cache, and state roots through their native platform conventions.

## Databases

SQLite databases contain durable sessions, projects, tools, Extensions, automations, memory, and related state. WAL and SHM files belong to the active database and must be backed up consistently.

## Credentials

Credential rows are encrypted and tied to an OS-protected key. Copying only the database to another account or machine can produce a vault ownership error. Reconnect providers through supported flows after migration.

## Overrides

Use `FORGE_CONFIG_DIR`, `FORGE_CONFIG`, XDG environment variables, or an explicitly configured database path only when you understand the isolation boundary. Test profiles should never reuse production credentials accidentally.