Build 3D worlds for dimos's MuJoCo sim (sim2), export them, drop a robot in.
# 1. dimOS Desktop (Mac or Linux)
curl -fsSL https://raw.githubusercontent.com/jeff-hykin/dimos-desktop-mirror/main/install.sh | bash
# 2. World Builder, as a Desktop app
dimos-desktop install github.com/dimensionalOS/dim-world-builder --ref mainuv pip install -e ~/dimos_worlds/<world> # into dimos's venv
dimos run <world>.go2 --simulation mujoco --transport zenoh # a Go2 in it + SceneData
dimos run <blueprint> <world>.scene-data --scene-package ~/dimos_worlds/<world> # SceneData beside any sim2 blueprintExport: scene.xml, scene.json (sim2: movers; annotations: labeled points, paths, areas, e.g.
the nav test; views + project in extensions), world.py / blueprints.py / scene_data.py (a
namespace package), meshes/, textures/. Python:
from <world> import world; world.render_view("overview"). SceneData answers
/scene_data_request on /scene_data (meshes, lights, cameras) and announces itself on
/scene_info; the Controller draws it as the
"Simulated world" layer. Needs dimos branch jeff/feat/sim2_world_builder.
python verify/nav_eval.py ~/dimos_worlds/<world> --blueprint unitree-go2-freewalk # walks the nav:mapping path, then nav:goal points
python verify/drive_go2.py examples/nav_test_course # walls, crates, cart, stairs collideAgents: every action is an endpoint (dimos.yaml); deno run -A tools/dwb.ts --help is the CLI.
dwb check reports clipping (edits, generate and export return the same warnings). Example built
that way: tools/examples/office_555.ts.
Reference photos: POST api/images (a JPEG/PNG body) returns { id, src }; an item of kind image
(params: { src, width, height, opacity?, doubleSided? }) shows it on a plane in the item's local
y-z, centered on its position, facing +x. It is visual only: no collision, not in the clip check,
left out of the export. GET api/selection is what the user has selected in the page used last.
Working on a world with an agent: changes made through the API
(POST/PATCH/DELETE api/project/items, POST api/project, POST api/project/undo, ...) show
up live in the open pages, keeping their view and selection; a page with unsaved edits keeps them
and asks before loading the new version. GET|POST api/camera reads or moves the user's view,
POST api/highlight blinks items, GET api/project/history lists a world's last 50 versions. Items
can carry notes.
deno run -A backend/main.ts --port 8797 & API_PORT=8797 deno task dev
deno task test && deno task check && dimos-desktop app check .
deno task update-hashes # after changing deno.json or deno.lock: flake.nix's hashes for the page












