Never use param files in aquery commands - #29
Merged
armandomontanez merged 1 commit intoOct 1, 2026
Merged
Conversation
When param files are enabled (e.g. on Windows by default), command line flags are placed in an external file that can only be generated at build time. Because these don't generate during `aquery` time, when an agent tries to view them they may or may not exist thanks to prior (potentially stale) `build` commands. This can throw some models into confusion loops as they try to reason about why they can't get the information they need. This adjusts the skill to instruct agents to run `aquery` commands with param files disabled.
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
2 participants
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.
When param files are enabled (e.g. on Windows by default), command line flags are placed in an external file that can only be generated at build time. Because these don't generate during
aquerytime, when an agent tries to view them they may or may not exist thanks to prior (potentially stale)buildcommands. This can throw some models into confusion loops as they try to reason about why they can't get the information they need.This adjusts the skill to instruct agents to run
aquerycommands with param files disabled.