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

Allow multiple instances of any provider in separate or combined menu-bar layouts

Open
  • Is something wrong?
#4,772 3 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
swift
Domain
desktop, devtools

Research direction

Start by tracing the existing provider configuration, menu-bar controls, and icon layout builder to see how provider identity and quota metrics are represented. The issue names no files or tests, so locate those entry points in the project before estimating the implementation. Done means independently named and configured instances can appear as separate icons or as labeled elements in one combined layout, with each indicator retaining its own account and quota.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🌊 off-meta tidepool P3

Please allow the same provider to be added more than once, with each instance independently named, configured, and bound to its own account or supported credential/profile source. Each instance should participate in the existing menu-bar controls and icon layout builder just as a different provider does.

Codex is one example of a general need. Users can have personal, work, or other accounts for Claude and other providers too. A setup such as Codex Personal + Codex Work should be as configurable as the existing Codex + Claude setup.

Both presentation choices are important:

  • Separate icons: show Codex Personal, Codex Work, Claude Personal, and Claude Work as independent menu-bar items, each displaying its own selected quota windows.
  • A combined icon built with the existing layout builder: add labeled bars or percentages from several instances to one icon. Each layout element should explicitly select its provider instance/account and quota metric, so two Codex accounts can remain visible simultaneously inside that icon.

For example, the user could choose either:

[Codex Personal: Session / Weekly]  [Codex Work: Session / Weekly]

or one custom item containing independently bound elements:

[Codex Personal: Session bar | Codex Work: Weekly % | Claude Work: Session %]

Requested behavior:

  • Adding or duplicating a provider creates an independent configuration/display instance, with a short user-selected name. Where saved accounts already exist, an instance can bind to one of them.
  • Instances use the existing controls for enabling, hiding, ordering, icon styles, layouts, and separate/combined presentation.
  • The layout builder can select a specific instance and quota metric for each element, including several accounts of the same provider in one icon.
  • Every indicator stays bound to its own account when the active or followed account changes. Its settings and usage remain independent of the other instances.
  • Both modes show the selected accounts' quotas while the dropdown is closed. A combined layout preserves the separate account values and labels.

Saving several accounts inside one provider, showing them only in the dropdown/Overview, or switching the followed account does not provide this flexibility. A separate-icons-only mode that is disabled with Merge Icons would address only part of the request; combined layouts should remain in scope.

This is a user-facing configuration and display request. Provider-specific authentication and external account-switching mechanisms can remain with their existing implementations. The internal representation of provider types, instances, and account identities is an implementation choice for maintainers.

Related history: #1268 and #1843. Both discussions are closed. This issue explicitly tracks independent provider instances in the existing menu-bar presentation controls and layout builder, beyond the multi-account storage and switching features that have already shipped.

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

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.