Skip to content

Configuration

OAK project settings are stored in .oak/config.yaml:

version: 0.1.0
agents:
- claude
- copilot
rfc:
directory: oak/rfc
template: engineering
auto_number: true
number_format: sequential
validate_on_create: true

The CI daemon stores its configuration in .oak/ci/config.yaml. You don’t need to edit this file directly — the dashboard reads and writes it for you.

Settings managed via the dashboard:

  • Embedding provider and model (Ollama, LM Studio, OpenAI-compatible)
  • Summarization provider and model (optional)
  • Session quality thresholds (minimum activities, stale timeout)
  • Log rotation (max file size, backup count)
  • Directory exclusions (patterns to skip during indexing)

See the Dashboard page for details on each setting.

Available RFC templates (specified via --template on oak rfc create):

TemplateDescription
engineeringEngineering RFC Template (default)
architectureArchitecture Decision Record
featureFeature Proposal
processProcess Improvement

During initialization, OAK installs agent-specific settings that enable auto-approval for the configured OAK CLI command (oak by default):

AgentSettings File
Claude.claude/settings.json
VS Code Copilot.vscode/settings.json
Cursor.cursor/settings.json
Gemini.gemini/settings.json
Windsurf.windsurf/settings.json

Run oak upgrade to update agent settings to the latest version.

If you need a different command in one repository (for example oak-dev), set:

Terminal window
oak ci config --cli-command oak-dev

This updates managed integrations in that project to use the new command. See Codebase Intelligence Configuration for details.

OAK creates and manages instruction files that reference your project constitution:

AgentInstruction File
Claude Code.claude/CLAUDE.md
VS Code Copilot.github/copilot-instructions.md
Codex / Cursor / OpenCodeAGENTS.md (root level, shared)
GeminiGEMINI.md (root level)
Windsurf.windsurf/rules/rules.md

If your team already has these files, OAK will append constitution references (not overwrite). Backups are created automatically.

The daemon exposes tools for agents via the Model Context Protocol:

ToolDescription
oak_searchSemantic search over code, memories, and plans
oak_rememberStore observations for future sessions
oak_contextGet relevant context for the current task
oak_resolve_memoryMark observations as resolved or superseded

See the MCP Tools Reference for full parameter documentation.