Repository navigation
fix: land a grok brief without the hidden trust prompt - #336
Open
douglasjarquin wants to merge 1 commit into
Open
douglasjarquin wants to merge 1 commit into
douglasjarquin wants to merge 1 commit into
Conversation
A Grok worker stops on a hidden prompt for the parent of the checkout's common .git, so the brief never lands. Record that directory under the worker's GROK_HOME before terminal.run, and leave an explicit refusal unchanged.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A Grok worker now receives its opening brief instead of stopping on a hidden trust prompt for the repository that owns the task worktree.
The prompt was why the brief never landed. The 20 second launch deadline stays where it is.
Sum records the directory Grok asks about, the parent of the checkout's common
.git, as trusted in that worker's GROK_HOME before the process starts. An existingtrusted = falsestays false. Workers already stopped on the prompt are not restarted.Validation
MISE_ENABLE_TOOLS=go,python,node python3 .agents/skills/verify/scripts/verify_run.py --base <merge-base of origin/main>passed on a clean tree. The record is.artifacts/verification/20261102T025820Z-d3b6d020/run.json. It certifies5fb55589991d89b5479fb209634c33ff0c1303f9(outcome pass, exit 0, 241 scenarios pass, 46 not-run).mise run test-livewas not run. The dispatch lab writes the trust file against a fake terminal and does not start Grok. The two workers already stopped on the prompt were left running.Four scenarios still have no visual comparison for this candidate.
questions.structured-decisionsandverify.fixture-git-isolationpassed their automated coverage with that note.pipeline.review-threadsandpipeline.review-thread-actionswere not exercised.The installed helper keeps the previous behavior until this merges and that installation is updated. There is no schema change.
grok-bots/sum/andgrok-bots/square/are unchanged: this writes one local trust file when a Grok worker is launched.Two launches that both see the folder as missing can each append it. Both lines say
trusted = true.