[agents, examples] feat: support Claude Code on OpenYuanRong - #170
Open
Mengyuyang wants to merge 1 commit into
Open
[agents, examples] feat: support Claude Code on OpenYuanRong#170Mengyuyang wants to merge 1 commit into
Mengyuyang wants to merge 1 commit into
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Mengyuyang
force-pushed
the
codex/claude-code-openyuanrong-main
branch
from
September 3, 2026 12:13
e6d1b89 to
ecc94b7
Compare
yyDing1
reviewed
Sep 3, 2026
Comment on lines
+70
to
+76
| _OPENYUANRONG_RUNTIME_ENV_KEYS = ( | ||
| "OPENYUANRONG_SERVER_ADDRESS", | ||
| "OPENYUANRONG_TOKEN", | ||
| "OPENYUANRONG_TUNNEL_SSL_VERIFY", | ||
| "USE_OPENYUANRONG_SDK", | ||
| "SANDBOX_NAME_PREFIX", | ||
| ) |
Collaborator
There was a problem hiding this comment.
Do not modify this file; inject these envs into the ray env.
Comment on lines
+69
to
+73
| executable: str = Field( | ||
| default="claude", | ||
| min_length=1, | ||
| description="Claude Code executable name or explicit sidecar path.", | ||
| ) |
Collaborator
There was a problem hiding this comment.
The real execution path should be injected into the env during sandbox start. This file is not expected to modify, too.
| @@ -0,0 +1,34 @@ | |||
| """Helpers for constructing Ray worker runtime environments.""" | |||
Collaborator
There was a problem hiding this comment.
what's the purpose of this file?
Mengyuyang
force-pushed
the
codex/claude-code-openyuanrong-main
branch
2 times, most recently
from
September 7, 2026 03:05
a078d0b to
2af2d18
Compare
Mengyuyang
force-pushed
the
codex/claude-code-openyuanrong-main
branch
from
September 7, 2026 11:00
2af2d18 to
1b3f756
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add an opt-in OpenYuanRong task configuration for running the existing Claude Code agent in SWE-Bench and SWE-ReBench sandboxes. The configuration mounts a prebuilt Claude Code sidecar and uses its explicit CLI path, so OpenYuanRong rollouts do not install or upgrade Claude Code inside each sandbox.
The standalone verl inference runner also propagates resolved editable package roots and the existing OpenYuanRong environment to Ray workers. This prevents driver/worker

vllmimport mismatches before expensive rollout actors are created.Changes
Add
examples/quickstart/training/task_config_claude_code_openyuanrong.yaml.Configure
swe_benchandswe_rebenchwith theopenyuanrongsandbox provider, OpenYuanRong registry image mapping, sidecar mount, tunnel proxy port, rollout timeout, and Claude Code prompt/model defaults.Add optional
agent.executabletoClaudeCodeConfig, defaulting toclaudefor backward compatibility.When
agent.executableis an explicit path such as/opt/claude-code/bin/claude, validate it withtest -xbefore rollout execution.Fail explicitly when the configured sidecar executable is unavailable. The explicit-path mode never falls back to npm or native Claude Code installation.
Keep the existing PATH-based
claudediscovery and installation fallback unchanged when no explicit executable path is configured.Add Ray runtime-environment helpers that resolve physical package roots for
vllm,verl, anduni_agent, then forward them to Ray workers through the firstray.init()call.Forward already configured OpenYuanRong environment variables to nested rollout workers and validate the worker-side engine import before creating the rollout worker group.
Configuration and API