I have recently found myself drawing parallels between deep research and knowledge working org structures. For example,board exec asks senior exec a question about a particular product. The senior exec then has to fire off emails to say 5 managers, who might go down their tree to ICs, all the info is gathered and synthesised into a response. Normally this response takes into account some angle the senior exec might h…
Show HN: Open-source Deep Research across workplace applications
21–30 of 32 posts
Re: Show HN: Open-source Deep Research across workplace applications
#22What's the difference between deep research and RAG?
Re: Show HN: Open-source Deep Research across workplace applications
#23Cool product. Few Qs: - What would you say is the agentic approach's special sauce over a typical RAG pipeline, ie query->multi-query generation->HyDE->vector search->bm25 search->RRF->rerank->evaluate->(retry|refuse|respond) that differentiates the approach? - If a user has 20 services connected, how does the agent know how to call/search/traverse the information in the right order? - Do you have any internal evals…
Quite a lot to cover here! So in addition to the typical RAG pipeline, we have many other signals like learning from user feedback, time based weighting, metadata handling, weighting between title/content, and different custom deep learning models that run at inference and indexing time all to help the retrieval. But this is all part of the RAG component. The agent part is the loop of running the LLM over RAG system…
Would you ever extend your app to search the web or specialized databases for law, finance, science etc?
Re: Show HN: Open-source Deep Research across workplace applications
#24Re: Show HN: Open-source Deep Research across workplace applications
#25Re: Show HN: Open-source Deep Research across workplace applications
#26Re: Show HN: Open-source Deep Research across workplace applications
#27I have recently found myself drawing parallels between deep research and knowledge working org structures. For example,board exec asks senior exec a question about a particular product. The senior exec then has to fire off emails to say 5 managers, who might go down their tree to ICs, all the info is gathered and synthesised into a response. Normally this response takes into account some angle the senior exec might h…
Yup, hopefully with Onyx, the folks who have these questions can just fire off a query with agent mode turned on and the LLM will research the relevant tree of knowledge and come back with an answer in the fraction of the time it would take for people to do it with all of the handoffs in between.
Re: Show HN: Open-source Deep Research across workplace applications
#28Re: Show HN: Open-source Deep Research across workplace applications
#29Re: Show HN: Open-source Deep Research across workplace applications
#30Before sharing how it works, I want to highlight some of the challenges of a system like this. Unlike deep research over the internet, LLMs aren’t able to easily leverage the built in searches of these SaaS applications. They each have different ways of searching for things, many do not have strong search capabilities, or they rely on their internal query language. There are also a ton of other signals that web searc…
When you talked about "document index is a hybrid index of keyword frequencies and vectors", I am a bit curious of how to get them. In pre-processing, do you have to use LLM / models go through documents to get keywords? What about vectors? Are you using embed model to generate them? Does that imply preprocess has to be done whenever there is new doc or any modification in existing doc? Would that be costly in time? Any spicy cook to make the preprocessing more efficient?