How to use Claude to build an approval-gated print server
A new QIDI Q2 owner reports using Claude to build a local print server that searches models, slices files and requests approval before printer actions. A Benchy print succeeded after feed problems.
reddit.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Editorial suggested prompt: Help me build a local print server for my printer API. Search and slice models using the correct printer profile, show estimated material and time, and require my explicit approval before starting or cancelling. Keep physical loading and first-layer checks with me.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- /u/Greedy-Duck
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The owner reports a working self-hosted print workflow and a good first Benchy with slight stringing after two attempts printed air because filament had not engaged. Claude also repaired a camera configuration broken by a firmware update.
- Human involvement
- The owner approves print requests and printer actions and physically loads filament. Two initial attempts failed to extrude; the source does not establish unattended physical safety or independent audits of the guardrails.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The owner chooses a QIDI Q2 with Claude's help and has Claude build a self-hosted printhub server for its Klipper/Moonraker API.
- The described workflow searches Printables, slices with official OrcaSlicer Q2 profiles and presents estimated time, material and cost for approval.
- The owner confirms starts or cancellations; the server checks filament compatibility and sends status and first-layer notifications through ntfy.
A new 3D printer owner, /u/Greedy-Duck, describes using Claude to handle the software setup for a QIDI Q2. Claude helped choose a printer with a Klipper/Moonraker API and built a small self-hosted server called printhub to connect the assistant to it.
The described workflow accepts an ordinary-language request, searches Printables and slices a model with OrcaSlicer using official Q2 profiles. It presents estimated time, material use and cost before the owner approves a print. The author says nothing starts or cancels without confirmation and that the server refuses to start when the loaded filament does not match the slice. A separate page lets their partner request jobs for approval.
The server runs in a Proxmox container. The author describes a firewall that restricts printer access to that server, Tailscale for remote access and ntfy notifications for printer events and a first-layer photograph. Those are reported controls, not an independent security or safety audit.
The physical result was not immediate. Two early attempts printed air because the filament had not engaged. After addressing loading, the owner reports a good Benchy with some stringing. Claude also found and fixed an incorrect camera ID after a firmware update. In comments, the owner confirms feed issues and says a proposed Raspberry Pi screen-leg project remained unprinted. That proposed project is not counted as a completed result here.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Reddit · /u/Greedy-Duck
Frequently asked questions
Can this setup start prints without approval?
The author says starts and cancellations require confirmation, and filament must match the slice. These are reported guardrails, not independently tested guarantees.
What did the owner actually print?
The owner reports a successful Benchy with slight stringing after two attempts printed air because filament had not engaged. A Raspberry Pi screen-leg project mentioned in comments had not yet been printed.
More details
Remaining steps
- Claude fixes a camera configuration after a firmware update. The owner resolves physical filament loading problems before reporting a successful Benchy.
About this account
Claude built the integration server and diagnosed a camera configuration fault. The reported server workflow searches models and prepares slices; it requires the owner's confirmation before starting or cancelling prints.
First-person account and saved author comments reviewed from https://www.reddit.com/r/ClaudeAI/comments/1x8xz3l/i_let_claude_handle_the_software_side_of_my_new/ Reported results have not been independently reproduced. Suggested prompt is an editorial reconstruction, not the author's original prompt.
Credit: /u/Greedy-Duck on r/ClaudeAI
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude · QIDI Q2 · Klipper/Moonraker · OrcaSlicer · Printables · Proxmox · Tailscale · ntfy
3D printing · Homelab · Human approval
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.