Skip to content

fix(pi-fff): clarify tool prompt guidance#487

Open
themauveavenger wants to merge 1 commit into
dmtrKovalenko:mainfrom
themauveavenger:fix/pi-fff-prompt-guidance
Open

fix(pi-fff): clarify tool prompt guidance#487
themauveavenger wants to merge 1 commit into
dmtrKovalenko:mainfrom
themauveavenger:fix/pi-fff-prompt-guidance

Conversation

@themauveavenger
Copy link
Copy Markdown

@themauveavenger themauveavenger commented May 19, 2026

Summary

The official pi documentation details how best to use promptSnippet and promptGuidelines. The three tools, ffgrep, fffind, and fff-multi-grep had these, but they weren't written in a way that an agent would be able to associate them with the actual tool. Specifically, each line in promptGuidelines should be written as "Use my_tool when..." because they are separated from where the tool's name and promptSnippet are loaded into the system prompt.

The other change here is making it so that "@" doesn't end up as part of the query sent to fff.

Validation:

  • bun test packages/pi-fff/test/query.test.ts
  • cd packages/pi-fff && bun run typecheck
  • I've been using this extension as it is in pi for the last day with success and no errors. Agents have an easy time using the tools and don't fall back to bash as often.

Tune pi-fff prompt snippets and guidelines so Pi's flat tool guidance clearly names fffgrep, ffffind, and optional multi-grep tools. Also normalize @-mention path arguments and sync README tool docs with the current schemas and defaults.

Validation:
- bun test packages/pi-fff/test/query.test.ts
- cd packages/pi-fff && bun run typecheck
@dmtrKovalenko
Copy link
Copy Markdown
Owner

thanks but I need to find some time to run our eval layer

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