Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

User plugins: allow Aside cookie import for a custom Qiniu quota plugin

Open
  • Is something wrong?
#4,792 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
swift
Domain
authentication, desktop

Research direction

Start by reading BrowserCookieImportSupport.importOrder(for:), then trace how UserProviderPluginCookieBroker applies the user-plugin browser policy and review the plugin documentation that describes Chrome-only imports. Check the existing Aside importer and tests for browser selection and declared-domain approval. Done means a custom Qiniu plugin can use the current Aside session while preserving manual Cookie fallback and the stated safeguards against background Keychain prompts.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:auth-provider impact:ux-friction issue-rating: 🦞 diamond lobster P2

Request

Please let user-installed provider plugins import cookies from supported browsers such as Aside, rather than restricting them to Chrome. An explicit browser/profile selection would also work.

My use case is a custom Qiniu Cloud Conatus quota plugin. I use Aside for the Qiniu console and want to keep standard CodexBar/Homebrew updates, without maintaining a locally rebuilt app.

Current behavior

  • The plugin originally used a manually pasted Qiniu console Cookie.
  • When that session became invalid, the official read-only quota endpoint returned HTTP 401.
  • Signing back into Qiniu in Aside restored HTTP 200 in the browser, but the plugin needed its copied Cookie updated separately.
  • Switching the plugin to ctx.browser.cookieHeader("portal.qiniu.com") cannot reuse Aside through the current user-plugin browser policy, even though SweetCookieKit already supports Aside.

This does not establish that every new login invalidates older sessions; the verified issue is the expired copied session and the inability to follow the current Aside session automatically.

Source checked

In 0.81.0 (ee890b5), and in the current default-branch file checked when filing:

  • BrowserCookieImportSupport.importOrder(for:) falls back to [.chrome] when there is no built-in provider.
  • User plugins reach this path through UserProviderPluginCookieBroker.
  • The plugin documentation also describes Chrome-only imports for user plugins.

A local diagnostic using the existing Aside importer and a modified user-plugin resolver successfully fetched the Qiniu quota through the native plugin runtime. No modified CodexBar app has been installed.

Expected behavior

For this Qiniu plugin, after I sign in again in Aside, refreshing CodexBar should use the current browser session without requiring another manual Cookie copy. Please retain declared-domain approval, manual Cookie fallback, and the existing safeguards against background Keychain prompts.

This request is for the cookie access needed by a custom Qiniu quota plugin, not for a new bundled Qiniu provider or unrelated provider integrations.

Related: #4215 covered adding missing browsers to the underlying catalog; this request concerns the remaining Chrome-only restriction for user-installed plugins.

AI-assisted investigation and drafting; no credentials or account identifiers are included.

Dominant language
Swift
Stars
22.8k
Forks
2.2k
Avg merge
21h 55m
Merged PRs (30d)
403

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from steipete/CodexBar

All issues in steipete/CodexBar

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.