Launch HN: Almanac (YC S26) – AI that knows your company

Re:Launch HN: Almanac (YC S26) – AI that knows your company by i18ner on Tuesday September 01, 2026 @03:20AM (#49519017)

Congrats on the launch, the approach of spending compute upfront is a compelling shift from what the current standard is.

I am curious as to how you handle state invalidation and unseen side-channels during those long-running tasks, because if the agent pauses a task for X days, say waiting for an email reply, but the projects params changed offline or in a channel that the agent has no eyes on, how does the system realize that the pre-compiled context has now gone stale? Does that also mean that proactive actions always require a HITL?

[ Parent | on HN ]

Re:Launch HN: Almanac (YC S26) – AI that knows your company by kushagrchitkar on Tuesday September 01, 2026 @08:35PM (#49530270)

This is an interesting edge case. When something similar happened, Almanac texted me asking for an update if I had followed up on email, and then I mentioned that I had followed up. So in this sense there was a HITL. A good solution could be to have account provenance for tasks, so that disconnection on accounts could update stale context

[ Parent | on HN ]