Design a part, slice it and print it on an Ender 3 V2, with Claude Code driving each step. The name comes from PETG, which strings along behind the nozzle whenever it gets the chance.
| Folder | What it is |
|---|---|
tramline/ |
A small Go print server for a Raspberry Pi. It switches the printer's plug, preheats, checks the bed's tram, and prints from the SD card or by streaming from the Pi. |
cura/ |
The tuned PETG profile, start G-code and scripts that slice STLs with Cura's engine from the command line. |
.claude/skills/ |
Claude Code skills for this project: solidcraft-design, cura-slicing and tramline. |
Prebuilt binaries from the latest release. The Pi runs the server from the same program that other computers use as the client:
- Linux arm64, for the Raspberry Pi
- Linux x86_64
- macOS arm64
- SHA256SUMS
Check the download and make it executable before installing it as tramline on your PATH, for example on a Mac:
shasum -a 256 -c --ignore-missing SHA256SUMS
chmod +x tramline-darwin-arm64
mv tramline-darwin-arm64 ~/.local/bin/tramlineOn Linux, use sha256sum instead of shasum -a 256. The binaries aren't signed, so on a Mac, a copy downloaded in a browser also needs xattr -d com.apple.quarantine ~/.local/bin/tramline before it will run. Building it yourself with just tramline/install works too, see Tramline, for printing.
-
Design in SolidCraft, a parametric CAD app, through its MCP server. Each design lives in
projects/<name>/. -
Slice the STL:
cd projects/<name> bash ../../cura/slice_petg.sh part.stl
This writes
part_PETG.gcodenext to the STL. -
Print with Tramline. It turns the printer on, always checks tram first, needs your confirmation that the bed is clear, and turns the printer off afterwards. See Tramline's README for printing from the card instead:
tramline upload part_PETG.gcode tramline print part_PETG.gcode --from pi --bed-clear
tramlineis the client thatjust installputs on the PATH, see Tramline, for printing.
These stay on the local machine, see .gitignore:
- The SolidCraft binaries on Linux (
solidcraft,solidcraft-cli,solvecraft-cli). On a Mac, SolidCraft is an app in/Applications. projects/, the designs, STLs and G-code.tramline/dist/,tramline/.cache/andtramline/test-logs/. Tramline's engineering notes refer to files intest-logs/, and those only exist locally.
Tramline's keys stay out too, in ~/.config/tramline/ on the client and /var/lib/tramline/ on the Pi. See Setting up a new computer for how to replace what's missing.
Claude Code picks up the skills by itself when started in this folder, but they rely on things git doesn't carry. Run these from the repository root. It works on Linux and macOS, and the steps say where they differ.
git clone git@github.com:Moudoux/stringing-along.git
cd stringing-along-
Install it:
- macOS: install the SolidCraft app in
/Applications. - Linux: copy the binaries
solidcraft,solidcraft-cliandsolvecraft-cliinto the repository root from a computer that has them.
- macOS: install the SolidCraft app in
-
Connect it to Claude Code:
# macOS claude mcp add solidcraft -- /Applications/SolidCraft.app/Contents/MacOS/solidcraft-cli mcp # Linux claude mcp add solidcraft -- "$PWD/solidcraft-cli" mcp
-
Copy
projects/across too, if you want the existing designs.
Install Cura 5.13, as the scripts run the engine inside it and expect it in one place. These are the only paths that aren't relative:
- macOS:
/Applications/UltiMaker Cura.app, the usual place. SetCURA_APPif it's somewhere else. Cura has no command of its own to put on the PATH, and doesn't need one. - Linux:
/opt/ultimaker-cura.
Older versions aren't safe to assume: 5.7.2 heats the nozzle to 235 C before the start G-code runs, so PETG oozes while probing. You also need Python 3 and bash.
The server is already on the Pi, so a new computer only needs a client. It must be on the same network as the Pi, and needs Docker and just to build.
-
Build the client and install it as
tramlinein~/.local/bin. This runstramline/build.sh, which builds in Docker and needs no Go on the host:just tramline/install
Set
TRAMLINE_BINDIRto install somewhere else.~/.local/binhas to be on your PATH. Ubuntu and Fedora add it by default, but macOS and Arch don't, so addexport PATH="$HOME/.local/bin:$PATH"to~/.zshrcor~/.bashrcthere. Run it again after pulling changes. -
Create this computer's key, in
~/.config/tramline/on Linux and macOS alike. It stays on this computer, and the command prints only the public fingerprint:tramline keygen
-
On the Pi, get the server's fingerprint and allow the new client:
sudo -u tramline tramline fingerprint sudo -u tramline tramline allow <client-fingerprint> --name <computer-name>
-
Back on the new computer, log in and check it works:
tramline login https://raspberrypi:8726 <server-fingerprint> tramline status
-
Add an SSH host called
raspberrypito~/.ssh/config, using userpi. Saving logs anddeploy/install.shboth use it. The client itself doesn't need SSH.
These stay on the original computer, in ~/.claude/:
- Global rules:
~/.claude/CLAUDE.mdholds the rules on never reading secrets, never running sudo, and handing off to a new session. Thetramlineskill repeats the first two, but only while that skill is in use, so copy the file across to keep them in every session. - Memory: Claude's notes aren't copied, so it starts without them. The READMEs and skills hold most of what matters.
This is only needed if the Pi itself is replaced. See Security, Install and updates, Config and the test plan in Tramline's engineering notes. In short: deploy/install.sh <ssh-host>, tramline init --ip <address> and tramline hue pair on the Pi, then fill in /etc/tramline/config.json with the plug's UUID from tramline hue plugs. These need sudo on the Pi, and the printer needs the USB cable with its +5V wire cut, see The USB cable in that README.
Tramline's stage 10 passed on the real printer on 2026-11-04, including a 63-minute streamed print. See the status table at the top of Tramline's engineering notes for what's proven on the printer and what has only run on the simulator.