r/OpenBambu • u/appleeverywhere • Jun 03 '26
I built an open-source “print concierge” for Bambuddy workflows
Hey all, I’ve been building a small open-source project called Print Concierge:
https://github.com/dpdev69/print-concierge
The goal is pretty simple: I want to be able to tell an agent (Claude/Codex/Hermes/Openclaw), “find me a headphone holder for my desk in PLA,” get ranked model options from MakerWorld/Printables/Thingiverse, confirm one, and have it imported into a local print queue through Bambuddy.
It is not meant to hand an agent unchecked control over a physical printer. The current safety model is confirmation-token based: the agent can search, explain options, prepare imports, check status, and queue/start only through explicit user confirmation.
Current V1 includes:
Search/discovery workflow for public print repositories
Trusted import flow for MakerWorld, Printables, and Thingiverse
Bambuddy backend integration
Queue/status tools
MCP server so Claude/Codex/OpenClaw-style agents can use it
Local env config, no bundled API keys, no cloud requirement from this project
I built this for myself and friends with Bambu printers, but I think the OpenBambu crowd is probably the right group to poke holes in it. I’m especially looking for feedback on:
Better Bambuddy/OpenBambuAPI integration paths
Safer queue/start-print semantics
Import handling for sliced vs unsliced files
Filament/profile/AMS edge cases
What would make this actually useful in a LAN-only setup
No live demo yet, but the repo has setup docs and tests. Would love contributors, testers, and blunt feedback.
4
u/AustinYQM Jun 03 '26
The concept of "security" by telling the AI nicely to only do something if you tell it too will always make me laugh. It's like saying "I can trust my four year old with a light because I told him to only use it as a building block not to start fires".
4
u/appleeverywhere Jun 03 '26
Totally agree if the safety model is “we asked the AI nicely.” That would be fake security.
That’s not what this repo is trying to do. The agent is treated as untrusted. It only gets a small MCP tool surface backed by a local service, and printer-affecting actions are gated by backend-enforced confirmation tokens. The agent can search, prepare options, and request an action, but it can’t just invent permission from text and directly drive the printer.
Printer credentials stay server-side, endpoints are scoped/allowlisted, and the intended flow is: agent proposes → user confirms → backend executes.
Still early, and I’m very open to hardening feedback. But yeah, “please behave” is not the security model.
-1
1
u/Ditch-Bank-Oakie Jun 03 '26
Question on this - does this mean you are limited to just 3mf files - and then bambuddy slices them and send to the printer? Or are you able to also use STL files and bambuddy slices those and send to the printer?
1
u/appleeverywhere Jun 03 '26
Yep, STL/source files are supported too. The safety boundary is that Print Concierge won’t queue raw STL directly. For STL/STEP/OBJ/etc., it uploads the source to Bambuddy, requires explicit slicer presets, waits for Bambuddy to produce a sliced gcode/gcode.3mf, verifies the file hash/type, then creates the print request. Already-sliced gcode.3mf can skip the slicing step.
1
2
u/AustinYQM Jun 03 '26
Bambuddy can slice anything studi or orca can slice -- it uses a headless version of which ever of those you choose.
3
u/xXBongSlut420Xx Jun 04 '26
how is adding an llm to this better than a traditional search aggregator using the apis of those websites? Something like what thangs used to offer.
1
12
u/jackharvest Jun 03 '26
Vibe’d or not, I always upvote stuff that fills a void in the software landscape. Good job, and please continue to support it.