verl-project/verl

[RFC][rollout] Should `actor_rollout_ref.rollout.mode` be removed since it should always be `"async"` now?

Open

#4604 opened on Dec 18, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Python (21,533 stars) (3,940 forks)auto 404
call for contributioncode qualitygood first issue

Description

Feature request

As is in title. cc @PeterSH6 @wuxibin89 .

Motivation

This makes the code cleaner.

Your contribution

I could help with cleaning if I get the bandwidth later. This is also a good first issue for learning about verl config and exercising global code search. So I also call for contributions from the community.

Contributor guide

Tech stack
python
Domain
backenddeveloper experience
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Pythonverl framework basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The task is to remove the `actor rollout ref.rollout.mode` configuration parameter and update all references to assume it is always 'async'. This involves searching the codebase for usage of this parameter and removing or simplifying related logic. The issue is a good starting point for learning the verl configuration system.