Often an AI reads info that might be outdated and then assumes it is right. It doesn't really have the concept of "this is old info, maybe I shouldn't trust it". How about creating a hook for when an agent reads one of the journal files that checks the file mtime and outputs a "this content is x days old, be sure to verify it is not outdated" as additional info.
Secondly, I don't think an AI agent has any way to "skim" content. I mean it either reads all or parts of the content or it greps it. Why not do some index.md file that lists all the journal files together with a short description (inspired by the Open Knowledge Format)?
I posted this a few months ago, but figured I'd try again since I don't hear about this pattern much. I'm using it daily, especially for exploratory tasks. It helps tremendously. (https://news.ycombinator.com/item?id=47896577)
I like the idea - but I have two concerns.
Often an AI reads info that might be outdated and then assumes it is right. It doesn't really have the concept of "this is old info, maybe I shouldn't trust it". How about creating a hook for when an agent reads one of the journal files that checks the file mtime and outputs a "this content is x days old, be sure to verify it is not outdated" as additional info.
Secondly, I don't think an AI agent has any way to "skim" content. I mean it either reads all or parts of the content or it greps it. Why not do some index.md file that lists all the journal files together with a short description (inspired by the Open Knowledge Format)?
I posted this a few months ago, but figured I'd try again since I don't hear about this pattern much. I'm using it daily, especially for exploratory tasks. It helps tremendously. (https://news.ycombinator.com/item?id=47896577)