Mr_Noodle wrote:Thanks for elaborating. What if ChatGPT is inconsistent with its summary or is just plain wrong? Are you willing to train the model yourself?
Sure, that will happen. I would maybe start with reviewing the filename before finally sorting. Not sure if I would train the LLM myself. Maybe it would be best to start with simple use cases. For all basic documents chatGPT returned overall satisfying results.
I think there are meaningful use cases which are far away from simple AI slogans.
I could think of general support in the application, like error detection and optimization, where the AI checks existing rules for conflicts, redundancies or inefficient processes and suggests improvements. Hazel could also analyze files and suggest rules based on user behavior or file patterns that can be adopted or adapted with a single click.
But the bigger value might be pre-configured options to connect to existing tools (GPT /Gemini etc) - the token to access the service is just configurable by the user.
I would see several information valuable for AI analysis:
1. new "AI" Date fields like creation date or due date (e.g. on invoices)
2. Sender / Creator of the file
3. Category: e.g. “invoice”, “image”, “contract”, ideally from a pre-defined list (so if I have 20 categories defined and the document cannot matched to one of them it will be named "unknown", so I have to look at it)
Im pretty sure there are much more possibilities.
The advantage would be that the current logic of Hazel could be retained but Hazel would become much more powerful.
Since I love Hazel, I just wanted to start the discussion. I think it would be great if Hazel could continue to develop and become even better known...