Yusef Mosiah Nathanson

Founder of Choir

The iMac Is a Better Agent Server Than a Laptop

Mosiah.org · article artifact

Running Hermes in UTM on a Mac is technically simple: make a Linux VM, install Hermes, keep the machine awake, and let agents work against durable local state.

The harder question is whether the Mac is a real home for agents or just another device that sometimes runs a chatbot.

For a laptop user, UTM is useful but fragile. A laptop moves. It sleeps. It loses network. It becomes the user's bag object, cafe object, battery object, couch screen, and travel companion. That flexibility is the point of a laptop, but it fights persistent agent work. Durable agents need a place where state can accumulate while the human is not actively holding the thread.

That is why people buy Mac minis.

But my iMac has turned out to be an even better personal agent station than I expected.

Constraints create constructs

I chose the iMac over a MacBook for ergonomic reasons. I wanted to use my split keyboard and remove the fallback to the built-in QWERTY keyboard. I also wanted to remove the option of pretending that serious work could happen anywhere: cafe, couch, airport gate, half-distracted portable posture.

That constraint became a construct.

The iMac is a station: large screen, stable power, fixed keyboard, persistent network, no lap mode. With caffeinate, it also becomes a plausible always-on agent host. Not a server rack, not quite a Mac mini, not merely a desktop — a human-comfortable review surface attached to a durable VM runtime.

That is the shape that matters:

Mac hardware
  -> UTM Linux VM
      -> Hermes Agent
          -> repos, skills, artifacts, cron jobs, browsers, evidence

The Mac remains the human machine. The UTM guest becomes the agent machine.

The operating pattern

The setup guide is short:

  1. Install UTM.
  2. Create a Debian or Ubuntu Linux VM.
  3. Give it enough disk, memory, CPU, and network access for browsers, builds, repos, and long runs.
  4. Install Hermes inside the VM.
  5. Keep canonical work inside the VM filesystem.
  6. Use shared folders only for deliberate transfer, not as the main state store.
  7. Keep the Mac awake during runs.

On macOS:

caffeinate -dimsu

or for a bounded eight-hour run:

caffeinate -dimsu -t 28800

That command is crude but philosophically correct. If agents are going to work overnight, the substrate has to stay alive overnight.

A daily pattern then emerges:

Evening:
  start bounded Hermes runs
  keep the iMac awake
  let the VM work

Morning:
  review evidence and diffs
  promote or reject changes
  update bags, notes, drafts, and next runs

The important distinction is between candidate motion and promoted reality. Agents can explore while the human is away. Promotion should still be serialized, evidenced, and reviewed.

Agentic depth needs boring infrastructure

The deeper point is not UTM. It is agentic depth.

Long-running agent work is not just a sequence of prompts. It becomes bags of tasks, probes, notes, verifier improvements, failed branches, cleanup passes, and promotion decisions. Choir's vocabulary for this is:

MissionGradient -> MissionBag -> Sweep -> Fly -> Cycle

A goal completes. A sweep improves a region. A fly runs a bounded campaign. A cycle keeps the system alive.

A laptop can host a prompt. A stationary VM can host a cycle.

That is the practical reason form factor matters. A persistent agent setup wants boring infrastructure: power, network, stable files, logs, browser state, source checkouts, scheduled jobs, and a place to return for review. The machine should make continuity easy and drift expensive.

The iMac surprised me because it combines both sides of the loop. It is stable enough to host agents and humane enough to review them. A Mac mini is the obvious always-on computer, but it needs a station around it. The iMac already is the station.

The scarce resource is review

The bottleneck is not CPU. It is human crystal attention.

A one-hour agent run can be exhausting because it returns with changed state that must be understood. The infrastructure should therefore optimize for:

promoted value / human crystal attention

A good Hermes-in-UTM setup preserves evidence, logs, source artifacts, drafts, and rollback paths. It lets the human sit down at the same station and ask: what changed, what was proven, what is risky, what can be ignored, and what needs a decision?

That is why the iMac matters. The split keyboard is there. The screen is there. The VM is there. The agents' world is there. Review happens in the place where the work lives.

Portability is not always freedom. Sometimes freedom is the removal of bad options.

The real guide

The mechanical guide is:

Install UTM.
Create Linux VM.
Install Hermes.
Keep the Mac awake.
Run agents in the VM.
Preserve artifacts.
Verify before promotion.

The real guide is:

Give agents a durable place to live.
Give the human a comfortable place to review.
Do not confuse portability with agency.
Do not confuse autonomy with depth.

The iMac was not just a desktop choice. It became an accidental agent server.

And maybe that is the lesson: durable intelligence is not only a model property. It is an arrangement of machines, posture, constraints, evidence, and return paths. The computer has to stay awake. The artifacts have to survive. The human has to return to a place where review is possible.