Mac mini as a server: 53 lessons learned while moving my AI jobs A solo developer moved scheduled AI jobs off a MacBook onto a 32 GB Mac mini M6 in a single day, using Claude Code to do the typing, and logged 53 wrong assumptions along the way — 33 of them general to any Mac and published in a public GitHub repo alongside a runbook and scripts. The developer's safe-run logs showed 73 runs dropped after waiting (30 during calls, 43 on battery at night) and 127 runs killed mid-flight by a memory guard between 18 October and 21 November 2026. The resulting rule: run jobs in the cloud unless they need local data or logins, and keep one job on one machine. Originally published at marian.coach https://www.marian.coach/blog/mac-mini-as-a-server/ . The full runbook with a check per step is in the public GitHub repo https://github.com/marian-kamenistak/mac-mini-as-a-server . My Mac mini https://www.apple.com/mac-mini/ M6 with 32 GB arrived. I gave myself one day, with Claude Code https://code.claude.com/ doing the typing, to move all scheduled jobs off the MacBook. By the evening I had logged 53 wrong assumptions, mine and Claude's. 33 of them apply to any Mac and are in the public repo https://github.com/marian-kamenistak/mac-mini-as-a-server , next to the runbook and the scripts. That list has grown to 37 since. The other 20 were about my own jobs. The 14 that hurt most are below. The rule I ended the day with: cloud first, the Mac mini only for what the cloud can't run, and one job on one machine. "My local notebook is freezing sometimes." I wrote that to Claude on 17 November, four days before the mini arrived. I run a one-person business with scheduled AI jobs around it: a brief before each mentoring call, lead source traces, blog publishing, follow-up messages, SEO reports. The bigger picture is in how my AI executive assistant works https://www.marian.coach/blog/ai-executive-assistant/?utm source=devto&utm medium=referral&utm campaign=mac-mini-as-a-server-202611 . Until this week all of it ran on the MacBook I use for video calls. The jobs run through a wrapper I call safe-run. Before a job starts, it checks if I'm on a call, if the laptop is on battery, if memory is low. If yes, the job waits and safe-run asks again 10 minutes later. Good for my calls, bad for the jobs. Some runs waited out their limit and were dropped. Its log from 18 October to 21 November 2026: | What happened | Count | |---|---| | A job had to wait | 432 times | | Longest wait | 6 hours, on 5 November. Then the run was dropped | | Runs dropped after waiting | 73 30 on calls, 43 on battery at night | | "Not yet" answers in total, one per 10-minute check | 2,204 | | Not yet, I was on a call | 1,581 | | Not yet, laptop on battery | 581 | | Not yet, memory low | 41 | | Not yet, no internet | 1 | | Killed in the middle by the memory guard | 127 runs 33 jobs | My calls beat my jobs, day after day Source: my safe-run log, 18 Oct to 21 Nov 2026. When my jobs had to wait The memory side looked like this: Memory: the MacBook before, the Mac mini after Sources: the safe-run and memory-guard log on the MacBook; macOS memory pressure on the mini, one reading on 21 Nov 2026. Not all of that memory was the jobs. On day two I counted 24 open Claude sessions on the same laptop, and I can't split the swap between the two. My Control Room dashboard showed it from the other side: in 25 days it recorded 495 runs that ended as "Mac asleep, offline or busy". On 17 November the overnight job that writes my outreach drafts crashed at 05:03 on a network timeout. The lid was closed. Why a Mac mini AI server and not a Linux box? My jobs are launchd jobs, my browser profiles are macOS Chrome profiles, and my Claude Code skills expect the same paths as on the laptop. A second Mac meant zero rewrites. Most Mac mini posts I read before buying start from the box: I Run 25 Automated Agents on a Mac Mini https://stacker.news/items/1435399 , or an M6 turned into an agent server that runs around the clock https://jamesm.blog/ai/mac-mini-m6-always-on-ai-agent-server/ . They're right that a mini is cheap, quiet and fast. Where I disagree: they put the whole stack on it. A Mac at home is one power cut, one macOS restart or one Wi-Fi drop away from stopping all of it. So I sorted the jobs before I moved one. A job runs where its data and its login live. Anything that only calls an API goes to the cloud. | Where | What runs there | My jobs, for example | |---|---|---| | MacBook | Where I work | Meetings + mic, Memory + search, Manual sends | | Mac mini | What the cloud can't run | Logged-in browsers, Claude Code jobs, Senders, Pollers + deploys | | Cloudflare Workers https://workers.cloudflare.com/ | APIs, sending, frequent crons | Newsletter send, Reindex queue, Mentee digest | | GitHub Actions https://github.com/features/actions | Batches on APIs, work that commits to a repo | CRM sync, SEO reports, Daily briefs | | Activepieces https://www.activepieces.com/ | the clock | Fires the GitHub Actions schedules on time | Where my scheduled jobs run now The cloud counts include only jobs that used to run on the Mac. Claude routines https://code.claude.com/docs/en/routines are the sixth place, for LLM judgment with both Macs off. I run 0 jobs there today. They're the next stop for the Claude Code jobs that don't need my files. Where my scheduled jobs run, 21 November 2026. The MacBook and the mini talk over Tailscale. One check before the questions: if a job keeps "already sent" state on disk, it stays where that state is until you move the state. Then ask in this order, per job. The first yes decides. Before the move, 70 jobs were tied to the Mac: 63 LaunchAgents plus the jobs of my Claude cron daemon. | Verdict | Jobs | |---|---| | Move to the Mac mini | 29 | | Has a cloud copy, the Mac version runs until the copy passes | 17 | | Merged into another job | 8 | | Stay on the MacBook | 7 | | Retired | 6 | | Still open | 3 | The rule says 29 jobs belong on the mini. Tonight it runs 47. The 18 extra are from the "cloud copy" row and the open ones: their Mac version keeps running until the cloud copy passes testing. 5 of them are senders, and their "already sent" memory still lives on the mini's disk. How much work moved? The safe-run log records how long each run took. Over the 34 days, the MacBook spent 207.9 hours running jobs. CPU and RAM per job weren't logged, so run time is the best measure I have. How much laptop work moved to the Mac mini Wall-clock run time from my safe-run log, 18 Oct to 21 Nov 2026. CPU and RAM per job were not logged. The jobs that took the most laptop time went to the mini: The 9 heaviest jobs the mini took over Source: safe-run log, 18 Oct to 21 Nov 2026. Run count and run length tell different stories. The pollers ran hundreds of times for under a minute each, the list builders and draft writers a few dozen times for half an hour: Many small runs or a few heavy ones Double sends are a state problem, not a machine problem. When the "already sent" ledger lives in a shared store with a key per message, a job can run on any machine, a restored backup or a cloned repo, and still send once. Mine still lives in gitignored files, so the senders are the last jobs to leave the box. For a team the same sort works. The home box becomes an office Mac, a hosted Mac or a self-hosted runner. The jobs with no clean cloud home are the same two: logged-in browsers and the subscription CLI on local files. Mentoring. Mac mini: intro-call briefs, session briefs and notes, the overnight session knowledge base, newsletter follow-ups, replies on syndicated posts, lead source traces. Cloud: the mentee evening digest and the newsletter send on Workers. ELC community. Mac mini: logged-in browser jobs that send follow-ups, bounce reroute, reply watch, overnight outreach drafts, the work-email finder, the partner lead list, grant research. MacBook: manual sends and grant follow-ups. ELC Conference. Mac mini: speaker invites from a logged-in browser. Platform and SEO. Mac mini: Reddit and Quora answers, the Copilot citation pull, the login check for browser profiles, blog publishing, the fix queue, canaries for the senders. GitHub Actions: CRM sync to analytics, SEO reports, Bing stats, AI-crawler logs, a pipeline health check, the daily web brief. Workers: the reindex queue. Both Macs: the Chrome cleaner, the Claude login watch, the ledger mirror. Personal ops. Mac mini: LinkedIn post drafts from yesterday's work, call follow-up drafts. GitHub Actions: the marketing board, daily and weekly. MacBook: meeting recordings, the memory jobs, the search index, the session snapshot. I asked ChatGPT and Perplexity the same question in English, Czech and Polish: can I use Migration Assistant to set up a Mac mini server? Both said yes, in all three languages. Perplexity added in English that a clean setup "is often preferable". Neither mentioned scheduled jobs. For a personal Mac, yes is the right answer. For a Mac that runs jobs, Migration Assistant copies the LaunchAgents and leaves their memory behind. Both Macs then send the same follow-up email to the same person. Four rules, written before I touched the box. My plists and scripts hard-code /Users/