Open-AgentRL
RL training framework for reasoning, tool use, and interactive agent environments.
- Source repo
- Gen-Verse/Open-AgentRL
- Stars
- ★ 641
- Last updated
- 3mo ago
- License
- Apache-2.0
- Primary language
- Python
- FA score
- 28/100 · Major gaps
At a glance
- Works with
- Portable with changes
- You'll need
- Typical use
- A research team reproducing agentic-reasoning experiments from 3K SFT and 30K RL datasets, then evaluating on AIME, GPQA-Diamond, or LiveCodeBench-v6.
- Main limitation
- It is not a plug-and-play inference product: adopters must provide models,
.parquetdata, absolute paths, and scenario configuration. - Source review
- 28/100 · Major gaps 8 safety controls not found
What does this agent do, and when should you use it?
Open-AgentRL brings together three agentic-RL research implementations: DemyAgent, RLAnything, and AutoTool. DemyAgent covers cold-start SFT and GRPO-TCR-based agentic RL, with evaluation workflows for math, science, and coding reasoning. RLAnything performs closed-loop optimization of policy, reward model, and environment for OSWorld computer control, AlfWorld text games, and coding tasks. AutoTool supplies a two-phase dynamic tool-selection framework that first stabilizes tool-integrated trajectories and then refines multi-step selection with KL-regularized Plackett–Luce ranking. It is a research training repository that requires users to supply models, data, configuration, and, for some scenarios, external execution infrastructure rather than a ready-to-deploy chat service.
For DemyAgent, the repository reads SFT, RL, and evaluation data in .parquet format, fine-tunes Qwen models through recipe/demystify/qwen3_4b_sft.sh or qwen2_7b_sft.sh, then runs GRPO-TCR with grpo_tcr_qwen2_7b.sh or grpo_tcr_qwen3_4b.sh. Code-execution tasks use a SandboxFusion /run_code endpoint, configured in sandbox_fusion_tool_config.yaml and verl/utils/reward_score/livecodebench/code_math.py. RLAnything launches training from scenario-specific YAML files through osworld_rl.py, alfworld_rl.py, and coding_rl.py, with matching *_eval.py evaluation programs. The AutoTool framework covers Phase I SFT-plus-RL trajectory stabilization and Phase II ranking-based tool-selection refinement; the repository says its full training data and toolset are still forthcoming.
- A research team reproducing agentic-reasoning experiments from 3K SFT and 30K RL datasets, then evaluating on AIME, GPQA-Diamond, or LiveCodeBench-v6.
- A team with a local or cloud SandboxFusion endpoint training Qwen-family models that execute code during reasoning.
- A team that has configured Volcengine cloud VMs, security groups, and an OSWorld image for RL training or evaluation of GUI computer-control policies.
- A researcher who has downloaded AlfWorld data and needs to train or evaluate RL policies in a text-based interactive game.
- A group investigating dynamic selection over a large, evolving tool library and willing to work before AutoTool’s full data and toolset are released.
How do you install or deploy this agent?
For DemyAgent:
git clone https://github.com/Gen-Verse/Open-AgentRL.git
conda create -n OpenAgentRL python=3.11
conda activate OpenAgentRL
cd Open-AgentRL
bash scripts/install_vllm_sglang_mcore.sh
pip install -e .[vllm]For RLAnything:
conda create --name rlanything python=3.10
source activate rlanything
pip install -r requirements_rlanything.txtThe supplied material does not state an API-key requirement. Code-execution RL additionally needs a SandboxFusion deployment or a Volcano Engine Cloud FaaS /run_code endpoint; the documented OSWorld setup uses Volcengine cloud VMs.
How do you use this agent?
Before DemyAgent cold-start SFT, set absolute TRAIN_DATA, EVAL_DATA, MODEL_PATH, and SAVE_PATH values in recipe/demystify/qwen3_4b_sft.sh or qwen2_7b_sft.sh, then run:
bash recipe/demystify/qwen3_4b_sft.shAfter configuring the SandboxFusion endpoint, RL data, model, benchmark paths, and default_local_dir, run:
bash recipe/demystify/grpo_tcr_qwen3_4b.shFor RLAnything, the first training invocation depends on the scenario; for example:
python osworld_rl.py config=configs/osworld_rl.yamlFor a single-node run, set num_node to 1 in the corresponding YAML configuration.
What are this agent's strengths and limitations?
- Covers agentic reasoning, GUI computer control, text-game environments, coding, and dynamic tool selection in one repository rather than a single benchmark recipe.
- DemyAgent documents an end-to-end path from cold-start SFT through GRPO-TCR, including named datasets, model checkpoints, scripts, and configuration fields.
- RLAnything explicitly combines policy, reward-model, and environment adaptation in a closed loop, with separate training and evaluation entry points for OSWorld, AlfWorld, and coding.
- AutoTool specifies a two-phase approach with KL-regularized Plackett–Luce ranking for multi-step dynamic tool selection.
- It is not a plug-and-play inference product: adopters must provide models,
.parquetdata, absolute paths, and scenario configuration. - Code-execution training depends on SandboxFusion or a Volcano Engine Cloud FaaS endpoint, with endpoint changes required in both tool configuration and reward-scoring code.
- The documented OSWorld experiment depends on Volcengine security groups, VM images, and a parallel cloud VM pool; infrastructure costs are not stated.
- AutoTool provides only an example format for its 200K tool-use trajectories; the full training data and toolset are described as coming soon.
How does this agent compare with similar options?
The repository states that its implementation builds on VeRL and ReTool. The supplied material does not provide a feature-by-feature comparison with either project.
Key facts side by side with the most closely related agents.
| Agent | Source review | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|
| Open-AgentRL This agent | 28 · Major gaps | ★ 641 | 3mo ago | Python | — |
| Relax Omni-Modal RL Engine | 64 · Some gaps | ★ 621 | 6d ago | Python | — |
| ART Agent Reinforcement Trainer | 34 · Major gaps | ★ 11k | today | Python | — |
| veRL Agent Training | 32 · Major gaps | ★ 2.3k | 3mo ago | Python | — |
How does FollowAgents rate this agent?
Why each dimension lost points
The evidence shows no mechanisms for permission management, user confirmation, data flow transparency, sensitive data handling, dependency security, external effects, rollback, or source attribution. The README mentions SandboxFusion and cloud services that may involve external execution, but no permission controls or user confirmation are described. Therefore, all trust criteria score 0.
Self-consistency: The README is consistent across sections (DemyAgent, RLAnything, AutoTool), but there are inconsistencies such as the RLAnything paper number 2602.02488 which looks like a future date, and the ICML 2026 acceptance claim is unverifiable. Dependency availability: requirements.txt lists dependencies but without pinned versions and no lock file, so dependency availability scores 1. Failure messages: No documentation of error handling or failure messages, so scores 0.
Audience and scenarios: The README clearly targets researchers and provides multiple training and evaluation scenarios (e.g., OSWorld, AlfWorld, coding), scoring 2. Capability boundaries: No explicit limitations or boundaries of the framework, scoring 1. Trigger precision: Specific commands and configurations are provided, but no trigger conditions or prerequisites, scoring 1. Environment fit: Installation instructions are provided, but no details on hardware or cloud dependencies, scoring 1.
Information architecture: The README is well-structured with navigation and sections, scoring 2. Install notes: Installation commands are provided, but no detailed dependency installation steps, scoring 2. Naming stability: Project and module names are consistent, but no naming conventions, scoring 1. Examples and FAQ: Training and evaluation examples are provided, but no FAQ, scoring 2. Known limitations: No known limitations are mentioned, scoring 0. License: Apache-2.0 license is provided, scoring 2. Versioning and changelog: Update log exists, but no version numbers or changelog file, scoring 1. Maintenance responsibility: No maintainers or contribution guidelines, scoring 1.
Output usability: Models and datasets are provided, but no output format or usage examples, scoring 1. Marginal value: Multiple innovative methods (e.g., RLAnything, AutoTool) are provided, but no detailed comparison with existing methods, scoring 2. Cost-benefit: No training costs or resource requirements, scoring 1.
Claim traceability: Paper and model links are provided, but no detailed reproduction steps, scoring 1. Cross-source corroboration: Multiple external links (e.g., arXiv, Hugging Face) are provided, but no independent verification, scoring 1. Fact-inference separation: The README mixes facts and inferences without clear distinction, scoring 1.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Not found in source: verifiable attributionInstall from the official repo or registry and check the publisher and URL to avoid look-alike packages.
- The repository provides no security mechanisms such as permission controls, user confirmation, or data flow transparency; assess risks before use.
- Dependencies are not pinned and no lock file is provided, which may lead to environment inconsistency or security vulnerabilities.
- Claims of ICML 2026 acceptance and paper numbers may be unverifiable; treat with caution.
- No known limitations are mentioned, which may hide potential issues.
FAQ
Can I deploy this directly as an online agent service?
What external access is needed for code-execution training?
/run_code API endpoint, configured in the specified files.Can OSWorld run on one node?
num_node to 1 in configs/osworld_rl.yaml; its reported experiments use parallel cloud VMs.