Wondering if CodexBar scans your disk? It doesn’t crawl your filesystem; it reads a small set of known locations (browser cookies/local storage, provider config files, local JSONL logs) when the related features are enabled. Plain Adaptive refresh never inspects local agent activity. The separate Adaptive (agent-aware) option asks before inspecting the running-process list (including command lines) to identify Codex/Claude and reading bounded known-session metadata. Declining returns to plain Adaptive.

Chromium cookie import needs the browser’s Safe Storage item, and an explicitly enabled Claude OAuth repair may read Claude Code’s own Keychain item. Background CodexBar paths fail or skip instead of requesting authorization; a user-initiated import or repair can still show the macOS prompt. Settings → Advanced → Disable Keychain access blocks CodexBar-owned Keychain operations and browser decryption, but cannot constrain provider-owned CLIs that CodexBar launches. Manual cookie headers, API keys, and file-backed sources remain alternatives where supported. See Keychain prompts for Allow Once vs.