chore: detect and converge LaunchAgent interpreter drift
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- macos, python
- Domain
- devops, infrastructure, tooling
Research direction
Start by reading PR #729 and the BrainBar cask updater, then inventory the com.brainlayer.* LaunchAgent plists, their ProgramArguments, and wrapper-resolved interpreters. Define the approved Homebrew runner contract and add fixtures for Homebrew, repository .venv, framework-pip, and missing-interpreter states. Done means read-only census and convergence are demonstrated on both Macs without changing the production database.
Written by the indexing model from the issue text.
Description
Problem
The v1.5.9 deploy exposed multiple interpreter families across ~/Library/LaunchAgents/com.brainlayer*.plist: Homebrew, the repository .venv, and a framework-level pip install. PR #729 now catches the shell PATH-shadow case, but its BrainBar cask updater does not own every maintenance LaunchAgent and should not silently widen into a fleet-wide plist migration.
Acceptance criteria
- Inventory every
com.brainlayer.*LaunchAgent ProgramArguments and any wrapper-resolved interpreter. - Define the canonical approved runner/interpreter contract for Homebrew-installed BrainLayer.
- Fail closed or report actionable drift for repository
.venv, framework-pip, missing, and mixed-version runners. - Add fixtures for Homebrew, repo-venv, framework-pip, and missing-interpreter states.
- Prove the read-only census and convergence path on both Macs without mutating the production database.
Relationship
- Follow-up to #729.
- #729 remains responsible for BrainBar cask/app drift and shell PATH resolution only.
— brainlayerCodex (worker) · codex/gpt-5.6-sol
- Dominant language
- Python
- Stars
- 9
- Forks
- 7
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 211
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EtanHey/brainlayer
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EtanHey/brainlayer#999 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EtanHey/brainlayer#986 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
EtanHey/brainlayer#985 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EtanHey/brainlayer#982 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
EtanHey/brainlayer#676 ·
Maintainers usually reply within 1 day
All issues in EtanHey/brainlayer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
spec-kitty/spec-kitty#5319 ·
Maintainers usually reply within 1 day
-
backend::vllm diffusion multimodal
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
openai/openai-agents-python#5229 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day