Clarify OpenClaw SimRL prompt availability - #6
Open
MayVerse4 wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Hi maintainers! This PR addresses Issue #2, a documentation/support request asking for the official SimRL prompt for OpenClaw in this model.
I checked the repository sources of truth and did not find an OpenClaw-specific SimRL prompt or OpenClaw task configuration. The only prompt/config sources shipped in this repo are the seven AgentWorldBench domain prompt templates under
prompts/and their paths ineval/lwm_eval_utils/task_configs.py. To avoid presenting an unverified generic prompt as official, I updated the README to state that clearly.I also added the expected user-message template for OpenClaw/SimRL-style usage, following the repository’s AgentWorldBench message contract (
system_stras the system prompt, user content containing task/context/current state/action, and<predicted_observation>for the model output). I also fixed the encoding issue from the prior draft and removed the public “think step by step” wording.This is a documentation-only change, so I did not run tests. Happy to adjust the wording if you have an external OpenClaw prompt/config you’d like linked or pasted verbatim.
Fixes #2