Support Comet browser cookie import, or explicitly document unsupported Chromium profiles

[h3x89]

Summary

CodexBar’s automatic cookie import does not find sessions when the user only signs in using Comet (Perplexity’s Chromium-based browser). Cookies live under a separate profile path (e.g. ~/Library/Application Support/Comet/Default/Cookies) and are not read by the current import logic.

Current behavior

• Providers that rely on browser cookies may show “no session” / import failures.
• docs/DEVELOPMENT.md lists supported browsers (Chrome, Arc, Safari, Firefox, Brave, Edge) but does not clearly state that other Chromium browsers (Comet, etc.) are unsupported.

Expected behavior

Either:

1. Feature: Comet (or a configurable “extra Chromium profile path”) is included in cookie discovery, or
2. Documentation: README + docs/configuration.md explicitly list unsupported browsers and point users to Manual cookieHeader configuration.

Motivation

Users who only use Comet for provider sites have no automatic path unless they switch browser or use manual configuration.

Possible implementation notes (if pursuing code)

• Comet uses Chromium-style cookie storage under Application Support (similar to Chrome).
• A generic “custom Chromium user data directory” in advanced settings could cover Comet and other forks without one-off hacks per app.

Acceptance criteria

• Official docs state whether Comet (and similar) are supported for automatic import.
• If not supported: documented workaround (Manual cookies / ~/.codexbar/config.json) without requiring users to post secrets in issues (see Security).

Security (for reporters)

• Do not paste real Cookie headers, Netscape exports, or cookieHeader values into GitHub issues, screenshots, or logs — they are session credentials. Use redacted examples only (e.g. session=<REDACTED>).

Environment

• macOS 14+
• CodexBar (current release)
• Any web-cookie-based provider where the user is logged in only via Comet