[Bug]: Source mode 'Cli' not supported for this provider

[biabbbb99]

Existing issues

• I searched existing issues and did not find a duplicate.

What happened?

Source mode 'Cli' not supported for this provider
I want to know how to make it work,thanks!

Affected area

• Tray panel
• Settings UI
• Config file / settings persistence
• CLI
• Provider-specific behavior
• Installer / release packaging
• Startup / background behavior
• Other

Steps to reproduce

can not get cursor,setting like this:

Logs, screenshots, or recordings

App version

0.43.0

Windows version

No response

Additional context

No response

[Finesssee]

Thanks for the report, I will try to fix this ASAP.

[Finesssee]

Status

Code bug in 0.43.0 for the default Cursor setup.

Root cause: with cookie source Manual (the default) and no stored cookie, the shell set SourceMode::Cli. Cursor does not support Cli, so you saw:

Source mode 'Cli' not supported for this provider

Fix: #213 remaps that case to Web and tries browser cookies (unless cookie source is explicitly Off).

What you can do today on 0.43.0 (before the next release)

You do not need to wait only—you can make 0.43.0 work with cookies:

1. Log into https://cursor.com in a browser (Chrome / Edge / Firefox).
2. CodexBar → Cursor provider settings:
   • Set cookie source to Auto or Browser, or
   • Manual: paste the Cookie header from DevTools on a cursor.com request while logged in.
3. Save and refresh.

If cookie source is Off, Cursor cannot fetch usage (by design). Turn it back to Auto/Manual.

After the next release / main build

Empty Manual + no pasted cookie should no longer hard-fail with “Cli not supported”; it will attempt browser cookies automatically. You still need a logged-in browser session or a valid manual cookie.

Build	Expectation
0.43.0 winget	Use Auto/Browser cookies or paste Manual cookie (workaround above)
Next release or main build	Default empty Manual no longer maps to unsupported Cli

Related fix PR: #213