Yep same, I often think why this isn’t a thing yet. Running some tasks in the night at e.g. 50% of the costs - there’s the batch api but that is not integrated in e.g. claude code
Summaries are a great first step — they reduce the friction of “re-reading”, and they can help you decide what’s actually worth keeping.
The question I’m curious about is what happens after the summary: do you want it to end as “good to know”, or do you sometimes want it to turn into something concrete (a bookmark tagged to an active topic, a short brief, or a next action)?
If you’re open to one more detail: how do you consume the summaries today — a daily digest you pull when you have time, or do you generate them only when you’re searching for something?
> Because we built the same inbox infrastructure as Gmail. Inboxes have threads, threads have messages, messages have attachments. You can search, label, filter, reply, forward. None of this comes out of the box with SES.
aws just gives you a low-level smtp + api service. we are the application layer they do not offer but your agents need to actually use email as first-class users.
No offence, but this reads to me like the classic dropbox HN comment
The idea is pretty solid, automation platforms often provision a mailbox per flow for this reason, so it makes sense to make a generic service that can be used through MCP for agents
Go to kimi chat, there will come up multiple suggestions of use cases. One of them will be the bargain robot. If you download their mobile app, the challenge to bargain will probably popup too!
Depending on how well you bargain with the robot, you can go as low as 0,99$ (difficult). Either way, their moderate plan doesn’t have to be 20$. The agent wants a good reason for why it should lower the price for you.
reply