A r/ChatGPTCoding post on August 20, 2026, did the round: a MacBook running Claude next to a tired HP laser, captioned exactly the kind of problem AI was made for. The photo — originally from a builder showing Claude writing a macOS driver for a Windows-only HP — pulled 1.3K upvotes and the usual split. Half the thread said this is the point of coding agents. The other half said writing is not the same as printing.
They are both right. Abandoned peripherals are a better job for a model than "build my startup." A terminal full of generated C is still not a test page.
This is the hardware cousin of teams canceling SaaS and rebuilding internally. The vendor left. The protocol is obscure. Custom used to mean a driver engineer. Now it means an agent, a USB cable, and someone willing to iterate.
TL;DR — should you let an agent write a printer driver?
| Question | Direct answer |
|---|---|
| Is this a good AI job? | Yes, as a class — glue for hardware the vendor abandoned |
| Is the screenshot proof? | No. Proof is a printed page, not a vibe |
| First move? | IPP/AirPrint, generic HP, then CUPS — often Linux already has the filter |
| Kernel driver? | Usually you do not need one. Userspace + CUPS is the sane path |
| Brick risk? | Real for firmware flashes. Low for a CUPS filter you can delete |
| Cheaper than a new printer? | Sometimes. Cap tokens. One thread joked the bill bought five printers |
| "Uncensored model"? | Wrong thread. Making your printer work is not a jailbreak contest |
Why this is actually the right problem
Models are strong where the work is lots of existing pattern, a device that talks back, and a binary success test. A printer either ejects a page or it does not. That is closer to loop engineering than to a product spec.
The thread's best stories have that shape:
- A grandparent OS upgrade killed an abandoned printer. A model edited or generated enough of a driver path that it worked again — the commenter's "oh, I get it" moment.
- An XP-only black-and-white laser became a house Wi-Fi printer because someone put CUPS on a spare Raspberry Pi and let the agent try filters until a page came out.
- A vinyl cutter whose vendor vanished: the owner still had to write firmware and the cutting app. That is not a five-minute driver. It is the same job at a higher price.
A treadmill "reverse engineered into a watch app" is a weaker analogy if the device already speaks a documented fitness protocol. Commenters called that out. Documented standard ≠ unique Windows blob.
This is also not Gen1Recomp as "zero source access". That joke overclaimed. The printer thread is the opposite: you have the hardware. You can fail in the open.
What "driver" usually means on a Mac in 2026
You usually do not need a kernel extension.
macOS printing is CUPS plus IPP. Many HPs already speak enough of that for print. Scan, panel, and "HP smart" extras are a different stack. If AirPrint works, stop. If Linux has a foo2zjs / HPLIP / generic filter for that family, that code is the translation target — as several commenters said — not a from-scratch Windows-to-IOKit port.
The comment that you can "shim Windows API calls and let the logic think it is still in Windows-land" is the kind of sentence that is easier said than done. Treat it as a research direction, not a prompt you paste once. We are not going to walk a reverse-engineering recipe here. If you do not own the device, or the goal is breaking ink locks, that is a different (and often illegal) job.
Ink DRM showed up in the thread too. Printers sold at a loss, ink sold at a margin, is an old business. Do not expect a chat model to be a cartridge jailbreak. That is not the grandma-printer story.
Writing ≠ will_work
Skepticism in the thread was the useful half.
- It might have copied a GitHub project. Possible. Check licenses if you ship anything.
- Claude has yeeted garbage lately. Also possible. The model will narrate success. Read the commands, not the vibe.
- A Linux Wi-Fi driver burned a whole day before the human bought a dongle. Hardware-in-the-loop still loses to a $15 part sometimes.
- Firmware flashes brick. Back up. Prefer userspace filters over flashing the printer's own ROM.
- Cost. Tokens plus your evening versus a new USB laser. Do the arithmetic before you romanticize "taking software back."
The original poster later commented that it worked. We did not stand next to that HP. A reply guessed LaserJet Pro MFP M28–M31 from text on the laptop; treat that as a screenshot read. If you have the same dusty HP, try CUPS/AirPrint first, then ask for the filter — not a kernel module.
The thread that went sideways
The top comments pivoted from printers to "models are good at reverse engineering, I wish they had fewer restrictions," then to which lab is "uncensored," then to using that for security exams and networks.
That is a different product argument (labs set refusal policies; they are not identical across vendors) and it is not the printer use case. Making a device you own print is maintenance. Pointing a model at other people's networks is not a tutorial we are going to write. If your actual job is authorized security work, use the program's rules, not a Reddit model-ranking thread.
Same for "what's stopping us from making Linux so good nobody wants Mac or Windows." The bottleneck was never a missing HP PPD. It was ops, apps, and taste. Agents change the cost of glue. They do not repeal 2x, not 10x.
What this means for what you build or pay
If you still have the hardware: try the boring path (AirPrint, generic driver, Linux CUPS filter, Pi print server) before a from-scratch driver. Then put the agent in a loop with the printer on the desk. Success is a page, not a gist.
If you are about to throw the printer away: a weekend of agent time can beat e-waste when a filter already exists in the open. If the vendor's whole business is locked ink or a unique dongle, buy a printer that speaks IPP.
If you sell hardware: abandoned Windows-only blobs are how your customers learn to hate you — and how they learn to replace you with an agent plus CUPS. Ship IPP. Document the protocol. The rebuild-internally wave includes peripherals.
If you are collecting "AI can reverse engineer anything" clips: require the test. The Hashimoto line still holds for anything you would trust overnight: commercial-grade is not a vibe.
A sane loop (no magic)
- Identify the printer exactly (model sticker, USB IDs if you know how to read them).
- Try AirPrint / IPP and macOS generic HP.
- Search whether Linux CUPS already prints to that family.
- If you need glue, ask the agent for a CUPS filter / PPD, not a kernel extension.
- Print a test page. Paste the error log, not "it didn't work."
- Stop when the page exists — or when a new printer is cheaper than the next hour.
That is vibe coding with a physical eval. It is the kind of problem models were made for. The screenshot was just the trailer.
Related on explainx.ai
- Is software dying or changing? Why teams rebuild internally
- Gen1Recomp — Claude and "zero source access" was a joke
- What is vibe coding?
- Should developers review AI-generated code?
- "2x, not 10x" — LLM coding productivity
- Loop engineering for coding agents
- OOMWOO — open-source vacuum, firmware not shipped
- os8088 — a Mac-like OS on an IBM XT
- CUPS · Vibe Coding · Coding Agent
Primary: r/ChatGPTCoding thread (August 20, 2026) · OpenPrinting CUPS
We did not reproduce the HP setup. Thread claims (it printed; token jokes; guessed model family) are reported as comments, not as our lab results. Do not flash firmware you cannot restore. Do not use this as a guide to bypass ink locks or access systems you do not own.