Modes

Modes control how aggressively AlphaBase can act during a task.

AlphaBase currently centers behavior on agent configuration. Legacy mode configuration is still recognized for compatibility but is deprecated.

Caution

Prefer configuring agent in alphabase.json for all new setups.

Built-In Behavior

Build

• implementation-first behavior
• tools enabled for editing and execution
• best for normal development work

Plan

• analysis-first behavior
• write/edit/patch/shell capabilities are restricted by default
• best for architecture review, risk analysis, and planning

Switch During Session

Use your mode/agent switch shortcut in the UI (for example Tab where supported) to move between build-style and plan-style workflows.

Recommended Configuration (Agent-First)

alphabase.jsonc

{
  "$schema": "https://alphabase.extremeharness.com/config.json",
  "agent": {
    "build": {
      "model": "<provider>/<model-id>",
      "temperature": 0.2
    },
    "plan": {
      "model": "<provider>/<model-id>",
      "tools": {
        "write": false,
        "edit": false,
        "patch": false,
        "bash": false
      }
    }
  },
  "default_agent": "build"
}

Legacy Mode Configuration (Deprecated)

If you still use mode, AlphaBase migrates behavior for compatibility. Use this only while transitioning older projects.

alphabase.jsonc

{
  "$schema": "https://alphabase.extremeharness.com/config.json",
  "mode": {
    "plan": {
      "tools": {
        "write": false,
        "edit": false,
        "bash": false
      }
    }
  }
}

Suggested Migration Path

1. Move any mode.<name>.prompt logic to agent.<name>.prompt.
2. Move model overrides to agent.<name>.model.
3. Move tool restrictions into agent.<name>.tools or permission settings.
4. Set default_agent explicitly.
5. Remove mode once your team verifies parity.

See Agents, Permissions, and Config.