@nickbaumann_: My laptop has become a “satellite device” since I started using Codex from my phone. And my Mac mini has become the “ho…

X AI KOLs Following News
codex multi-device workflow ssh remote-development ai-assistant

Summary

A user shares his experience setting up Codex across multiple devices (MacBook, Mac mini, phone) with SSH, creating an always-accessible AI coding assistant that feels like a persistent presence rather than being tied to a single computer.

My laptop has become a “satellite device” since I started using Codex from my phone. And my Mac mini has become the “home.” It’s clunky, but the end state feels more like how we’re going to be working in the near future: I’m currently running the Codex app on 2 devices: 1. my MacBook 2. my Mac mini My laptop isn’t reliably connected to Wi-Fi enough, so I keep a Mac mini on my desk that is always connected. When I kick off new threads from my phone, I start them on the Mac mini. When I’m working from my desk, I run them there too. The cool part is that I’ve added my MacBook and Mac mini as connected devices to each other. That means I can start and resume threads from either device. So if I’m in a meeting but want to continue a thread on my laptop that was started on my Mac mini, I can do that. I’ve also set up mutual SSH for Mac mini <> MacBook, so files are easy to access from either side. It’s not fully seamless yet, but the model works. What this means: - I have an always-on Codex that is accessible from my phone, with its own dev environment - All threads are always accessible from any of the 3 devices - I can run heartbeat threads that stay on 24/7 It’s a little makeshift today, but the shape of it feels very real to me: Codex is no longer tied to whichever computer happens to be open in front of me. It starts to feel like something I can stay connected to across whatever device I’m using.
Original Article
View Cached Full Text

Cached at: 05/15/26, 04:59 AM

My laptop has become a “satellite device” since I started using Codex from my phone. And my Mac mini has become the “home.” It’s clunky, but the end state feels more like how we’re going to be working in the near future:

I’m currently running the Codex app on 2 devices:

  1. my MacBook
  2. my Mac mini

My laptop isn’t reliably connected to Wi-Fi enough, so I keep a Mac mini on my desk that is always connected.

When I kick off new threads from my phone, I start them on the Mac mini. When I’m working from my desk, I run them there too.

The cool part is that I’ve added my MacBook and Mac mini as connected devices to each other. That means I can start and resume threads from either device. So if I’m in a meeting but want to continue a thread on my laptop that was started on my Mac mini, I can do that.

I’ve also set up mutual SSH for Mac mini <> MacBook, so files are easy to access from either side. It’s not fully seamless yet, but the model works.

What this means:

  • I have an always-on Codex that is accessible from my phone, with its own dev environment
  • All threads are always accessible from any of the 3 devices
  • I can run heartbeat threads that stay on 24/7

It’s a little makeshift today, but the shape of it feels very real to me: Codex is no longer tied to whichever computer happens to be open in front of me. It starts to feel like something I can stay connected to across whatever device I’m using.

add the other device on both devices, this is how you can see both sets of threads from both devices

what makes that a blocker?

Similar Articles