987: Remote Coding Agents

What It Covers

Wes Bos and Scott Tolinski break down the remote coding agent landscape, covering when and where agents run, hardware options from Mac Mini home servers to VPS rentals, CLI and web interfaces like OpenCode and Cursor Cloud, environment setup requirements, and web search API costs for autonomous agents.

Key Questions Answered

• •Hardware setup: Running agents on a dedicated home machine — a refurbished Mac Mini, old MacBook, or $200 refurbished Dell box — costs far less than cloud services while providing full environment access. Pair it with Tailscale to create a private network accessible from any device, anywhere, without exposing ports publicly or relying on third-party infrastructure.
• •Cursor Cloud agents: Cursor's long-running cloud agents provision Ubuntu boxes with approximately 18GB RAM and a full Chrome browser for visual testing. Agents can run for configurable hour increments, submit pull requests autonomously, and interact with live pages via DOM inspection — but transitioning from cursor.com back to the local editor requires a manual git pull, creating friction.
• •Event-triggered automation: Connecting Sentry error monitoring to Cursor's API key enables self-healing software — new errors automatically trigger a cloud agent that reads error metadata, analyzes the codebase, and submits a pull request fix without manual intervention. Sentry also offers agent monitoring to track token usage and LLM call costs per automated task.
• •Web search API costs: Autonomous agents performing web searches consume budget quickly. Brave Search API charges $5 per 1,000 queries; Exa AI charges $7 per 1,000 but offers 1,000 free monthly requests. A single agent prompt can trigger 7–10 searches simultaneously, meaning free tiers deplete fast on research-heavy tasks requiring external documentation lookups.
• •Port standardization: Assigning each project a fixed port number using the project name in leet speak (e.g., "5ynta_" style substitutions) eliminates confusion when AI agents spin up duplicate processes on incremented ports like 3001, 3002, and 3007. This also prevents browser history collisions, stale service worker registrations, and local cookie conflicts across projects.