Skip to content

Stop echoing caller file paths in recommended_next_steps - #99

Merged
rajeeja merged 1 commit into
mainfrom
rajeeja/next-steps-no-path-echo
Aug 6, 2026
Merged

Stop echoing caller file paths in recommended_next_steps#99
rajeeja merged 1 commit into
mainfrom
rajeeja/next-steps-no-path-echo

Conversation

@rajeeja

@rajeeja rajeeja commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Every suggested next step interpolated the caller's own absolute grid and data paths back into the string, so a four-step list repeated the same path four times and those echoed paths alone ran 28-36% of an inspection result. Steps now name a caller-supplied value by parameter name, spell out only values the server discovered, and bracket what is still missing, which shrinks results 18-34% and raises the computed-answer share from 25-49% to 39-61%. Closes #83.

Every suggested call interpolated the caller's own absolute grid and data
paths back into the string, so a four-step list repeated the same path four
times; those echoed paths alone were 28-36% of an inspection result. Steps
now name a caller-supplied value by parameter name, spell out only values
the server discovered, and bracket what is still missing, which shrinks
results 18-34% and raises the computed-answer share from 25-49% to 39-61%.
@rajeeja
rajeeja merged commit a4cb3fe into main Aug 6, 2026
7 checks passed
@rajeeja
rajeeja deleted the rajeeja/next-steps-no-path-echo branch August 6, 2026 13:56
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.

A tool catalog is 74% of what the server sends back

1 participant