disconnect internet and if it runs well then you get an even safer feeling. for this example though, it still needs internet access to read and write the emails but the model processing the contents can be local to your system.

To be transparent - I do work at CrewAI. This is a side project I built using the open-source framework solve a real problem I was having with email management. Happy to answer any questions about how it works or the thought process behind it.

this is an interesting trend. email is just a database at this point. do you see this changing to something else?

it's wild. saas at your command.

yes, you could use the `knowledge_source=[file_name]` param in the agent to pass in the writing style or one shot examples. they'll get indexed in a vector db and used by the agent.

frfr let it all pile up

you're absolutely right. i definitely don't need an agent for that just like the first section of pulling in the emails. i can use the `@after_kickoff` decorator to empty trash.

fixing that right now; oversight on my end. this is purely a project i built to fix my email problems. also how is this spam?

If anyone has questions about implementation details or how to adapt it for different workflows, I'm happy to help.

Why not archive vs. the destructive delete. There is a risk of misclassification to promotion and then 2 days later delete. Seems like a default aggressive stance.

i thought about doing that but for this email account specifically, i hadn't used it in years and the storage is full and haven't been able top receive any emails isnce last Aug. so thought to delete since they're old and probably not important anymore.

i can definitely add an archive tool and pass that to the agent and remove the delete tool.