Skip to main content

Configuration reference

Desktop users should normally change settings in the AgentDock app. This page is mainly for headless Linux, Docker, automation, and advanced configuration.

Configuration surfaces​

EnvironmentRecommended place
macOS / WindowsAgentDock app and Advanced Settings
Linux serviceProtected service environment file
DockerCompose .env, environment, or secrets
Foreground processEnvironment variables and supported CLI flags

CLI flags override the matching environment variables they expose.

Default paths are:

~/.agentdock AgentDock state
~/AgentDock Default working directory

Core runtime​

SettingEnvironment variableCLI flagDefault
Listen addressAGENTDOCK_HOST--host127.0.0.1
PortAGENTDOCK_PORT--port8765
Log levelAGENTDOCK_LOG_LEVEL--log-levelinfo
Chat cardsAGENTDOCK_MCP_APPS_MODE--mcp-apps-modefull
stdio transportAGENTDOCK_STDIO--stdiofalse
State directoryAGENTDOCK_HOME—~/.agentdock
Working directoryAGENTDOCK_DEFAULT_DIR—~/AgentDock
Trusted proxy CIDRsAGENTDOCK_TRUSTED_PROXY_CIDRS—empty

Chat-card mode accepts full, compact, or off.

Authentication​

Bearer Token:

AGENTDOCK_AUTH_TOKEN=<random-secret>

OAuth settings:

VariablePurpose
AGENTDOCK_OAUTH_ENABLEDEnable OAuth
AGENTDOCK_SERVER_URLPublic HTTPS origin, without /mcp
AGENTDOCK_OAUTH_PASSWORDPassword used on the authorization page
AGENTDOCK_OAUTH_TOKEN_SECRETSigning secret for OAuth state and tokens
AGENTDOCK_OAUTH_ACCESS_TOKEN_TTLOptional access-token lifetime

A non-loopback listener must use Bearer Token or OAuth. Public access should use HTTPS; see Public access.

Browser​

VariableCLI flagPurpose
AGENTDOCK_BROWSER_ENABLED--browser-enabledEnable browser tools
AGENTDOCK_BROWSER_EXECUTABLE_PATH--browser-executable-pathUse a specific Chrome, Chromium, or Edge executable
AGENTDOCK_BROWSER_CDP_URL--browser-cdp-urlConnect to a configured CDP endpoint
AGENTDOCK_BROWSER_REUSE_EXISTING_CDP--browser-reuse-existing-cdpPrefer a reusable local CDP browser

See Use the browser for normal setup and usage.

Coding Agents​

VariablePurpose
AGENTDOCK_ACP_ENABLEDEnable Coding Agent tools
AGENTDOCK_ACP_PROFILES_JSONConfigure available Coding Agent profiles
AGENTDOCK_ACP_DEFAULT_PROFILEChoose the default profile
AGENTDOCK_ACP_MAX_CONCURRENT_PROMPTSLimit concurrent prompts
AGENTDOCK_ACP_INTERACTION_TIMEOUT_MSSet the interaction timeout

Desktop users should configure Coding Agents in the AgentDock UI. Headless deployments can use these variables. See Use local Coding Agents.

Other settings​

NexusDock pairing is stored as a paired device identity rather than a normal runtime environment variable. See Connect AgentDock.

Managed Skill and dynamic MCP credentials are configured through their own environment-management interfaces instead of global AgentDock variables.

Project rules use AGENTS.md; they are not runtime environment settings.