31–40 of 56 posts
Really simple and well designed website for the brand identity. Logo, background, UI and FAQ all flows well. Feel like I trust the project without knowing much about it or having the usual “trusted by” section. Keep it up!
The source-retention detail seems more important than the model list: if an email is compiled into a wiki and later deleted, or access is revoked, how quickly does that fact disappear from the personal or company wiki? Is the wiki rebuilt from current source state, or are removals handled as a separate event?
> that knows everything about your company Given that I don't know everything about my 4-person company, and that I never knew everything when it was a 1-person company (guess which person is that), this sound like https://x.com/mitchellh/status/2044529496217555333 (apologies for twitter link)
There is a lot of competition in this space, both commercial companies and open source. It seems like the biggest advantage for using one of these and not Claude or Codex is that you can use multiple models. Otherwise, those two have all the same features, or probably will in the next week. Are you able to use multiple models? Or I guess the first question is, what model(s) are you using? At this point, many enterpri…
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 own keys/subscription. We do not have formal benchmarks to measure improvement in performance. A big reason is that most benchmarks are very "atomic facts memory" focused. They'd give…
Cool! What model does it use now? Enterprises will definitely want to know.
And the other big question: Why not just use Claude or Codex (via CLI on a desktop or droplet)?
Earlier quoted context omitted.
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 own keys/subscription. We do not have formal benchmarks to measure improvement in performance. A big reason is that most benchmarks are very "atomic facts memory" focused. They'd give…
> Currently we don't allow for multiple model selection, but it is on the roadmap. Cool! What model does it use now? Enterprises will definitely want to know. And the other big question: Why not just use Claude or Codex (via CLI on a desktop or droplet)?
How are you different from the following cos? OpenTag Turnstone Memory Store Hyper Hyperspell Wato Savant Shepherd Glen OpenTag Janet AI screenpipe Cerenovus jo Bond Airweave Mem0 Theta Nessie Mosaic Onyx Slite Dashworks Circleback Stamp Tasklet Within Khoj
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 to then power capabilities. Two such examples are written in the post as proactive agents and the handling long horizon tasks. I believe this is still just scratching the surface. Havin…
I lead two different functional areas within tech and work in a larger tech platform for the parent company of a couple dozen operating companies.
All that to say “I would almost surely be better served by a hierarchy or general graph of wikis rather than just ‘me’ or ‘all 15K employees’.”
Even a 50 person company might benefit from “me”, “my team”, “my department”, and “whole company”.
Don’t have time to dig deep into it this afternoon, but want to comment to come back but also to suggest an expansion past your stated “one personal and one company” wiki. I lead two different functional areas within tech and work in a larger tech platform for the parent company of a couple dozen operating companies. All that to say “I would almost surely be better served by a hierarchy or general graph of wikis rath…