Almanac is an AI agent that knows your company. Connect your accounts in one click and it builds a self-updating "brain" from your work, then lives in Slack & iMessage to actually get tasks done. It has its own computer, so it keeps working after you close your laptop.
Free Options
Launch Team / Built With
EneyProactive AI for Mac. Free test, 20,000 credits.
Promoted
Hi @kushagra_chitkara
you mentioned using "dreaming" sleep time compute to resolve wiki contradictions. does that run as daily batch jobs on Modal or immediately when a new doc drops in?
@mohsinproduct It runs nightly. The way we think about context is quite similar to how humans hold memory. You have your immediate context, which we maintain when new things drop. And dreaming is where we consolidate the day's affairs to your permanent memory
@kushagra_chitkara the personal vs shared accounts is a nice touch. i’d be a little nervous about an agent having access to everything otherwise. congrats on the launch!
@kamal_sharma26 Hey Kamal, totally makes sense. I was on your side, but I have seen how much more productive I become with Almanac. I feel with the right permissions and infrastructure, more and more people will start leveraging agents for personal use cases
This is awesome. What happens if there's conflicting context on the same topic? like an old slack thread vs a newer doc? How does the brain decide what's the latest? I mean it's not even just dates. Sometimes half the info is in slack and half in a doc.
@alokvats This is the problem with current memory tools. That's the insight we have, that you need to spend resources upfront to resolve this conflicts, before making them permanent in the wiki. We take a thorough look at all your sources through something we call dreaming, which is basically sleep time compute, and then add the relevant information to the wiki
This is great! The personal vs. company wiki split is very important. How do you handle situations where private context should inform a company task without accidentally exposing that private information?
@marinos_eliades We have worked a lot towards the quality of the wiki. Usually, the relevant context is in the company wiki. If the task is a private task to the user, the context is available in the private wikis. Further, the agent still has access to the original sources, so it can check that as required.
How can I control which tools Almanac has access to? What if I only want read access to my emails?
@dsllwn Currently we ask for all the permissions upfront
This is crazy, this is a problem every company I've talked recently is having and ourself are experiencing. This is an incredible product
@daniel_martinez19 Thank you!! Would love to hear any feedback you might have
saw the reply above about currently asking for all permissions upfront rather than scoped access. that's the one thing that'd stop me from connecting real accounts to something that also keeps running after i close my laptop. is scoped/read-only access per tool on the roadmap or is all-or-nothing the plan for a while
@galdayan Currently we ask for all permissions upfront. Scoped access is something interesting, I hadn't thought about that as a hiccup before today, but definitely going to add it to the roadmap based on the response in the comments
@kushagra_chitkara good to hear, thanks for actually considering it instead of just saying "noted". scoped access is the kind of thing that's easy to deprioritize until someone hits it in production, so glad it's on the list now