explaingit

sahel-sh/deephone

Analysis updated 2026-05-18

2PythonAudience · researcherComplexity · 5/5Setup · hard

TLDR

Research code for an ACL 2026 paper studying whether AI search agents should spend compute on reranking documents or on more reasoning, plus a new cost metric.

Mindmap

mindmap
  root((DeepHone))
    What it does
      Rerank vs reason study
      Effective Token Cost
      BrowseComp-Plus benchmark
    Tech stack
      Python
      vLLM
      FAISS
      Pyserini
    Use cases
      Reproduce paper results
      Compare rerankers
      Benchmark agents
    Audience
      Researchers
      ML engineers
    Requirements
      GPUs
      Java 21
      uv environment

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Reproduce the experiments and figures from the Rerank Before You Reason paper.

USE CASE 2

Compare how reranking versus extra reasoning affects a deep search agent's accuracy and cost.

USE CASE 3

Benchmark different retrievers, rerankers, and agent models on the BrowseComp-Plus dataset.

USE CASE 4

Measure the Effective Token Cost tradeoff between reranking depth and reasoning effort.

What is it built with?

PythonvLLMFAISSPyseriniJavauv

How does it compare?

sahel-sh/deephone0-bingwu-0/live-interpreter0cm-labs/tokenizer-benchmark
Stars222
LanguagePythonPythonPython
Setup difficultyhardmoderatemoderate
Complexity5/52/52/5
Audienceresearchergeneralresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Requires multiple GPUs to serve large language models locally, plus a Java runtime and a specific Python environment manager.

No license is stated in the README, so usage rights are unclear.

In plain English

DeepHone is the research code behind an academic paper called Rerank Before You Reason, accepted at ACL 2026 Findings. It studies AI agents that search through documents and reason about them to answer hard questions, sometimes called deep search agents. The question the paper asks is where an agent's limited compute budget is best spent: on having the AI think longer at search time, or on reranking, a step that reorders retrieved documents by relevance before the agent starts reasoning about them. To test this, the authors use a benchmark called BrowseComp-Plus, made up of 830 questions that require real reasoning, searched against a fixed set of about one hundred thousand documents. They separately measure the retriever that finds candidate documents, the reranker that reorders them, and the agent that reasons over the results, and compare the tradeoffs using a new measurement they call Effective Token Cost. Their main finding is that reranking reliably improves both how relevant the retrieved documents are and how often the agent gets the final answer right, and that a moderate amount of reranking is often a cheaper way to gain accuracy than making the agent reason more. They also find that small, efficient rerankers capture most of these gains at a much lower cost than larger ones. This repository builds on an existing project called BrowseComp-Plus, keeping its benchmark, its retrieval methods, and its agent clients for services including OpenAI, Anthropic, Gemini, and others, while adding the new reranking integration and cost analysis used in the paper. It provides two kinds of rerankers, one that reranks whole lists of documents at once and one that judges documents one at a time, several retrieval methods including keyword based and embedding based search, scripts that use another AI model as a judge to score answers, and scripts that generate the charts and tables from the paper. Running the full pipeline requires a fairly involved setup: a Python environment managed with a tool called uv, a Java runtime for the keyword search component, and access to GPUs to run the large language models locally using a serving tool called vLLM. The README documents the exact commands needed to reproduce each table and figure from the paper.

Copy-paste prompts

Prompt 1
Explain the difference between listwise and cross-encoder reranking as used in this project.
Prompt 2
Walk me through setting up the environment with uv and Java for this repository.
Prompt 3
Explain what Effective Token Cost measures and why the paper introduces it.
Prompt 4
Show me the command to run the deep-research agent with reranking at depth 20.

Frequently asked questions

What is deephone?

Research code for an ACL 2026 paper studying whether AI search agents should spend compute on reranking documents or on more reasoning, plus a new cost metric.

What language is deephone written in?

Mainly Python. The stack also includes Python, vLLM, FAISS.

What license does deephone use?

No license is stated in the README, so usage rights are unclear.

How hard is deephone to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is deephone for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.