Search-SWE

Benchmark · Search-system engineering

Search systems built by agents.
Evaluated by execution.

Search-SWE evaluates whether a coding agent can autonomously investigate an environment, construct a search workflow, debug it, and deliver a working system under a fixed budget.

Open-ended methodology · Reproducible execution · Hidden tests
01 · INPUT
04 · OUTPUT
Information task corpus · sources · constraints
Coding agent inspect · build · iterate
Executable search reproducible · scored
fixed sandbox
same budget
Method agnosticNo prescribed retrieval recipe
Execution firstSystems are rebuilt and run
Resource awareTime, memory, and network count
Result groundedSearch quality meets hidden tests

01 · Motivation · Why

Search quality depends on more than a ranking formula.

01

Real systems are assembled

Useful search requires data inspection, indexing, retrieval, filtering, reranking, and output validation.

02

Agents face open environments

The best solution is not always known in advance. Agents must discover packages, models, tools, and constraints.

03

Plans are not deliverables

A convincing explanation is not enough. The final artifact must build, run, and retrieve the right result.

THE QUESTION

Can a coding agent turn an information need into a working, reproducible search system?

02 · Search-SWE · What

A benchmark for search-system engineering agents.

Given a task, data or information sources, a sandbox, public examples, and hidden tests, the agent must deliver an executable search system.

Search-SWE treats every information need as an end-to-end software-engineering problem.

The benchmark does not pre-select BM25, dense retrieval, RAG, reranking, or an agentic workflow. It evaluates the result produced by the agent under the same execution and resource conditions.

CORE PRINCIPLE

Do not score the plan.
Score the executable result.

01ExploreDiscover the environment
02ConstructBuild the search system
03ValidateTest and iterate
04DeliverSubmit a reproducible artifact

03 · Task construction · How

Make the task open-ended for the agent, precise for the grader.

TASK INSTANCE

Information need

A realistic query, corpus, source collection, or multi-step information requirement.

EXECUTION CONTRACT

Fixed sandbox

The same compute, storage, software, model, and network budget is available to every run.

GRADING SIGNAL

Public and hidden tests

Examples support iteration while hidden queries measure whether the delivered system generalizes.

The homepage highlights six selected tasks. The complete catalog contains seven defined tasks, including Task 2-3.

04 · Tasks

Six representative Search-SWE tasks.

The homepage gives a quick view of six selected tasks across implementation, optimization, and repair. Select any card to open its detailed task brief.

05 · Evaluation setting

Every submission has to survive four checks.

01

Build

Can the system build its index or required assets in a clean sandbox?

02

Function

Are inputs, outputs, IDs, ordering, and edge cases handled correctly?

03

Search quality

Does the returned Top-k list contain a verified positive result?

04

Resources

Does the run stay within the time, memory, disk, GPU, and network budget?

CLEAN-RUN SETTING Same sandbox profile·Rebuild from submission·Hidden query evaluation

06 · Results

The leaderboard starts with a reproducible run.

Results will be added as public tasks and baseline submissions become available.

RESULTS BOARD● preparing

Benchmark release in preparation

The first release will include task specifications, baseline systems, and reproducible evaluation reports.

Follow development

Search-SWE

Measure the system that gets built.

Explore the task catalog