Configuration options

Where configuration lives in V1

Most user-facing configuration is done via the Settings UI in the Web app (LLM provider/model, integrations, MCP, secrets, etc.).

For self-hosted deployments and advanced workflows, Faheem Code also supports environment-variable configuration.

These are some commonly used variables in V1 deployments:

LLM credentials
- LLM_API_KEY
- LLM_MODEL
Persistence
- FC_PERSISTENCE_DIR: where Faheem Code stores local state (defaults to ~/.faheem-code).
Public URL (optional)
- FC_WEB_URL: the externally reachable URL of your Faheem Code instance (used for callbacks in some deployments).
Sandbox workspace mounting
- SANDBOX_VOLUMES: mount host directories into the sandbox (see Docker Sandbox).
Sandbox image selection
- AGENT_SERVER_IMAGE_REPOSITORY
- AGENT_SERVER_IMAGE_TAG
Sandbox networking (self-hosting behind a reverse proxy)
- SANDBOX_CONTAINER_URL_PATTERN / FC_SANDBOX_CONTAINER_URL_PATTERN: the URL pattern used to reach exposed sandbox ports, with {port} as a placeholder (default http://localhost:{port}). Set this to your public hostname, e.g. https://my-domain:{port}, when self-hosting behind a reverse proxy. See Docker Sandbox: Self-hosting behind a reverse proxy.
- AGENT_SERVER_USE_HOST_NETWORK: when true (also 1/yes), run agent-server containers in Docker host-network mode so each container's ports are reachable directly on fixed host ports instead of randomly assigned ones. See Docker Sandbox: Self-hosting behind a reverse proxy.

Some deployments still use the legacy RUNTIME environment variable to choose which sandbox provider to use:

If you are looking for the old config.toml reference or V0 “runtime” providers, see: