Configuration
There's no external config file — AgentDock's configuration lives entirely in its Settings UI and local database.
AgentDock does not read a project-level or machine-level configuration file. There's no .agentdockrc, no YAML or JSON config, and no way to configure AgentDock outside of its own Settings UI.
All configuration state — settings, sessions, workspaces, and message history — is stored locally in a SQLite database (via sql.js) inside Electron's per-user userData directory. There is no remote backend, and nothing to sync or check into version control.
Settings shape
The closest thing to a configuration reference is the Settings object AgentDock persists:
ts
appearance: 'system' | 'light' | 'dark'
agents: Record<AgentId, { customPath, permissionMode, model, reasoningEffort }>
permissions: { confirmDestructiveGitActions: boolean }
advanced: { gitExecutablePath: string } // defaults to 'git'
cliSetup: { setupDismissed: boolean }AgentDock Pro adds:
ts
defaultAigencyRunView?: 'simple' | 'advanced'
defaultAigencyPermissionMode?: 'ask' | 'allow-approved' | 'bypass'
aigencyRoutingCalibration?: /* preset-based routing dial */Each field is documented on its corresponding Settings page:
- Agents
- Models & reasoning effort
- Appearance
- Permissions
- Advanced & diagnostics
- AIgency settings (Pro)