alibaba / alibaba/ROLL

Verify evals on Papers with Code

Open
#482 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
3.4k
Forks
312
Avg merge
1h 2m
Merged PRs (30d)
2

Description

Hi,

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

I've made the [paper](https://paperswithcode.co/paper/2512.24873) and [7 paper-native evaluations](https://paperswithcode.co/paper/2512.24873#results) available on Papers with Code.

The paper has results on [Coding Agents](https://paperswithcode.co/tasks/coding-agents), [Agents](https://paperswithcode.co/tasks/agents), and [Deep Research Agents](https://paperswithcode.co/tasks/deep-research-agents) task pages.

The ROME (30B MoE, activated 3B) result currently ranks third on [Terminal Bench 1.0](https://paperswithcode.co/benchmark/terminal-bench-1-0?task=coding-agents&eval=21581).

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: #3 on Terminal Bench 1.0](https://paperswithcode.co/api/v1/papers/2512.24873/leaderboard-badge.svg?eval=21581&live=1)](https://paperswithcode.co/api/v1/papers/2512.24873/leaderboard-badge-link?eval=21581)

Kind regards,

Niels

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked paper, its seven Papers with Code evaluation results, and the Terminal Bench 1.0 leaderboard entry. Compare the score, model name, benchmark protocol, and openness metadata with the paper or official release artifacts; the work is done when inaccuracies are identified and the relevant entries are corrected or confirmed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.