← All use cases

Use case P52 · Human

3D-printer owner uses Claude to build a checklist showing which filament color to load next

Christian Fredrik Kalager Schaller ·

The short version

What they did

Christian Fredrik Kalager Schaller wanted to print multiple colors on his single-extruder Prusa Core One without losing track of fifteen manual filament changes. He worked with Claude to build Prusa Color Mate, which reads the print instructions and presents the color changes as a checklist. The first attempt read the wrong file type and produced the wrong order; he supplied documentation and source code until it worked with the actual printer file. He tested it with his own print and explicitly says he had not tested other printers.

Result (as claimed)

“So know I had the working application going and was able to verify it with my first print.”

“It solves my issue the way it is today, but if there turns out to be an interested user community out there maybe I will try to clean it up and create a proper flatpak for it.”

Prompt

I’m using Claude Code to build a local checklist for manual filament changes on my [printer model]. I’ll provide [sample sliced print file] and [file-format documentation].

1. Identify which file and commands record the actual change order. Do not use the model’s available-color list as the printing sequence.
2. Extract each change into a table showing order, layer or height and color when recorded. Ask me to label colors the file does not identify.
3. Build a simple screen showing the next change and a box I can tick when it is done.

Explain the setup in plain words. Compare the extracted order with [slicer preview or short test print] and report mismatches. Flag unsupported formats instead of guessing. Do not claim support for printers or file types we have not tested.

Do it yourself

These steps are my suggested way in, not Christian’s setup.

Level: Advanced to build the app. A printed checklist from a chat is Intermediate.

What you need

  • A single-extruder 3D printer and a slicer that can insert color changes, such as PrusaSlicer.
  • A chat assistant that can read files, such as Claude or ChatGPT.
  • For the app, a coding agent such as Claude Code.

Start simple

  1. Slice a small two- or three-color model with color changes at set layers.
  2. Export the plain-text G-code and upload it, or a part of it, to the chat.
  3. Ask it to find every color change command and list the layer, height and color.
  4. Print that list and tick off each change as the printer pauses.

Take it further

  • Have a coding agent build a small local app that reads your sliced file and shows the checklist.
  • Give it your printer’s file format documentation if it guesses wrong.
  • Add a progress screen that shows which change comes next.

Check your work

  • Compare the list with the color-change markers in your slicer’s preview.
  • Do a short test print before trusting it on a long one.

Source checked. The link, author, date and quote were confirmed against the source. The result itself has not been reproduced. Prompt adapted for this library, inspired by the case. Business size: Individual. Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.

More in Electronics and 3D printing

New cases go out every Saturday in Inside AI.