This series is about moving from mobile SSH to a durable, repository-backed AI agent workflow.

The starting point was simple: I wanted to keep local Codex work moving when I was away from my Mac.

The deeper question became:

How do I turn remote access into a recoverable, verifiable, long-running agent workflow?

Articles Link to heading

  1. Remote Agent Workflow, Part 1: Remote Mac Terminal for Codex
    Set up phone-to-Mac terminal access with Tailscale, SSH, Termius, tmux, and caffeinate.

  2. Remote Agent Workflow, Part 2: From Remote Shell to Agent Control Plane
    Explain why mobile SSH is useful infrastructure but not a good daily interface for long-running agent work.

  3. Remote Agent Workflow, Part 3: Turning Telegram into a Local Codex Control Plane
    Use a Telegram Bot in polling mode as a lightweight mobile control surface for local Codex tasks.

  4. Remote Agent Workflow, Part 4: In the Repository, Not in the Chat
    Treat the repository as agent memory, operating contract, and verification harness.

  5. Remote Agent Workflow, Part 5: What Still Matters After Codex Mobile
    Reframe the custom workflow after official Codex Mobile: not as a replacement, but as a project-side workflow adapter.

Core Progression Link to heading

Remote terminal
  -> remote runtime
  -> mobile control plane
  -> repository memory
  -> repository harness
  -> workflow adapter

The goal is not to prove that one interface is better than another.

The goal is to make AI coding agents work inside a project workflow that can be resumed, verified, and improved over time.