microsoft / microsoft/AutoSaddler

Verify evals on Papers with Code

Open Beginner friendly
#6 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
225
Forks
15
Avg merge
2d 8h
Merged PRs (30d)
3

Description

Hi,

Niels here from the open-source team at Hugging Face. Congratulations on your work!

I've made the paper and 3 paper-native evaluations available on Papers with Code.

The paper has results on Coding Agents and Agents task pages.

The AutoSaddler result currently ranks first on GAIA2.

Would it be possible to verify these results and let me know if any score, model name, benchmark protocol, or openness metadata should be corrected? The imported rows are tied to the paper or its official release artifacts; comparison-table baselines were not added.

You can also edit the task, methods, project page, and GitHub URL directly from the paper page using your Hugging Face account.

If you'd like to showcase the results in your repository README, you can copy these live leaderboard badges (or use the “Copy PwC badge” button in the Results section):

Papers with Code: SOTA on GAIA2

Kind regards,

Niels

Contributor guide

Open the contributing guide

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.

Research direction

Start with the linked Papers with Code paper page and its three paper-native evaluation results, then compare them with the paper or official release artifacts. Verify the score, model name, benchmark protocol, and openness metadata for the AutoSaddler rows, and report any corrections; completion means the imported results are confirmed or the needed changes are identified.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.