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

SHAPER VLABench reproduction: 800-episode evaluation split and sandbox configuration

Open
#650 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start with the linked SHAPER recipe and inspect its episode configuration plus harness_optimizer.txt to identify the defined training and validation splits and sandbox modules. Trace the evaluation entry point and documentation for the command that generates or consumes the 800-episode C1–C4 manifests. Reproduction is complete when the exact manifests, runtime configuration, command, and final evolved skill/harness artifacts are identified and verified.

Written by the indexing model from the issue text.

Description

Hi, I’m trying to reproduce the VLABench results using the SHAPER recipe on v0.x.

I have two questions:

  1. The recipe defines 15 training and 24 validation episodes, while the paper reports 800 held-out episodes across C1–C4. Where can I find the exact evaluation manifests and the command used to reproduce Table 2?
  2. harness_optimizer.txt says modules such as collections are preloaded, but the sandbox namespace does not appear to provide them. Generated candidates encounter NameError: name 'collections' is not defined. What runtime configuration should be used?

Could you also share the final evolved skill and harness used for the reported results?

Thank you!

Dominant language
Python
Stars
18.8k
Forks
1.7k
Avg merge
3d 13h
Merged PRs (30d)
10

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 microsoft/agent-lightning

All issues in microsoft/agent-lightning

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.