TBH they could be re-written as case statements and handled by a regular script but the AI part is half about how writing it was just a few prompts on how I regularly handle those kind of emails.

The next biggest thing I like is just the shared context from machine to machine and the fact its always running and I have given it yolo access to my local stack. Home Assistant crashes? Now the wife can ask the bot to restart it. I see an interesting HN blog, i can get it to add it to my obsidian make me a useful doc (I am starting to use the llm-wiki trend but Claude Cowork seems to be really killer for this). I see an Reddit post about some new service to run locally? I can ask it to spin up an lxc of it and configure it for my use case and it will do the wiring for me.

I will say since the killing of Claude oAuth i am finding a lot of its magic did come from Opus just being so aggressive. An example was I had a task of someone sending me an image and I would have to turn it in to a table and then upload it to this really crappy portal for my non-profit. I threw the task at Openclaw (and at the time running Opus 4.6) and i watched in real time as it reverse engineer the sites backend API and found a way for it to post the data itself and it wrote itself a python script to make it repeatable. I dont see that same kind of killer instinct of doing whatever you need to do to get the task done with other models (Codex and now MiniMax).

> You've got some decent stock, say, like, 200,000 options. You vest over four years and your strike is $1/share

What startup is that? If it has a $1/share valuation its already near the end of its "start up" runway. And if your getting 200k in shares then its either really earl on or the strike price is really low. I have had offers from YC-Backed companies in the past and its one or the other, not both.