Ollama login detection fails because CodexBar does not recognize current `__Secure-session` cookie

[hckal]

SUMMARY

CodexBar reports:

No Ollama session cookie found. Please log in to ollama.com in your browser.

But Safari is already signed into ollama.com.

This appears to be caused by CodexBar’s Ollama cookie detector recognizing older cookie names only, while the current Ollama web session is stored under __Secure-session.

Observed behavior

CodexBar fails to detect an existing Ollama web session and keeps prompting the user to log in.

Expected behavior

If the browser has a valid signed-in ollama.com session, CodexBar should detect it and use it.

Evidence

From the installed CodexBar.app binary, the Ollama detector appears to recognize these cookie names:

• __Secure-next-auth.session-token
• next-auth.session-token
• __Host-ollama_session

From Safari’s local cookie store for ollama.com, the active session cookie present is:
__Secure-session.

Environment

• CodexBar: 0.19.0
• Browser: Safari
• macOS
• Full Disk Access / restart / re-login were already attempted

Thank you!

[anirudhvee]

Hey @hckal, #707 adds support for Ollama’s __Secure-session cookie. Could you test a build from the PR and let me know if it fixes it for you?

[ImBada]

Hi @anirudhvee, I had the same issue and just tested your branch, but it didn't work. I tried logging in on both Chrome and Safari, and neither worked.