Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Make arm run here #2
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
This runs the SO-101 arm server, from trevato's workbench branch, as the forge app, on its simulated servo bus. main has no runnable code (it's CAD files, URDFs and guides), so this branch starts from origin/workbench (bd7c03c).
shipped merged
This runs the SO-101 arm server, from trevato's workbench branch, as the forge app, on its simulated servo bus. main has no runnable code (it's CAD files, URDFs and guides), so this branch starts from origin/workbench (bd7c03c). That means this pull includes the four unmerged workbench commits (servo driver, CLI, arm server and browser app, ArUco kit, Nix shell). Merging it lands workbench too.
What changed on top of workbench (one commit, b0418ce):
forge.json— install withbun install --cwd Software/so101 --frozen-lockfile, runbun run Software/so101/bench/fake-serve.ts, test withbun --cwd Software/so101 test. The health path is/status.Software/so101/bench/fake-serve.ts— readsPORTandHOST, and keeps poses, recordings, settings and metrics in$FORGE_APP_DATA/so101. Without those variables it behaves as before: port 8102, bound to 127.0.0.1, data in a temp dir.Software/so101/src/fake-serve.test.ts— starts the script the way the forge does, then checks/statusanswers and that a saved pose lands underFORGE_APP_DATA. It fails without the change.Software/README.md— one paragraph on how it runs here.
The routes, the page and the server code are unchanged. Locally, all 92 tests pass and tsc --noEmit is clean. The server starts on an empty data dir, /status and / answered in under 40 ms, and saved poses survived a restart.
What could not fit:
- No real arm. The server talks to Feetech servos over a USB serial board, and a forge process has none. The preview is the repository's own simulator (
fake-serve): every move arrives instantly, and load and temperature read 0. Driving a real arm still means runningso101 serveon the machine the arm is plugged into, under Node. - No cameras. The page expects MJPEG streams on ports 8080 and 8081 of the same host, and nothing serves those here, so the camera panes stay empty.
?stream=<url>still points the first pane at a stream. - No authentication, and no same-origin check on mutations. I kept the original behaviour; its README says to keep it on a LAN. Anyone who can reach the preview can change the simulated arm's poses and settings.
- The Python vision kit, the Nix shell and the
justrecipes need a camera or hardware, so they don't run here.
To try it, open the preview: / shows the 3D arm. Drag a joint or use the jog sliders, save a pose, restart the app, and the pose is still listed.
🤖 Generated with Claude Code
This pull runs the SO-101 arm server from trevato's workbench branch as this repository's app, using its simulated servo bus. The branch was already cut from origin/workbench (bd7c03c) and adds one commit, b0418ce, on top, so it already follows the steward's note. No upstream CAD, STL, URDF or docs files are touched.
Base branch: The forge opened this pull against main, and retargeting it is a repository setting agents cannot change. Measured against main, it shows the four workbench commits plus mine; against workbench it is only b0418ce. I recommend making workbench the default branch, since main has no runnable code and production should follow the app. Retargeting this pull to workbench would also work.
What b0418ce changes:
forge.json(new): installs withbun install --cwd Software/so101 --frozen-lockfile, runsbun run Software/so101/bench/fake-serve.ts, tests withbun --cwd Software/so101 test, and uses/statusas the health check.Software/so101/bench/fake-serve.ts: readsPORTandHOST, and keeps poses, recordings, settings and metrics in$FORGE_APP_DATA/so101. Without those variables it behaves as before: port 8102, bound to 127.0.0.1, data in a temp dir.Software/so101/src/fake-serve.test.ts(new): starts the script the way the forge does, checks that/statusanswers, and checks that a saved pose lands underFORGE_APP_DATA. It fails without the change.Software/README.md: one paragraph on running the app here and locally.
The routes, the page and the server code are unchanged from workbench. All 92 tests pass and tsc --noEmit is clean.
What I chose not to do:
- No real arm. The server drives Feetech servos over a USB serial board, and a forge process has none. The preview runs the repository's simulator, so every move arrives at once and load and temperature read 0. Driving the physical arm still means running
so101 serveon the machine it is plugged into. - No cameras. The page expects MJPEG streams on ports 8080 and 8081, so the camera panes stay empty.
?stream=<url>still points the first pane at a stream. - No authentication and no same-origin check on changes. I kept the original behaviour, which the README says is for a LAN. Anyone who can reach the preview can change the simulated arm's poses and settings; that needs its own issue.
- The Python vision kit, the Nix shell and the
justrecipes need hardware or a camera, so they don't run here.
To try it: open the preview, and / shows the 3D arm. Drag a joint or use the jog sliders, save a pose, restart the app, and the pose is still listed.
🤖 Generated with Claude Code
Closes #1
This runs the SO-101 arm server, from trevato's
workbenchbranch, as the forge app, on its simulated servo bus.mainhas no runnable code (it's CAD files, URDFs and guides), so this branch starts fromorigin/workbench(bd7c03c). That means this pull includes the four unmergedworkbenchcommits (servo driver, CLI, arm server and browser app, ArUco kit, Nix shell). Merging it landsworkbenchtoo.What changed on top of
workbench(one commit, b0418ce):forge.json— install withbun install --cwd Software/so101 --frozen-lockfile, runbun run Software/so101/bench/fake-serve.ts, test withbun --cwd Software/so101 test. The health path is/status.Software/so101/bench/fake-serve.ts— readsPORTandHOST, and keeps poses, recordings, settings and metrics in$FORGE_APP_DATA/so101. Without those variables it behaves as before: port 8102, bound to 127.0.0.1, data in a temp dir.Software/so101/src/fake-serve.test.ts— starts the script the way the forge does, then checks/statusanswers and that a saved pose lands underFORGE_APP_DATA. It fails without the change.Software/README.md— one paragraph on how it runs here.The routes, the page and the server code are unchanged. Locally, all 92 tests pass and
tsc --noEmitis clean. The server starts on an empty data dir,/statusand/answered in under 40 ms, and saved poses survived a restart.What could not fit:
fake-serve): every move arrives instantly, and load and temperature read 0. Driving a real arm still means runningso101 serveon the machine the arm is plugged into, under Node.?stream=<url>still points the first pane at a stream.justrecipes need a camera or hardware, so they don't run here.To try it, open the preview:
/shows the 3D arm. Drag a joint or use the jog sliders, save a pose, restart the app, and the pose is still listed.🤖 Generated with Claude Code
Closes #1