Skip to content
Prompt & SolderHow to Ask Claude
All builds

Image: paperflowmac.vercel.app · PaperFlow for macOS — your desktop, quietly alive. Native video wallpapers and Wallpaper Engine scenes, free and open source.

Worked Proof shown

A Wallpaper Engine style app for macOS rewritten in Rust

Claude wrote the whole Rust rendering backend for a macOS live-wallpaper app that uses far less memory than existing apps.

—

Credits

  • Reddit poster Suitable-Accident-66 Source ↗

Earliest dated source: 2 Nov 2026

The full story

The poster used Claude to build a Wallpaper Engine port for macOS, with Claude writing the entire Rust backend from scratch. The poster says the weekly usage limit was used up building it.

The claimed result is that plain video wallpapers use 12 to 25 MB where other apps took 200 to 250 MB, and heavy scenes dropped from 1.5 to 1.7 GB to under 700 MB. These figures are the poster's own.

How it was done

Tools

Themes

Loading themes…

Sources

From a short post by the maker, so the details are as they tell them.

  • Reddit: Wallpaper Engine port for MacOSForum threadDeleted on Redditreddit.com

    The maker's post on r/ClaudeCode.

    The poster has deleted it, but the original is still readable (it can take a few seconds to load): archived copy of Reddit: Wallpaper Engine port for MacOS (opens in a new tab)

  • The project: paperflowmac.vercel.appBlog or write-uppaperflowmac.vercel.app

    Linked in the post.

  • Reddit: Wallpaper engine port for MacOS, rewritten from scratch using RustForum threadreddit.com
    Reddit poster: Suitable-Accident-66Posted 2 Nov 2026

    If it disappears: archived copy of Reddit: Wallpaper engine port for MacOS, rewritten from scratch using Rust (opens in a new tab)

Related builds

Finding related builds…

Prompt & Solder

An independent community project. Not affiliated with Anthropic.

What this is. Real projects where people used Claude to build, fix, port, revive or take apart something, from jailbroken Kindles to rebuilt DOS games, plus the times it went badly wrong. Every build links to where it was shared, and every source is listed here.

How far to trust it. We summarise what people reported and say what each build rests on: a full write-up with code, a short post, or a passing comment. We haven't tested them ourselves. Photos are shown from the original sources with credit. Only modify hardware you own, and back up first.

Privacy. No accounts. Analytics cookies (Google Analytics) only if you accept them; no ads or cross-site tracking. Searches are counted anonymously (just the words) to show what's popular, and so are clicks on Ask Claude (just the count). The Claude connector only receives the search words your Claude sends it.

How toAsk ClaudeEvery sourceStatsSubmit a buildPrivacyRSS