Configuration overview

Mogick keeps user-level and project-level configuration separate. Global configuration applies to every project for the current user, while project configuration applies only to the current workspace.

Configuration files

File	Global path	Project path	Purpose
config.json	<config-dir>/config.json	.mogick/config.json	LLM, permission, memory, session, and runtime settings
mcp.json	<config-dir>/mcp.json	.mogick/mcp.json	MCP server definitions
auth.json	<config-dir>/auth.json	.mogick/auth.json	OAuth tokens, API keys, and other credentials; never commit this file
sessions.sqlite	<db-path>	—	Persistent session data

Projects can also contain .mogick/skills/, which holds project Skills. Plan Artifacts are saved with the session in the session store.

Project settings generally override fields with the same name in the global configuration; fields omitted by the project continue to use global values. A non-empty project-level llm.providers[] replaces the entire global array, while auth.providers entries are merged by provider ID.

Find the right configuration page

Goal	Page
Connect a model service or configure OAuth or an API key	Authentication and models
Configure MCP servers	MCP server configuration
Change the session policy or per-tool permissions	Tool permission policies
Change session heartbeat, timeout, concurrency, or storage	Session and history settings

Common environment variables

Variable	Purpose
MOGICK_CONFIG_DIR	Override the default global configuration directory
MOGICK_DATA_DIR	Override the data directory
MOGICK_CONFIG_FILE	Select the main config.json; does not change auth, MCP, Skills, or data paths
MOGICK_RUNTIME_ENV	Select runtime preset
MOGICK_TUI_THEME	Set auto, dark or light

export MOGICK_CONFIG_DIR=/home/user/.mogick
export MOGICK_DATA_DIR=/mnt/mogick-data
mogick

See Data directories and environment variables for the complete list.

Path placeholders <config-dir> and <db-path> refer to the effective profile/channel paths; see Data directories.