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

Improve readability of red pace text in stacked menu bar layout

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

Maintainers usually reply within 1 day

@steipete is already working on this.

Since Oct 27, 2026.

  • #4791 by @arnodirlam — open
  • #4812 by @steipete — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
frontend

Research direction

Start by locating the compact two-line menu bar layout and the Color Pace Indicator rendering, then inspect the actual menu bar background and appearance with the reported red values such as +13% and +7%. Keep the pace-state colors and their meaning; done when positive pace text is easier to read in the compact layout across the relevant appearances.

Written by the indexing model from the issue text.

Description

clawsweeper:fix-shape-clear clawsweeper:needs-live-repro clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🐚 platinum hermit P2

Context

With Color Pace Indicator enabled, positive pace values are red to indicate usage ahead of pace. In the compact two-line menu bar layout, the red text is difficult to read at a glance. The reported example shows +13% and +7%.

Suggested outcome

Keep the pace-state colors and their meaning, while making red pace text easier to read in the compact menu bar. Please assess the text against its actual menu bar background and appearance before choosing a rendering change.

This is a color-legibility report; #4713 separately proposes heavier text for stacked layouts. The color meaning was introduced in #3428 and implemented by #3429.

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.