Adding ROS simulation assets

.github/workflows/ci.yml

@@ -11,10 +11,12 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.11", "3.12", "3.13"]
+        python-version: ["3.12", "3.13"]
 
     steps:
     - uses: actions/checkout@v4
+      with:
+        submodules: recursive
 
     - name: Set up Python ${{ matrix.python-version }}
       uses: actions/setup-python@v5

.gitignore

@@ -22,8 +22,22 @@ poetry.lock
 botpy.log
 nano.*.save
 .DS_Store
-uv.lock
 package-lock.json
 node_modules/
 .claude/scheduled_tasks.lock
 .claude/worktrees/
+.codex/
+
+# ROS workspace build artifacts
+robotics
+# robotics/ros_ws/build/
+# robotics/ros_ws/install/
+# robotics/ros_ws/log/
+
+# Local simulation planning docs
+docs/simulation-agent-workflow.md
+docs/simulation-development-flow.md
+
+# Local robotics docs
+robotics/README.md
+robotics/README.general.md

.python-version

@@ -0,0 +1 @@
+3.12

AGENTS.md

@@ -0,0 +1,24 @@
+# RoboClaw Agent 开发指南
+
+运用第一性原理思考，拒绝经验主义和路径盲从，不要假设我完全清楚目标，保持审慎，从原始需求和问题出发，若目标模糊请停下和我讨论，若目标清晰但路径非最优，请直接建议更短、更低成本的办法。
+
+---
+
+## 工作规范
+
+### 架构原则
+
+- 对象优先：所有功能从对象建模出发——先识别实体与职责边界，再设计对象间的协作关系。
+- 物理文件组织必须直接反映逻辑架构。目录名、文件名、包结构要让人一眼看出模块职责和层级关系。如果架构调整了，文件结构必须同步调整。
+
+### 代码规范
+
+- 框架代码放 `roboclaw/embodied/`，用户资产放 `~/.roboclaw/workspace/embodied/`。
+- 不写向后兼容代码。不保留旧接口、不做 fallback 适配、不写 deprecated wrapper。旧的不要了就直接删掉。
+- 不用 try/except 吞错误。有报错就让它直接抛出来，不要静默捕获。只在确实需要处理特定异常时才 catch。
+- 复用优先。已有实现的功能不要重复造轮子，先找现有代码再决定是否新写。
+- 单个 .py 文件不超过 1000 行。超过时必须将独立逻辑拆分到单独的模块。
+- 嵌套不超过 3 层缩进。超过时应将内层逻辑提取为独立函数。
+
+
+---

CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md

README.md

@@ -42,6 +42,7 @@
 
 ## 📢 News
 
+- **2026-04-11** Web dashboard for the full embodied workflow.
 - **2026-03-24** Conversational arm setup, calibration, teleoperation, data collection, training, and inference.
 - **2026-03-17** Embodied framework skeleton, domain contracts, and assembly-centered onboarding controller.
 - **2026-03-12** Repository created.

docs/DOCKERINSTALLATION.md

@@ -9,7 +9,7 @@ If you do not want Docker, use [INSTALLATION.md](./INSTALLATION.md).
 Start from a clean clone:
 
 ```bash
-git clone https://github.com/MINT-SJTU/RoboClaw.git
+git clone --recurse-submodules https://github.com/MINT-SJTU/RoboClaw.git
 cd RoboClaw
 ```
 

docs/INSTALLATION.md

@@ -1,42 +1,64 @@
 # RoboClaw Installation Guide
 
-This guide is the native host installation path. If you want Docker-based workflows, use:
+This guide is the native host installation path. RoboClaw uses `uv` as the only supported Python environment and dependency workflow. If you want Docker-based workflows, use:
 
 - [Docker Installation](./DOCKERINSTALLATION.md)
 
-## 1. Prerequisites
+## 1. Install uv
 
-Start from a clean clone:
+Install `uv` with the official installer:
 
 ```bash
-git clone https://github.com/MINT-SJTU/RoboClaw.git
+curl -LsSf https://astral.sh/uv/install.sh | sh
+```
+
+Verify that `uv` is available:
+
+```bash
+uv --version
+```
+
+## 2. Clone RoboClaw
+
+Start from a clean clone and fetch submodules:
+
+```bash
+git clone --recurse-submodules https://github.com/MINT-SJTU/RoboClaw.git
 cd RoboClaw
 ```
 
-## 2. Install RoboClaw
+The embodied engine lives in `roboclaw/embodied/engine` as a git submodule and is required during installation.
 
-Install the package in editable mode:
+If you already cloned the repository without submodules, run:
 
 ```bash
-pip install -e ".[dev]"
+git submodule update --init --recursive
 ```
 
-After installation, the `roboclaw` command should be available:
+## 3. Sync the Project with uv
+
+RoboClaw pins Python with `.python-version` and uses `uv sync` to create `.venv` and install all default development dependencies:
 
 ```bash
-roboclaw --help
+uv sync
+```
+
+After sync, verify that the `roboclaw` command is available:
+
+```bash
+uv run roboclaw --help
 ```
 
 Expected result:
 
 - commands such as `onboard`, `status`, `agent`, and `provider` are listed
 
-## 3. Initialize RoboClaw
+## 4. Initialize RoboClaw
 
 Run:
 
 ```bash
-roboclaw onboard
+uv run roboclaw onboard
 ```
 
 This should create `~/.roboclaw/config.json`, `~/.roboclaw/workspace/`, and the initial workspace scaffold. You can verify it with:
@@ -57,12 +79,12 @@ You should see at least:
 ~/.roboclaw/workspace/memory/MEMORY.md
 ```
 
-## 4. Verify Status Output
+## 5. Verify Status Output
 
 Run:
 
 ```bash
-roboclaw status
+uv run roboclaw status
 ```
 
 Check that:
@@ -72,14 +94,14 @@ Check that:
 - the current `Model` looks correct
 - provider status matches the actual state of your machine
 
-## 5. Configure the Model Provider
+## 6. Configure the Model Provider
 
 Before testing `roboclaw agent`, make sure the model provider is configured.
 
 First run:
 
 ```bash
-roboclaw status
+uv run roboclaw status
 ```
 
 This tells you which providers are already available on the current machine.
@@ -93,8 +115,8 @@ If you are using an OAuth-based provider, log in directly.
 The current codebase supports:
 
 ```bash
-roboclaw provider login openai-codex
-roboclaw provider login github-copilot
+uv run roboclaw provider login openai-codex
+uv run roboclaw provider login github-copilot
 ```
 
 ### 5.2 API key provider
@@ -127,20 +149,20 @@ Common API key providers include:
 Then run:
 
 ```bash
-roboclaw status
+uv run roboclaw status
 ```
 
 Check that:
 
 - the current `Model` is correct
 - the provider you want to use is no longer `not set`
 
-## 6. Verify the Basic Model Path
+## 7. Verify the Basic Model Path
 
 Run one minimal message to confirm that RoboClaw can respond:
 
 ```bash
-roboclaw agent -m "hello"
+uv run roboclaw agent -m "hello"
 ```
 
 Check that:
@@ -149,18 +171,10 @@ Check that:
 - the agent returns a normal reply
 - failures point clearly to model configuration, provider setup, network, or permissions
 
-## 7. Launch the Web Dashboard
+## 8. Launch the Web Dashboard
 
 The web dashboard provides a browser-based UI for chatting with RoboClaw.
 
-### Prerequisites
-
-Install the web optional dependency (if not already included in `.[dev]`):
-
-```bash
-pip install -e ".[web]"
-```
-
 Install the frontend dependencies:
 
 ```bash
@@ -174,7 +188,7 @@ Build the frontend and start the server:
 
 ```bash
 cd ui && npm run build && cd ..
-roboclaw web start
+uv run roboclaw web start
 ```
 
 Open **http://127.0.0.1:8765** in your browser.
@@ -183,7 +197,7 @@ Open **http://127.0.0.1:8765** in your browser.
 
 ```bash
 # Terminal 1: start backend
-roboclaw web start
+uv run roboclaw web start
 
 # Terminal 2: start frontend dev server
 cd ui
@@ -195,7 +209,7 @@ Open **http://localhost:5173** in your browser. The Vite dev server proxies `/ap
 ### Options
 
 ```bash
-roboclaw web start --host 0.0.0.0 --port 9000
+uv run roboclaw web start --host 0.0.0.0 --port 9000
 ```
 
 | Flag          | Default       | Description                |