> ## 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.

# Configuration

> Configure providers, agents, tools, permissions, servers, and experiments

TurenOS retains `forge` configuration names for compatibility.

## Configuration files

The global configuration directory defaults to `~/.config/forge`. Use `forge.json` or `forge.jsonc` for user configuration. A project can also provide repository-scoped configuration.

Common sections include:

* Providers, model settings, and custom endpoints
* Agents and model defaults
* Tool and permission rules
* MCP servers and Extensions
* Server hostname, port, CORS, and discovery
* Experimental overrides

## Precedence

Explicit command-line and session selections override configured defaults. Project configuration augments or overrides user configuration where allowed. Environment-provided configuration is intended for managed or ephemeral execution.

Useful environment controls include:

```text theme={null}
FORGE_CONFIG
FORGE_CONFIG_DIR
FORGE_CONFIG_CONTENT
FORGE_DISABLE_PROJECT_CONFIG
FORGE_SERVER_USERNAME
FORGE_SERVER_PASSWORD
FORGE_EXPERIMENTAL
```

Product capabilities default on. Set `FORGE_EXPERIMENTAL=false` only as a broad rollback; prefer a capability-specific override when available.

<Warning>
  Do not put literal provider keys or OAuth tokens in checked-in configuration. Use Provider Settings, declared Extension secrets, environment injection, or the Secret Vault.
</Warning>