Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Add webarena_verified_hard benchmark subset configuration

Open Beginner friendly
#415 0 comments 0 reactions 0 assignees View on GitHub

@sriram687 is already working on this.

Since Oct 26, 2026.

  • #416 by @sriram687 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python

Research direction

Start with browsergym/experiments/src/browsergym/experiments/benchmark/configs.py at the TODO around line 163 and read how webarena_verified is configured. Use the linked upstream subset file as the source for the 258 hard task IDs. Done means DEFAULT_BENCHMARKS["webarena_verified_hard"]() returns the hard subset while the existing full benchmark remains unchanged.

Written by the indexing model from the issue text.

Description

Feature Request: webarena_verified_hard Benchmark Preset

Add a preset for the official 258-task WebArena-Verified hard subset to BrowserGym.

File: browsergym/experiments/src/browsergym/experiments/benchmark/configs.py (line 163, resolves existing TODO) Breaking changes: None

Summary

DEFAULT_BENCHMARKS only exposes the full 812-task webarena_verified. This adds webarena_verified_hard, filtered to the 258 hard tasks from the upstream subset file.

  Full Hard
Tasks 812 258
Eval time / API cost baseline ~68% lower

Why

  • Faster, cheaper iteration on complex multi-step tasks
  • One-line standardized access, no ad-hoc filter scripts:
DEFAULT_BENCHMARKS["webarena_verified_hard"]()
  • Existing webarena_verified stays untouched
Dominant language
Python
Stars
1.4k
Forks
202
Avg merge
12d 2h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ServiceNow/BrowserGym

All issues in ServiceNow/BrowserGym

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.