Skip to content

fix(resolve): map grok-build to grok in the pid walk - #860

Open
apstndb wants to merge 2 commits into
fujibee:mainfrom
apstndb:fix/859-grok-build-pid
Open

fix(resolve): map grok-build to grok in the pid walk#860
apstndb wants to merge 2 commits into
fujibee:mainfrom
apstndb:fix/859-grok-build-pid

Conversation

@apstndb

@apstndb apstndb commented Aug 17, 2026

Copy link
Copy Markdown

Fixes #859.

_agmsg_agent_binaries has no grok-build arm, so the type falls through to claude codex gemini and grok-build watchers are not liveness-gated.

Independently mergeable. Split out of #856 because cursor monitor only needs the cursor-agent arm. Reading detect_proc from the manifest stays #631.

Do not list agent (Homebrew grok-build and the Cursor CLI installer share that basename). The policy is on #856; this PR comments the omission.

#858 stays a draft until this and #857 have landed.

Test plan

  • bats tests/test_resolve_project.bats --filter agent-binaries
  • bats tests/test_resolve_project.bats
  • CI green

Without this arm, grok-build falls through to claude/codex/gemini, so
agmsg_agent_pid never sees a live grok and watchers are not liveness-gated.

Co-authored-by: Cursor <cursoragent@cursor.com>
…ibee#856)

Homebrew grok-build and the Cursor CLI installer both ship `agent`.
Listing it on either type would attach the wrong pid (fujibee#93).

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: grok-build pid walk falls through to claude/codex/gemini

1 participant