panevibe
GitHub

Configuration

Everything has a working default; environment variables are escape hatches rather than a required setup surface.

View Markdown

Core variables

  • PANEVIBE_IDE_CLI overrides the binary launched by a default chat pane.
  • PANEVIBE_IDE_HOME_OVERRIDE moves worktrees and harness state.
  • PANEVIBE_IDE_POLICY_DIR points to custom tool-permission policies.
  • PANEVIBE_MCP_CONFIG merges additional MCP servers into every pane.
  • PANEVIBE_NO_MEM_GUARD disables the low-memory load shedder.
  • PANEVIBE_NO_FREEZE_WATCHDOG disables compositor self-healing.

Browser variables

  • PANEVIBE_PW_EXECUTABLE selects a Chromium binary.
  • PANEVIBE_PW_HEADLESS enables headless mode.
  • PANEVIBE_PW_USER_DATA_DIR selects the persistent profile directory.
  • PANEVIBE_PW_MAX_PAGES, PANEVIBE_PW_RENDERER_LIMIT, and PANEVIBE_PW_JS_MAX_MB tune safety bounds.
  • PANEVIBE_PW_2CAPTCHA_KEY is empty by default; no CAPTCHA key ships with the source.

Where state lives

Application data follows the native platform location. Worktrees and engineering-harness state live under ~/.panevibe unless PANEVIBE_IDE_HOME_OVERRIDE changes the root. Transient MCP configuration is written under the operating system temp directory.