I've been using both Elicit and ResearchRabbit for the past six months to track new ML papers, specifically in the areas of efficient inference and model quantization. My workflow demands that I catch relevant pre-prints almost as soon as they hit arXiv, and I need to quickly assess whether they contain any substantial benchmarks or are just incremental. Both tools promise to solve this, but they take fundamentally different approaches, and their effectiveness is highly dependent on how you work.
Here's a blunt breakdown of my experience, focusing on concrete functionality rather than marketing promises.
**Elicit's "Ask a Question" Model**
* **Strength:** Unbeatable for targeted, one-off investigative queries. When I hear about a new technique (e.g., "Sliding Window Attention"), I can ask Elicit: "What are the most cited papers on sliding window attention for LLMs in the last 2 years?" and get a synthesized list with key claims extracted. The ability to ask "What are the limitations of this paper?" directly on a paper's page is its killer feature.
* **Weakness for Tracking:** It's reactive, not proactive. You have to know what to ask. It's less of a "keeping up" tool and more of a "drilling down" tool. Its email alerts are based on saved search queries, which are just keyword matches and lack the semantic/similarity intelligence of its main interface.
**ResearchRabbit's "Visualization & Discovery" Model**
* **Strength:** The map/graph visualization is excellent for discovering related work and tracing lineages. Adding a seminal paper (e.g., "LoRA: Low-Rank Adaptation of Large Language Models") and letting it build a "Similar Work" or "Earlier Work" graph surfaces papers I would have missed with pure keyword searches. Its "Colleagues also liked" feature often points to community-vetted quality.
* **Weakness for Tracking:** The UI can feel slow when you just want a clean, sortable list. The recommendation algorithm, while good for exploration, can sometimes drift from a tightly focused sub-topic if you're not careful with your seed papers.
**Critical Comparison for Daily/Weekly Paper Scanning**
| Aspect | Elicit | ResearchRabbit |
| :--- | :--- | :--- |
| **Primary Input** | Natural language question | Seed papers or authors |
| **Output for Tracking** | List of papers with AI-generated summaries/answers | Interactive graph + list of recommended papers |
| **Alert Relevance** | Medium (keyword-based only). High false-positive rate on broad ML terms. | High (similarity-based). New papers connected to your collection are flagged. |
| **Speed of Use** | Very fast for Q&A. Slower for browsing a feed. | Slower initial setup (curating seed collection). Faster for visual browsing of new connections. |
| **Benchmark Extraction** | Excellent. Directly pulls quantitative results from PDFs into a table. | Poor. You must open the PDF yourself. |
**My Synthesized Workflow**
I now use them in tandem, not in isolation.
1. **ResearchRabbit is my baseline tracker.** I maintain a "collection" for each of my focus areas (e.g., "LLM Inference Optimization"). I add every foundational and high-quality paper I find. Every Monday, I check the "Recommended" feed and the "Authors in your collection have new papers" alert. This catches ~80% of what's newly relevant.
2. **Elicit is my analytical drill.** When a new paper from ResearchRabbit looks promising, I open it in Elicit. I immediately use the "What are the main findings?" and "What are the limitations?" buttons. If it's a benchmark paper, I use the "View Results Table" feature to extract the key metrics without reading the full PDF. This is where Elicit saves hours.
The bottom line: If you want a *passive*, similarity-based alert system, ResearchRabbit is superior. If you need to *actively interrogate* a paper's content the moment you find it, Elicit has no equal. For a field moving as fast as ML, you realistically need both, but your primary "keeping up" mechanism will likely be ResearchRabbit's alerts and graphs. Elicit is the force multiplier for understanding what you've found.
Show me the benchmarks
I'm a data scientist at a ~200 person fintech, and I track ML papers daily for my work on model optimization. I've used both tools for about a year to monitor arXiv and specific conference feeds for work on our production LLM pipelines.
1. **Primary Workflow: Proactive vs. Reactive.** ResearchRabbit proactively pushes new papers via email alerts and a visual map. Elicit is reactive; you must formulate a specific question. For staying ahead, ResearchRabbit's alert system is essential, giving me a daily digest. Elicit won't notify you of anything new on its own.
2. **Handling of Pre-prints and Speed.** ResearchRabbit's alerts for arXiv feeds reliably hit my inbox within 24 hours of posting, which is fast enough for my needs. Elicit's database feels broader but less time-sensitive; its main value is extracting claims from papers that are already published or have some citation trail, not catching brand-new pre-prints.
3. **Real Pricing and Access.** Elicit's free tier is generous for individual researchers. ResearchRabbit is also free. Neither has tiered pricing that I've seen, so there's no direct cost, but the "cost" is in workflow fit. Elicit's paid API is priced per query for programmatic use, which adds up.
4. **Where Each Clearly Breaks.** ResearchRabbit's visualization of paper connections becomes messy and less useful once you're tracking more than a few niche areas. Elicit struggles with highly novel, zero-citation pre-prints and can give generic or inaccurate summaries if the paper isn't yet in its training corpus.
My pick is ResearchRabbit for your stated use case of "catching relevant pre-prints almost as soon as they hit arXiv." Elicit is my second tool for deeper investigation *after* the alert comes in. If you need to parse a high volume of new papers daily, tell us how many feeds you're monitoring and whether you work solo or need to share these alerts with a team.
Data is the new oil - but it's usually crude.
You're right about proactive vs reactive being the main distinction. ResearchRabbit's alert system is fundamentally for surveillance, while Elicit is for interrogation.
Your point about Elicit's database being "broader but less time-sensitive" matches my experience. I've found its latency for new arXiv pre-prints can be days, which is useless for catching things as they drop. It needs a citation graph to start working effectively.
The real cost is indeed workflow fit, but also noise. ResearchRabbit's daily digest often includes tangential papers, requiring manual filtering. It's a firehose you have to actively manage, not a smart feed.