Crash on launch when Cursor provider is enabled in 0.20 (55)

[anirudhvee]

Description

After updating CodexBar to 0.20 (55), the app launches and then exits within a few seconds if the cursor provider is enabled.

Disabling the cursor provider makes CodexBar launch and stay running again.

Environment

• CodexBar version: 0.20
• Build: 55
• macOS version: 26.4 (25E246)
• Hardware: Apple Silicon (MacBookPro17,1)

Steps to Reproduce

1. Enable the cursor provider in CodexBar Settings or in ~/.codexbar/config.json
2. Launch CodexBar, or reload the Cursor provider if CodexBar is already open
3. Wait a few seconds

Actual Behavior

• CodexBar exits/crashes within a few seconds
• A crash report is generated

Expected Behavior

CodexBar should remain running with the Cursor provider enabled.

Reproducibility

This is reproducible on my machine.

I verified:

• cursor enabled -> CodexBar exits and writes a fresh crash report
• cursor disabled -> CodexBar launches and stays running
• enabling cursor from the CodexBar UI also reproduces the crash

Workaround

Setting the Cursor provider to disabled in ~/.codexbar/config.json avoids the crash:

{
  "enabled": false,
  "id": "cursor"
}

Crash Evidence

Crash report:

• CodexBar-2026-04-08-004223.zip

Short excerpt:

app_version: 0.20
build_version: 55
os_version: macOS 26.4 (25E246)
exception: EXC_CRASH / SIGABRT
CursorStatusProbe.fetch(cookieHeaderOverride:logger:)
CursorStatusFetchStrategy.fetch(_:)
ProviderFetchPipeline.fetch(context:provider:)

[piero]

I can reproduce this issue.

App Version: 0.20
MacOS Version: Sequoia 15.7.4 (24G517)
Hardware: Apple M4 Pro

[SKYhuangjing]

I can reproduce this issue.

App Version: 0.20
MacOS Version: 26.5 Beta (25F5042g)
Hardware: Apple M1 Pro

[anirudhvee]

I’ve been digging into this locally and may have a fix. I’ll test it a bit more and open a PR if it checks out.

[ratulsarna]

I’ve been digging into this locally and may have a fix. I’ll test it a bit more and open a PR if it checks out.

Hey @anirudhvee , I've also been looking at the issue since you raised and created a PR for same. Can you check if the issue gets resolved on the PR's branch: #663

[anirudhvee]

Hey @anirudhvee , I've also been looking at the issue since you raised and created a PR for same. Can you check if the issue gets resolved on the PR's branch: #663

Hey @ratulsarna, yes, I had already pushed #664 by the time I saw #663. I’ll test your branch now and report back here.

[anirudhvee]

Tested #663 locally and it fixes the crash for me too, so I’m closing #664 to keep the fix in one place.