-
Notifications
You must be signed in to change notification settings - Fork 32
feat: implement scene update logic based on predicted action type #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
Collaborator
xiaow190
commented
Jul 30, 2025
- Support model-predicted actions: add_object, remove_object, position
- Parse model output with ... tag
- Dispatch to corresponding handlers (add/remove/position) based on action type
- Update flagscale scene info accordingly
- Fixed import path case issue for `Collaborator` to ensure cross-platform compatibility. - Replaced editable Git dependency with pinned `mcp==1.10.1` for stable installation.
…s API - Replaced stdio-based MCP connection with HTTP-based streamable client using config-defined URL. - Updated `config.yaml` to include MCP server URL under `mcp.URL`. - Refactored `robot_status` endpoint to return structured list of registered robot states. - Removed unused Flask imports and simplified code structure.
…ble and step delay
… subtask dispatching
- Fixed inconsistent indentation in the Docker run command - Added missing container path for the `-v` volume mount - Removed trailing whitespace after `-p 8888:8888` - Improved readability with consistent parameter alignment
…ask-required steps
…ass for better modularity and maintainability
…h scene info - Implemented read_all_environment to fetch and parse all environment data from Redis - Updated MASTER_PLANNING_PLANNING prompt to include scene_info and require task decomposition to consider available objects in the scene
- document required fields in master/slaver config.yaml including model.cloud_server, collaborator, profile, tool, and robot - provide examples for slaver.robot in both local and remote call modes - clarify default values and usage to help users correctly configure RoboOS
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.