Build a small all-in-one media server manager under a hard memory budget

A homelabber used Claude to write holyarrs, one app replacing six media server tools, and held it to about 70 MB of idle RAM with a test that fails above 250 MB.

Done withClaude· Nov 6, 2026

What they did

Reddit user u/CoderLuii, who says he has more than ten years in software and security, runs a home media server with the usual set of six separate apps for finding and managing movies, shows, music and subtitles. He wanted one app with a streaming-service look instead, so he designed holyarrs and had Claude write the code, in Go. Before any code, he set limits on idle memory, start time and download size. He had Claude build the same 10,000-poster home page two ways and measured both, shipped it as a single program with no operating system image inside, and added tests that load a 12,800-item library and fail if idle memory passes 250 MB, plus one that kills the app mid-job and fails if it is not back within 2 seconds.

How it went

He reports a download of about 15 MB and idle memory of about 70 MB with 12,800 titles, against 110 to 140 MB each for some of the apps it replaces. One home page build was about three times lighter and drew in half the time, so he kept that one. The restart test passes in about half a second. He says Claude kept letting memory creep past the limit until the failing test existed. The app was not yet publicly released at the time of the post.

Worth knowing

His main lesson is that the agent does not care about size unless a test makes it. A commenter pointed out that 250 MB leaves a lot of room above 70 MB for slow creep, and he agreed to check against the last release's number instead. He says he used Claude but does not name the tool or harness.

Try it

With Claude· 7 parts to fill in

We are building [describe the app] to replace [the tools it replaces]. Before writing features, write down hard budgets: idle memory under [number] MB, cold start under [number] seconds, download size under [number] MB. Add automated tests that load [a realistic data size] and fail if idle memory goes over the budget, and one that kills the app mid-task and fails if it is not back within [number] seconds. When there are two reasonable ways to build a heavy screen, build both, measure them, and show me the numbers before choosing. Stop and tell me whenever a change would push us over a budget instead of raising the limit.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related