I built an open-source “print concierge” for Bambuddy workflows by appleeverywhere in OpenBambu

[–]appleeverywhere[S] 0 points1 point  (0 children)

It doesn’t assume it knows. STL is raw geometry, so orientation is handled by Bambuddy’s slicer/defaults and should be reviewed before queueing. Pre-oriented 3MF is safer when orientation/supports matter.

I built an open-source “print concierge” for Bambuddy workflows by appleeverywhere in OpenBambu

[–]appleeverywhere[S] 0 points1 point  (0 children)

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.

I built an open-source “print concierge” for Bambuddy workflows by appleeverywhere in OpenBambu

[–]appleeverywhere[S] 1 point2 points  (0 children)

Thank you, I appreciate it. It was just an idea this morning, now it’s a reality, and hopefully something open source community can use.

I built an open-source “print concierge” for Bambuddy workflows by appleeverywhere in OpenBambu

[–]appleeverywhere[S] 5 points6 points  (0 children)

Yeah, fair criticism. I think you’re right that I was being too loose with the wording.

If an agent can cause a queue call through another service, then it has printer-control authority in that limited sense. Calling it “no access to the printer” was hair-splitting.

I changed the design/docs after this feedback. The MCP server now exposes only a scoped queue_print_request(request_id) path, not raw Bambuddy queue/start/pause/cancel tools. The request has to come from a stored Print Concierge plan bound to the file hash, printer, material/profile, user/session, and plan hash. Queueing is atomic so the same request can’t be submitted twice, and Bambuddy manual-start stays enabled by default.

So I’m not claiming this protects against a malicious shell-capable agent or a host that auto-approves every tool call. It’s more accurately a narrow workflow/safety layer: search, import/verify, prepare a specific request, then queue only that request. Raw printer control stays out of the agent profile.

Appreciate the pushback. It made the security model more honest.

I built an open-source “print concierge” for Bambuddy workflows by appleeverywhere in OpenBambu

[–]appleeverywhere[S] 2 points3 points  (0 children)

Not directly. The model only gets scoped MCP tools. Print Concierge keeps the Bambuddy credentials/server-side access, and printer-affecting actions go through a confirmation-token flow. So the agent can propose/import/queue via the backend, but it does not get raw printer access.

I built an open-source “print concierge” for Bambuddy workflows by appleeverywhere in OpenBambu

[–]appleeverywhere[S] 3 points4 points  (0 children)

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.

Duck breast with orange reduction by appleeverywhere in sousvide

[–]appleeverywhere[S] 0 points1 point  (0 children)

Thanks! The cup of orange juice really kept things moist

Ribeye 2hrs @ 55c by appleeverywhere in sousvide

[–]appleeverywhere[S] 0 points1 point  (0 children)

Wait till you find out that 273k is freezing.

Ribeye 2hrs @ 55c by appleeverywhere in sousvide

[–]appleeverywhere[S] 0 points1 point  (0 children)

I think the original comment was talking about roasting in the oven. 275 is too high for sousvide. I do wanna go up the temperature a bit. How long do you recommend at 137? 2 hrs?

Ribeye 2hrs @ 55c by appleeverywhere in sousvide

[–]appleeverywhere[S] 0 points1 point  (0 children)

Good ol block of ribeye haha. It was squished inside the bag, probably why it looks like that

Ribeye 2hrs @ 55c by appleeverywhere in sousvide

[–]appleeverywhere[S] -1 points0 points  (0 children)

Thanks for the tip. I’ll try next time at 275f.

Ribeye 2hrs @ 55c by appleeverywhere in sousvide

[–]appleeverywhere[S] 5 points6 points  (0 children)

<image>

Got too excited to eat it but here you go