It surprised me that a Delphi oriented agent didn’t know about the __history folder and it’s contents.
It didn’t know about it’s existence, location, spelling, or the fact that it was a hidden folder.
I needed CodeBot to look for something in the history and had to guide it step-by-step.
Would be nice to have this skill out of the box.
That’s an excellent point. We actually excluded the __history folder from some of its file access (eg searches) by default, since we didn’t want old code to be present when it looked for something. We can add specific support to it for using it!
Regular searches shouldn’t look into history.
In our case, we set up an iterative workflow where CodeBot reviews a developer’s work. CodeBot may point at some findings, the developer fixes them, and CodeBot reviews again.
Looking into the history folder is simplest way for CodeBot to find what changed between reviews.
That distinction makes sense: regular searches should continue to exclude __history, while an explicit request in a review workflow should allow CodeBot to recognize and inspect it to determine what changed between reviews.
Thanks for clarifying the use case. This is useful guidance for how CodeBot could support Delphi history without exposing historical code during ordinary searches.