Remote Mac

Use when the user says MacBook, Mac Studio, clawmac, moltymac, Molty, Tailscale, or asks to run/check something on one of Peter's Macs.

Peter's Topology

• Primary daily driver: Peter's MacBook Pro, local host steipete-mbp, Tailscale peters-macbook-pro-1.
• Corporate workhorse: Mac Studio, Tailscale peters-mac-studio-1, usually best reached as steipete@steipete-macstudio.local.
• Personal cloud OpenClaw: clawmac (Peter may typo/say crabmac), Tailscale/SSH steipete@clawmac, gateway via LaunchAgent ai.openclaw.gateway, loopback 127.0.0.1:18789, Telegram connected.
• Network split:
  • corporate: Peter's work-managed environment. Treat Mac Studio as the main remote Mac to configure and inspect there.
  • personal: Peter's personal LAN / personal cloud environment, including clawmac.
• Network boundary: clawmac and the personal LAN are unreachable from Peter's corporate Mac. Never use clawmac as a relay or LAN vantage from there.
• Molty: runs on Mac Studio, not moltymac, when healthy. Expected runtime is tmux session openclaw-gateway-watch-main from /Users/steipete/clawdbot with pnpm gateway:watch --benchmark, LAN bind *:18789, Discord bot Molty, plus Slack and Telegram connected.
• moltymac: old/alternate node. If Tailscale shows it offline or SSH times out, do not treat it as the live Molty runtime.

Manager repo source of truth: