You asked a sharp question: of everything the fleet runs today, what is genuinely 100% locked to a Mac and could never move to a PC plus a browser? Here is the grounded answer, built from an actual inventory of what the fleet uses right now, split two ways: what locks you to a Mac, and what would lock a chiropractor you sell this to to a Mac.
The trap is treating anything Apple flavored as Mac locked. Most of it is not. Here is the honest sort.
What the fleet uses today, whether it is Mac locked, and what replaces it if you leave the Mac.
| What the fleet uses | Mac locked? | Why / replacement |
|---|---|---|
| iMessage personal SMS lane texts to you, blue bubble | Mac only | Messages.app plus chat.db plus AppleScript. Replacement already in hand: OpenPhone for all SMS, which the TTC line already uses. |
| Instagram carousels over 10 slides TTC and VE posts | Mac only | iPhone Mirroring needs a Mac, the Apple ID, and a paired iPhone. Workaround: post 10 or fewer on the web, or do big carousels on any phone manually. |
| Driving native Mac apps Messages, Keynote, System Settings, Photos, Safari for iCloud | Mac only | Needs a logged in Mac screen and macOS permission grants. Cannot run headless or off box. Note: most automation targets are web, which is not Mac locked. |
| iCloud and Apple account | Mac only | Your personal Apple ecosystem. A customer who is not on Apple does not need any of this. |
| Service auto start Cloudflare tunnel, web terminal, daily exports, the daemon | Movable | Uses launchd on Mac. Equivalent on Linux is systemd, on Windows is Task Scheduler. |
| Credential storage fallback | Movable | Keychain is only the fallback. Primary is 1Password, cross platform. Linux secret-tool, Windows Credential Manager cover the fallback. |
| All Claude agents Sage, Apollo, Scribe, Forge, Athena and the rest | Portable | Each machine has its own login. Runs on any operating system. |
| Telegram comms | Portable | Public Bot API over plain web requests. No Apple anything. |
| Browser automation GHL, ChiroHD, Brevo, SKED, Cloudflare, Gmail web | Portable | Chrome DevTools protocol on any operating system with Chrome. |
| Codex execution, transcoding, builds, storage, free and cheap APIs | Portable | All cross platform binaries and web services. |
What actually keeps you on a Mac.
Strip it down and your Mac requirement is almost entirely your own Apple lock in, not the business system:
None of those three are the business system. They are personal conveniences. If you were willing to run all SMS through OpenPhone and cap or hand post the rare big carousel, even you could run the whole fleet on a PC and keep the Mac only as an Apple side device. You probably will not want to give up iMessage, and that is fine. The point is that the requirement is a preference, not a technical wall.
This is the question that matters for scaling. The answer is strong.
A chiropractor buying your system is not buying your Apple account. They get the clinic operations, the content engine, the web automation, the agents, the comms. Every piece of that runs on a Windows PC plus a browser. Walk the list:
That is the whole list. This is a selling point, not a problem. You can tell a chiropractor: run it on the PC you already have. No Apple tax, no Mac to buy.
You do not move the agents onto the Mac. You reach into the Mac from the PC. This is the key unlock.
The old framing said the agents that touch the Mac must live on the Mac. That is not quite right, and your instinct was better. What must happen on the Mac is the execution of an Apple only action, not the brain that decides it. So the architecture is:
Hosts the entire agent fleet with its own Claude login, plus heavy compute: browser workers, transcode, builds, free API helper jobs, bulk files. Headroom for parallel processing, many agents at once, and even running multiple operating systems side by side for experiments or for selling whole setups to other clinics. This is the product.
No reasoning agent lives here. It just keeps a logged in session awake with a thin hands process: a Claude Code or Codex session sitting in the desktop session, holding the screen and accessibility permissions. A PC agent tunnels in over Tailscale and tells it what to do. That hands process can then do anything on the Mac, the GUI, native apps, the iCloud Drive files, reading the iMessage history file.
An agent on the PC decides it needs something Apple only. It opens a tunnel to the Mac mini over Tailscale and hands the instruction to the persistent hands session already running in the Mac desktop session. That session executes it on the real Mac screen and reports back. The brain scaled on the PC, the hands stayed on the Mac, and you never had to host an agent there.
You cannot cold SSH into the Mac and fire GUI clicks. macOS blocks any process that is not inside a real logged in desktop session with screen recording and accessibility permission granted. So two requirements: the Mac stays logged in and awake, and the hands process runs inside that session rather than being freshly spawned over plain SSH. A persistent session that PC agents talk to satisfies both. The fleet already proved this exact pattern with the Argus operator.
What is left that truly pins you to a Mac, day to day, is essentially nothing. The Mac becomes a box you reach into only for the rare genuinely Apple only task.
You were right and I was wrong, so this is on the record.
I had told you one Anthropic account could only run on one machine. That was wrong, and you caught it. You already run Claude Code across many computers on one account without trouble, because each machine holds its own login credential. They do not share one file, so they do not fight.
The two hour lockout this morning was a same machine problem: about ten agents on the one Mac all sharing the one stored credential, racing to refresh a one time use token. First one wins, the rest get locked out. That is a single file collision on one box, not a multi machine issue.