By late afternoon the gripper should already be flying the room, pinching a sock, and dropping it in a tagged hamper – gamepad or the stock laundry routine. That end state is why Stringman (Neufangled’s open-source room-scale cable gripper, assembled unit still listed around $795 with roughly a 4-week lead as of the current store page) is the hardware thread people keep forwarding from Hacker News.
I matched the official install guide against HN and Discord failure modes so the Wi-Fi and mounting traps show up before you are on a ladder with three lines in your face.
Assembled path first (the $795 unit vs the kit)
Two SKUs, one clear winner if you want motion this month:
- Assembled (~$795, ~4-week lead as of the store page) – anchors, eyelets, gripper/marker arrive built. Mount, QR Wi-Fi, full cal. About an hour of ladder work plus ~5 minutes hands-off calibration.
- Hardware kit (~$655 listed) – you print structure (PET-GF is the strength pick), build anchors/gripper, flash Pis. Multi-day. Soldering-seal connectors. Real maker time.
Most buyers who want it running this week take assembled. This guide is that path only. Printing still uses the same host stack and stud rules – just add days.
Hanging a curtain rod is the right difficulty metaphor. Drill, checklist, do not improvise ceiling attachments.
What you are actually hanging
Payload first, marketing second: 2.2 kg near the floor, about 1.9 kg average across a 7×7×3 m volume at the 28 N tension cap, after subtracting the 638 g gripper – those numbers sit on Neufangled’s specs. Work envelope is rooms with a 3-10 m XY diagonal and ceiling heights 2.3-4 m; traverse sits near 0.4 m/s. Two anchor cams at 1920×1080@30fps plus a gripper wide-FOV stream at 684×384@60fps.
Mechanically it is a cable-driven parallel setup: powered anchors in two opposite corners, passive eyelets in the others, four braided lines into a marker box with a two-finger wristed gripper. Four actuators cover whole-room volume a desk arm never sees. Price undercuts research arms hard.
Open stack, not vapor: OSHWA US002788, CAD/PCBs/software public, Apache 2.0 on the software side, LeRobot-native, MCP extra for agents, air-gapped LAN mode. Host PC does the brains (Linux/Mac preferred, 6-8+ cores; GPU/NPU if you run local models). Hanging compute is Pi Zero 2W on the gripper and Pi 3A+ class on anchors. Host side is pip install "nf_robot[host]" then stringman-headless per PyPI nf-robot.
Stock behavior is laundry-to-tagged-hamper. Other tasks you collect.
Install walkthrough (assembled)
Tools: step ladder, drill/driver, the hex/T20 bits in the box. Follow the official arp_install_guide – the gotchas below are the ones that actually strand people.
1. Work volume and mounts
Powered anchors on one diagonal; eyelets on the other. That quadrilateral is the workspace. Ceiling fan in the room? Keep mounts at or below blade height so lines cannot eat the fan. Bunk beds can live inside the volume; there is still no smart obstacle avoidance – you babysit those paths.
Studs or structural columns only. Lateral load is not theoretical. No adhesive, no magnets, no drop-ceiling T-bars (they bend; calibration and swing-cancel die with them). Parking hook on a stud near an anchor: high enough to walk under, not so high that precision falls apart near the ceiling.
2. Floor power, Wi-Fi, host
Pull lines down. Power and join Wi-Fi on the floor before you commit the gripper to the air. After boot, components hunt a QR share for about 10 seconds. iPhone codes behave. Android decorative QRs only work if they fill the whole frame – use a blocky code from qifi.org instead. Hold each camera (gripper included) ~10 seconds until a motor buzz or finger wiggle.
Guest Wi-Fi and AP/client isolation block discovery. Anchors, gripper, and host need the same full LAN. Only one full Stringman on that LAN during first discovery.
Pro tip: Barrel jack into the anchors before AC via the outlet remote. Reverse order can permanently damage anchors. That warning is straight from the install guide – not folklore.
python3 -m venv venv
source venv/bin/activate # Windows: use your venv activate path
pip install "nf_robot[host]"
stringman-headless
UI: http://localhost:8090/?robotid=lan (Playroom relay is optional later). You want two anchors + one gripper. Run firmware update and timezone sync from Calibration. Community reports of multi-hour clock skew are ugly because swing cancel does not just fail – it can amplify. Sync first.
3. Lines, tension, full calibration
Power off. Gripper in room center. Black carabiners: anchors → black bar. Silver: eyelets → white marker corners. No crosses. Gray power tether into the gripper. Power on, tension (D-pad left or key 2), tap E briefly to lift.
Print origin + helpers 1-3 at 100% scale, no margins. Origin at floor center. Full Calibration moves the robot; lines may go slack on purpose while it hunts eyelets. Card shifts? Abort and restart. Finished UI room shape should match the real room; WASD straights should look straight. Enable swing cancel and confirm damping – not growth.
Drive into the parking hook, save Parking, then unpark/park once before you trust it.
4. First useful motion (and the AI hooks)
Clip a fiducial on the hamper – or any bin. Models treat the tag label as the destination. Gamepad teleop is the sane data path (common picks are a DualShock-class pad on Mac or a Logitech-class pad on Linux). A few dozen pick episodes in the UI is enough for some DiT-style behaviors to start (~50 is the figure Neufangled-style notes float). Or fire the default laundry routine and watch.
Agents: MCP extra plus the Python telemetry websocket let you send velocities or higher-level episode commands without writing IK. Details live in the nf-robot docs and public firmware repos – not in a second kinematics stack you maintain.
After the honeymoon
Lighting has to stay bright and stable; dim corners break marker detect and parking. Raise speed, fly higher, or drop the 28 N tension limit for a softer release, and usable payload shrinks – those 2.2 / ~1.9 kg figures are not free at every height. Two-finger + wrist loves socks and soft toys; flat books and cable tangles still fight it.
Lines stay up (parked high, thin) unless you carabiner-disconnect. Self-park failing usually means re-record under better light or redo room cal with cards spread farther. Host wants real cores; add NPU/GPU if models run local. Macs are fine for acceleration.
Some afternoons the cal cards will not stay put and you will redo the run while muttering. That is normal cable-robot life, not a unique Stringman curse – the room geometry has to be true or every later policy looks drunk.
Early platform energy is real. Nathaniel Nifong (Neufangled) shows up on Discord; the recent HN thread sat around 401 points with active creator replies. Expect pulls, model tweaks, and the occasional “update firmware and try again.”
FAQ
Is the assembled Stringman beginner-friendly?
Mounting and first cal: yes, if you can drill studs and follow a checklist. New skills and vision debug: you need a terminal and a gamepad. One chore works out of the box. It is not a finished Roomba.
Can I run it fully offline?
Yes. Default stringman-headless is LAN-only – UI and models stay local. Optional free Playroom relay is remote access you can revoke. Neufangled’s stated position: they do not store your video on the relay path. If the lab network is locked down, skip guest SSID tricks; put host + robot on one ordinary LAN segment and leave the relay off.
What if someone walks into a line or grabs the gripper?
At 28 N (backpack-ish) motors release with damping so a person can pull free. Wireless hardware E-stop rides the outlet remote. Overhead parking keeps lines mostly out of head space. The misconception: “it will notice people.” It will not – no intelligent person detection yet – so kids, pets, and party guests still need a human in the loop.
Order assembled from neufangled.com, print the cal cards before the box lands, join Discord early. First tagged-hamper drop is when the HN demo stops being a clip and starts being furniture that moves.