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

BrainBar Runtime Agents over-counts Codex by 1: Codex Computer Use helper under ~/.codex/computer-use counted as a session

Closed Beginner friendly
#984 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
macos, swift
Domain
desktop

Research direction

Start in Dashboard/AgentActivityMonitor.swift by reading isAppBundled and the existing agent-count fixtures. Add the RED fixture row for the synthetic ~/.codex/computer-use/…app/Contents/MacOS/… path, then run the relevant fixture or test and confirm it is no longer counted as a top-level Codex session.

Written by the indexing model from the issue text.

Description

bug

Found by the v1.5.42 installed deploy (lead brainlayerClaude-90982d09), on both Macs.

Symptom: the Dashboard → Runtime "Agents" row (from #977) counts one extra Codex session on the M4 and on the M1.

Root cause: the helper ~/.codex/computer-use/Codex Computer Use.app/Contents/MacOS/SkyComputerUseService is counted as a top-level Codex CLI session. The app-bundled exclusion (isAppBundled in Dashboard/AgentActivityMonitor.swift) only excludes paths under /Applications/…app/ and /System/, so an .app bundle living under a user directory passes.

Evidence (counts only): removing that one process drops the Codex count by exactly 1 on each Mac. On the M4 the Claude count (10) matched the 10 live Claude panes in cmux.

Fix direction: treat any executable inside a *.app/Contents/ bundle as app-bundled, wherever the bundle lives, not only under /Applications. Add a RED fixture row with a synthetic ~/.codex/computer-use/…app/Contents/MacOS/… path.

Vendor split: UI/behaviour, so Opus implements and Codex reviews.

— brainlayerClaude-90982d09 (Claude Opus 5.5)

Dominant language
Python
Stars
9
Forks
7
Avg merge
4h 25m
Merged PRs (30d)
404

Getting set up

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 EtanHey/brainlayer

All issues in EtanHey/brainlayer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.