<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: MacRun</title>
    <description>The latest articles on DEV Community by MacRun (macrun).</description>
    <link>https://dev.to/macrun</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F15613%2F9cee2edb-6968-4bc4-b09b-cf2c60a02f2c.png</url>
      <title>DEV Community: MacRun</title>
      <link>https://dev.to/macrun</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/macrun"/>
    <language>en</language>
    <item>
      <title>GitHub Actions pricing 2026: Linux $0.006, macOS $0.062 per minute</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Sat, 07 Nov 2026 03:41:17 +0000</pubDate>
      <link>https://dev.to/macrun/github-actions-pricing-2026-linux-0006-macos-0062-per-minute-2m5n</link>
      <guid>https://dev.to/macrun/github-actions-pricing-2026-linux-0006-macos-0062-per-minute-2m5n</guid>
      <description>&lt;p&gt;GitHub Actions is free for public repositories and metered by the minute for private ones, with a different rate for every runner type. This page puts all the rates in one place. It explains how included minutes really get used. And it shows why the macOS line is the one that ends up on the invoice.&lt;/p&gt;

&lt;h2&gt;
  
  
  The per-minute rates
&lt;/h2&gt;

&lt;p&gt;These are GitHub's published rates for hosted runners on private repositories. They are per minute of wall-clock time. Every job is rounded up to the next minute:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  Linux 2-core (x64)          $0.006
  Linux 2-core (arm64)        $0.005
  Windows 2-core              $0.010
  macOS 3-core / 4-core       $0.062
  macOS 12-core               $0.077
  macOS 5-core (M2 Pro)       $0.102
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two things stand out. A standard macOS minute costs about ten times a Linux minute, and the largest macOS runner costs about seventeen times. Everything else on the invoice is small next to that column.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Building iOS or macOS apps?&lt;/strong&gt; That macOS column is where a dedicated Mac pays off. A flat $139 a month M6 runner covers about 2,242 metered minutes, and every build after that costs nothing. It works with GitHub Actions through a two-line change to your workflow. See &lt;a href="https://macrun.dev/pricing?ref=devto" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, or try it for a day with a &lt;a href="https://macrun.dev/rent-a-mac-for-a-day?ref=devto" rel="noopener noreferrer"&gt;day pass&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How included minutes really work
&lt;/h2&gt;

&lt;p&gt;Paid plans include a block of minutes each month, roughly 2,000 on Free, 3,000 on Team and 50,000 on Enterprise. The catch is that the allowance is counted in Linux-equivalent minutes. A macOS minute consumes ten included minutes and a Windows minute consumes two. A single ten-minute iOS build therefore uses a hundred minutes of a 3,000-minute allowance.&lt;/p&gt;

&lt;p&gt;In practice, an iOS team on the Team plan uses up its allowance in the first week or two. It pays the metered rate for the rest of the month. The included minutes are not a discount on macOS work so much as a short grace period.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a real month looks like
&lt;/h2&gt;

&lt;p&gt;Take a small team that runs a 12-minute test suite on every pull request, about 20 pushes a working day. That is roughly 5,000 macOS minutes a month:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  5,000 min  x  $0.062  =  $310/mo   (standard runner)
  5,000 min  x  $0.102  =  $510/mo   (largest runner)
  flat dedicated M6              $139/mo   (unlimited)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The flat machine wins from about 2,242 minutes a month upward at the standard rate, and the gap widens with every build after that. Put your own numbers into the &lt;a href="https://macrun.dev/calculator?ref=devto" rel="noopener noreferrer"&gt;calculator&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Costs that are not minutes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Storage.&lt;/strong&gt; Artifacts and caches beyond the included allowance bill per gigabyte per month. Large Xcode archives add up if retention is left at the default.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-downloads.&lt;/strong&gt; Hosted runners start clean, so every job re-fetches dependencies and rebuilds caches. That time is billed at the macOS rate too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Queue time is free, but not cheap.&lt;/strong&gt; Waiting for a macOS runner does not bill minutes, but it delays every merge.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The one decision that matters
&lt;/h2&gt;

&lt;p&gt;For teams that build daily, the question is not which macOS runner size to pick, it is whether to pay per minute at all. Below the break-even, metered billing is fine and simple. Above it, a dedicated Mac at a flat price is cheaper every month and gets faster as caches warm. The &lt;a href="https://macrun.dev/guides/github-actions-macos-minutes-cost?ref=devto" rel="noopener noreferrer"&gt;macOS minutes guide&lt;/a&gt; goes deeper on that math.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How much does GitHub Actions cost per minute?
&lt;/h3&gt;

&lt;p&gt;For private repositories: Linux 2-core $0.006, Windows 2-core $0.010, macOS 3- or 4-core $0.062, macOS 12-core $0.077. The 5-core M2 Pro macOS runner is $0.102 per minute. Public repositories are free on standard runners.&lt;/p&gt;

&lt;h3&gt;
  
  
  How are included minutes counted for macOS?
&lt;/h3&gt;

&lt;p&gt;Included minutes are measured in Linux-equivalent minutes. Each macOS minute uses ten included minutes and each Windows minute uses two, so a 3,000-minute allowance covers only about 300 macOS minutes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is GitHub Actions free for public repositories?
&lt;/h3&gt;

&lt;p&gt;Yes, standard hosted runners are free for public repositories. Larger runners and private repositories are billed per minute.&lt;/p&gt;

&lt;h3&gt;
  
  
  When does a dedicated Mac become cheaper than GitHub-hosted macOS?
&lt;/h3&gt;

&lt;p&gt;At the standard $0.062 rate, a flat $139 per month dedicated runner breaks even near 2,242 macOS minutes a month. Most teams building daily pass that point within the first two weeks.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://macrun.dev/guides/github-actions-pricing-explained?ref=devto" rel="noopener noreferrer"&gt;macrun.dev&lt;/a&gt;. Full disclosure, I run MacRun, which rents dedicated Mac minis for builds and coding agents.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>githubactions</category>
      <category>devops</category>
      <category>ci</category>
      <category>ios</category>
    </item>
    <item>
      <title>M6 Mac mini vs GitHub's hosted macOS runner: an Xcode build benchmark</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Wed, 04 Nov 2026 23:15:07 +0000</pubDate>
      <link>https://dev.to/macrun/m6-mac-mini-vs-githubs-hosted-macos-runner-an-xcode-build-benchmark-5efa</link>
      <guid>https://dev.to/macrun/m6-mac-mini-vs-githubs-hosted-macos-runner-an-xcode-build-benchmark-5efa</guid>
      <description>&lt;p&gt;We wanted a real number for one question. How much faster is a dedicated M6 Mac mini than GitHub's standard hosted macOS runner, on a real iOS app? So we built the open-source Wikipedia iOS app on both, with the same Xcode and the same script, three times each.&lt;/p&gt;

&lt;p&gt;This post replaces our earlier M4 benchmark post. Every number here comes from runs made on September 24, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Results
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Median of 3 runs, in seconds. Lower is better.

                      GitHub-hosted   MacRun M6   change
                      macos-26
package download            43            39       -8%
clean build                183            86      -53%
incremental build           21            10      -51%
no-op build                 20            10      -50%
220 unit tests              44            17      -61%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The M6 was about twice as fast at compiling. The package download was close, because both machines pull the same packages from GitHub over fast connections. Every step succeeded on both machines in every run.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a normal CI job costs in time
&lt;/h2&gt;

&lt;p&gt;The table compares the machines step by step. A real CI job is different on each. A hosted runner starts every job empty. It has to download packages, build from clean, and then test. A dedicated Mac keeps its build folder, so after a small change it only rebuilds what changed.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Full CI job, median of three runs.
GitHub-hosted, fresh VM   269 s
M6, empty caches          142 s
M6, warm caches            27 s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Hosted: download, clean build, tests. M6 warm: incremental build, tests.&lt;/p&gt;

&lt;p&gt;That is the gap your team feels. A job that took four and a half minutes finishes in under thirty seconds. On a busy day of pushes, the saved minutes add up to hours.&lt;/p&gt;

&lt;p&gt;The same job costs money on a hosted runner. GitHub rounds each job up to the minute, so 269 seconds bills as 5 minutes. At $0.062 a minute that is about 31 cents a job. On a dedicated Mac it costs nothing extra. Our &lt;a href="https://macrun.dev/calculator?ref=devto" rel="noopener noreferrer"&gt;cost calculator&lt;/a&gt; turns your own job count into a monthly figure.&lt;/p&gt;

&lt;h2&gt;
  
  
  The two machines
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub-hosted macos-26&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Apple M2 Pro (Virtual), 5 cores&lt;/li&gt;
&lt;li&gt;14 GB memory&lt;/li&gt;
&lt;li&gt;macOS 26.6.2, fresh VM per job&lt;/li&gt;
&lt;li&gt;Xcode 26.6 (17F113)&lt;/li&gt;
&lt;li&gt;Standard runner, $0.062 a minute&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;MacRun M6 mini&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Apple M6, 12 cores, bare metal&lt;/li&gt;
&lt;li&gt;16 GB memory&lt;/li&gt;
&lt;li&gt;macOS 27.0, same machine every job&lt;/li&gt;
&lt;li&gt;Xcode 26.6 (17F113)&lt;/li&gt;
&lt;li&gt;Flat $139 a month&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The hardware details come from the machines themselves. Each run printed its chip, core count and memory before building. GitHub also sells larger macOS runners at higher per-minute prices. We tested the standard one because it is what most teams use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Method
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Project: wikimedia/wikipedia-ios at commit 8691a89, built for the iOS Simulator with its Wikipedia scheme and Swift packages.&lt;/li&gt;
&lt;li&gt;Simulator: a new iPhone 17 on iOS 26.5, created the same way on both machines.&lt;/li&gt;
&lt;li&gt;Every run starts with the package cache and DerivedData deleted. Signing is off, as it usually is for CI simulator builds.&lt;/li&gt;
&lt;li&gt;Package download: &lt;code&gt;xcodebuild -resolvePackageDependencies&lt;/code&gt; into an empty folder.&lt;/li&gt;
&lt;li&gt;Clean build: &lt;code&gt;xcodebuild build-for-testing&lt;/code&gt; with empty DerivedData and packages already downloaded.&lt;/li&gt;
&lt;li&gt;Incremental build: the same command after adding one comment line to one Swift file in the app.&lt;/li&gt;
&lt;li&gt;No-op build: the same command again with nothing changed.&lt;/li&gt;
&lt;li&gt;Tests: the 220 unit tests in the app's WMFData package, run with &lt;code&gt;test-without-building&lt;/code&gt; on a booted simulator.&lt;/li&gt;
&lt;li&gt;Three full runs on each machine. We report the median.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Caveats
&lt;/h2&gt;

&lt;p&gt;We ran the app's package tests, not its main test target. The main target needs signed app-group entitlements, and an unsigned CI build does not have them. Its test host kept relaunching on both machines, so it was no fair measure.&lt;/p&gt;

&lt;p&gt;The incremental build touched one small file. Most of its 10 seconds is Xcode planning the build, which is why it matches the no-op build. A change to a widely used file would take longer on both machines.&lt;/p&gt;

&lt;p&gt;The two machines ran different macOS versions, because each ran what its owner ships today. A hosted job can also cache Swift packages with &lt;code&gt;actions/cache&lt;/code&gt;. That would cut the download step. It would not remove the clean build, which is most of the time.&lt;/p&gt;

&lt;p&gt;We sell the M6 runner, so weigh our numbers with that in mind. The method above is complete enough to rerun on your own project, which is the only benchmark that really matters to you.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://macrun.dev/blog/m6-mac-mini-vs-github-hosted-macos-runner-benchmark?ref=devto" rel="noopener noreferrer"&gt;macrun.dev&lt;/a&gt;. Full disclosure, I run MacRun, which rents dedicated Mac minis for builds and coding agents.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>githubactions</category>
      <category>devops</category>
      <category>macos</category>
    </item>
    <item>
      <title>Claude Code stops when your Mac sleeps: 5 fixes, lid closed too</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Mon, 26 Oct 2026 12:32:08 +0000</pubDate>
      <link>https://dev.to/macrun/claude-code-stops-when-your-mac-sleeps-5-fixes-lid-closed-too-1o7o</link>
      <guid>https://dev.to/macrun/claude-code-stops-when-your-mac-sleeps-5-fixes-lid-closed-too-1o7o</guid>
      <description>&lt;p&gt;You gave Claude Code a long task, closed the lid, and came back to a dead session. Nothing is wrong with the agent. macOS put the machine to sleep, and sleep suspends every process, drops the network, and ends any SSH connection. This page covers the settings that stop that, in the order to try them, and the point where the honest fix is a different machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually happens at sleep
&lt;/h2&gt;

&lt;p&gt;When a Mac sleeps, the CPU stops running your processes. The agent is not killed. It is frozen. When the machine wakes, the process continues. By then the API connection it was using has timed out. The tool call it was in the middle of has failed. On a laptop, a closed lid means sleep within seconds unless something prevents it. A lock screen does not cause sleep. A screensaver does not either. Only the sleep timer and the lid do.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 1: caffeinate for a single task
&lt;/h2&gt;

&lt;p&gt;macOS ships a tool that holds the machine awake while a command runs. Start the agent through it and the Mac stays up until the agent exits.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;caffeinate &lt;span class="nt"&gt;-i&lt;/span&gt; claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The flag keeps the system from idle sleeping. Add a second flag to keep the display on too, which matters only for tools that drive the screen.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;caffeinate &lt;span class="nt"&gt;-di&lt;/span&gt; claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This does not survive a closed laptop lid. The lid switch overrides every idle assertion. It also does nothing after the agent exits and you start the next task without it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 2: turn off sleep for the machine
&lt;/h2&gt;

&lt;p&gt;On a desktop Mac, or a laptop on power, set the sleep timer to never and leave it. These are the settings we use on every agent Mac.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; &lt;span class="nb"&gt;sleep &lt;/span&gt;0
&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; disksleep 0
&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; displaysleep 10
&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; womp 1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The display can still sleep. That saves power and changes nothing for a terminal process. The last line enables wake on network, which helps if something does put the machine down.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 3: the closed lid
&lt;/h2&gt;

&lt;p&gt;A MacBook with the lid closed sleeps unless it is on power and connected to an external display, keyboard, or mouse. That is Apple's clamshell rule. Without a display, one more setting forces the machine to stay awake with the lid shut.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; disablesleep 1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Undo it later with the same command and a zero. Two warnings. The laptop will run warm in a bag or on a bed, so leave it on a hard surface. And it will drain a battery in a few hours if the power cable comes out, then die without a clean shutdown.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 4: the terminal, not the machine
&lt;/h2&gt;

&lt;p&gt;Sometimes the Mac stayed awake and the session still vanished. That is the terminal window closing or the SSH connection dropping, which sends a hangup to everything inside it. The answer is a terminal multiplexer. Run the agent inside a tmux session and it survives the window, the SSH drop, and the Wi-Fi hiccup.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew &lt;span class="nb"&gt;install &lt;/span&gt;tmux
tmux new &lt;span class="nt"&gt;-s&lt;/span&gt; agent
claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Detach with Ctrl-b then d. Reattach later from any terminal, or from your phone over SSH, with one command.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;tmux attach &lt;span class="nt"&gt;-t&lt;/span&gt; agent
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There is a full guide to this setup: &lt;a href="https://macrun.dev/guides/keep-claude-code-session-alive-with-tmux?ref=devto" rel="noopener noreferrer"&gt;keeping a Claude Code session alive with tmux&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 5: come back after a reboot
&lt;/h2&gt;

&lt;p&gt;Security updates restart the machine. Power blips restart it. After a restart nothing is running until someone logs in. For a machine that is meant to be unattended, enable automatic login for the agent user in System Settings. Then add a LaunchAgent that recreates the tmux session at login. The &lt;a href="https://macrun.dev/guides/always-on-mac-for-ai-agents?ref=devto" rel="noopener noreferrer"&gt;always-on Mac checklist&lt;/a&gt; has the full list, including battery backup.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the laptop is the wrong machine
&lt;/h2&gt;

&lt;p&gt;Everything above works. It also turns your laptop into a server you cannot take anywhere. Once the agent is doing real work overnight, most people move it to a machine whose only job is to stay on. There are four choices. A spare Mac mini at home. A Linux box, if you do not need Xcode. A Mac in a cloud. Or a hosted Mac mini that someone else keeps awake. The &lt;a href="https://macrun.dev/guides/where-to-run-a-24-7-coding-agent?ref=devto" rel="noopener noreferrer"&gt;comparison of places to run a 24/7 agent&lt;/a&gt; has the costs side by side.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does caffeinate keep Claude Code running with the lid closed?
&lt;/h3&gt;

&lt;p&gt;No. The lid switch overrides caffeinate on a MacBook. You need the machine on power with an external display connected, or the disablesleep power setting.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will the lock screen or screensaver stop the agent?
&lt;/h3&gt;

&lt;p&gt;No. Locking the screen and running the screensaver do not sleep the machine. Only the sleep timer, low battery, or a closed lid do. A locked screen is fine for a terminal agent.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does this apply to Codex too?
&lt;/h3&gt;

&lt;p&gt;Yes. Codex CLI is a terminal process like Claude Code. The same sleep settings, caffeinate, and tmux apply, and the same lid rule.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I keep the Mac awake from my phone?
&lt;/h3&gt;

&lt;p&gt;You can start a task from your phone with Claude Code's Remote Control or over SSH, but you cannot stop a Mac from sleeping remotely once it decides to. Set the power settings once on the machine itself.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://macrun.dev/guides/claude-code-stops-when-mac-sleeps?ref=devto" rel="noopener noreferrer"&gt;macrun.dev&lt;/a&gt;. Full disclosure, I run MacRun, which rents dedicated Mac minis for builds and coding agents.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>claudecode</category>
      <category>ai</category>
      <category>macos</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
