Skip to content

Make use of agentWorkingDir to specify directory agent runs from#128

Merged
haroonc merged 1 commit intogemini-cli-extensions:evalsfrom
kmontg:evals
Apr 11, 2026
Merged

Make use of agentWorkingDir to specify directory agent runs from#128
haroonc merged 1 commit intogemini-cli-extensions:evalsfrom
kmontg:evals

Conversation

@kmontg
Copy link
Copy Markdown

@kmontg kmontg commented Apr 11, 2026

This makes use of the new agentWorkingDir option from skillgrade. Previously, the agent only ran from the /workspace directory, but if source code is cloned it should be in a sub-dir (to prevent conflicts with files at the /workspace level). Here we are able to 'cd' to a directory like this and gemini will run from there too.

@kmontg kmontg requested a review from haroonc April 11, 2026 03:29
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates eval.yaml to generalize task instructions and specify agentWorkingDir for several evaluation tasks. It also refactors scripts/BASE_GEMINI.md, replacing the "Context Loading" section with "Strict Prohibitions" that limit parameter searching and tool usage. Review feedback indicates that the generalized instructions in eval.yaml may be too vague, and the removal of context-loading guidelines—coupled with new restrictions on resource discovery—could lead to agent failures when locating configuration files or executing standard deployment workflows.

@haroonc haroonc merged commit 3737c95 into gemini-cli-extensions:evals Apr 11, 2026
2 checks passed
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.

2 participants