kushagrchitkar

4 ms·

1.
by kushagrchitkar 1mo ago
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 b
2.
by kushagrchitkar 1mo ago
We have been debating what the best benchmark to show would be. I'd love to test it out on long horizon tasks, but then we're thinking of best to make the base wiki to test it out
3.
by kushagrchitkar 1mo ago
Forgot to reply instantly, but its gone now: https://usealmanac.com/pricing
4.
by kushagrchitkar 1mo ago
I agree with the take. This was on the roadmap, but given the responses today, we will make permissions inside the company a bigger priority. To brainstorm, would you want the ability to define teams inside a company as well? I was thinking
5.
by kushagrchitkar 1mo ago
Hey, glad you found it interesting to work on. We're not looking for interns right now, but shoot me an email at kushagra@usealmanac.com, would love to keep people in mind
6.
by kushagrchitkar 1mo ago
Its GPT-5.6-terra under the hood. Also we want to control the harness. Features like proactivity/long tasks are not possible the way Claude/Codex work today. We do plan on releasing our desktop app, which would have these things i
7.
by kushagrchitkar 1mo ago
Wiki updates happen once a day through. That is when the entire day's context is updated in the wiki. That is when the fact disappearance would take place
8.
by kushagrchitkar 1mo ago
The current permission implementation is binary. It is either personal to you, or is shared with everyone in the company. Having more granular permissions is something that has been requested often, and it is on our roadmap. I'm curiou
9.
by kushagrchitkar 1mo ago
Thank you
10.
by kushagrchitkar 1mo ago
There is truly a lot of competition in the space. The reason we're confident we stand out is because of our wiki layer. We have seen both the benefits of having a detailed compiled wiki, and more importantly, actually using this layer
11.
by kushagrchitkar 1mo ago
Currently we don't allow for multiple model selection, but it is on the roadmap. We do have a cli, which allows you to use the wiki layer and the tools in whatever harness you prefer. Further, we want to allow users to also bring their
12.
by kushagrchitkar 1mo ago
I'd love to hear how you're approaching this problem, and what would you like to see on the website to convince you to try out Almanac
13.
by kushagrchitkar 1mo ago
Thanks! I saw the video again and can't look beyond the low resolution now lol. We knew from day 1 that trusting agents is going to be the most difficult part of our product, so we take privacy and security with the utmost seriousness
14.
by kushagrchitkar 1mo ago
The documentation is not just for lookup queries. Having this layer betters the quality of responses, but also enables a lot of features we have in Almanac/plant to add. I mentioned in the post how this layer enables proactive agents a
15.
by kushagrchitkar 1mo ago
Just checked out WorkIQ, the promise is quite similar. Spend compute and time upfront developing the knowledge base, which will later result in much better answers
16.
by kushagrchitkar 1mo ago
For us, these two things have not been very different. We do make both, a personal and a company wide wiki, so Almanac is useful in both regards
17.
by kushagrchitkar 1mo ago
Our browser is interactive, in the sense that one could click around the browser, as well as the agent. Usually for 2FA logins, Almanac would hand it over to the human, who'd complete login, and then continue. We use Browserbase for th
18.
by kushagrchitkar 1mo ago
It of course gets more magical the longer you use it, but we've felt it starts providing utility from first few days itself. It could identify things that are going on immediately in your life and help there
19.
Launch HN: Almanac (YC S26) – AI that knows your company(usealmanac.com)
59 points by kushagrchitkar 1mo ago|48 comments