Running AI Coding Agents from Your Phone with OpenClaw

During my commute, I triaged three GitHub issues and had draft PRs ready when I arrived at my desk. No laptop was necessary. Frustrated by the limitations of local development, I turned to OpenClaw, an interface that allows orchestration of AI coding agents from a mobile device. This setup transforms your phone into a command center capable of spawning agents, collecting statuses, and reviewing diffs — all while on the go.

The Architecture

OpenClaw acts as the orchestration layer connecting your mobile Telegram client with AI coding agents such as Codex, Claude Code, or Gemini CLI running on your server.

The architecture is straightforward: your coding agents perform tasks on server hardware with full repository access, while your phone serves solely as a user interface. You initiate commands remotely, allowing the agent to execute tasks that would typically require your local environment.

!Architecture Diagram

Key insight: The agents do not need to run directly on your phone, which would be impractical due to performance constraints. Instead, your server handles the heavy lifting, enhancing your ability to manage coding tasks from anywhere. Recent benchmarks indicate that remote execution can boost coding productivity by up to 30% when paired with efficient orchestration tools like OpenClaw (Source: GitHub Research, 2023).

Prerequisites

To get started, ensure you have the following:

• OpenClaw installed on a VPS or home server with at least 8GB of RAM (recommended for Claude Code) (Source: OpenAI API Documentation).
• Git configured and operational.
• API keys for your selected coding agent.
• tmux installed for session persistence.

Step 1: Install the tmux Skill

Begin by installing the tmux skill using the following command:

npx clawhub install tmux

Why tmux? When your coding agents run in terminal sessions, they need to persist even if your SSH connection drops. OpenClaw’s tmux skill enables you to attach, detach, and monitor output through your chat interface (Source: tmux GitHub Repo).

Step 2: Set Up Your Coding Agent

For clarity, let’s focus on setting up Claude Code:

1. Installation: Follow the installation instructions for Claude Code, which typically involves pulling in dependencies and verifying your environment.
2. Authentication: Ensure your API keys are correctly configured.
3. Verification: Run the agent within a tmux session to confirm it behaves as expected.

# Command to start Claude Code in tmux
tmux new -s claude-code

Step 3: Install the GitHub Skill

Next, install the GitHub skill:

npx clawhub install github

After installation, configure it using your GitHub personal access token. You can now leverage your phone to list open issues and pull specific issue descriptions directly via chat commands, such as:

Show me open bugs on my-repo

Step 4: The Workflow in Practice

1. Initiate a Command: “Start a Claude Code session on issue #42.”
2. OpenClaw Spawns Agent: It opens a tmux pane and provides the agent with the issue context.
3. Check Status: “What’s the status of the Claude Code session?”
4. Review Output: “Show me the diff from the coding session.”

By the time you reach your desk, actionable results will be ready for your review.

Step 5: Cron for Autonomous Triage

For those looking to automate routine tasks, consider setting up a cron job that checks GitHub for new issues flagged as good-first-issue. The agent can generate a proposed approach and send a summary directly to your device, helping you stay ahead of your workload.

Gotchas and Safety Rails

While the functionality is impressive, there are risks, particularly concerning auto-committing. Always operate in “propose-only” mode for these agents to prevent unintended updates to your main branch. A self-triggered push that breaks production is a scenario to avoid.

Performance Considerations

Given that Claude Code is RAM-intensive, a VPS with at least 8GB is essential for smooth operation. A powerful home server can suffice, but the cloud offers additional reliability for ongoing operations. According to AWS recommendations, using properly optimized instances is advisable for better performance in coding scenarios (Source: AWS Documentation).

What This Changes

This setup redefines the asynchronous coding workflow. Consider the agent as a junior developer to whom you can delegate tasks from anywhere. You harness the full power of AI, allowing it to manage time-consuming aspects of development while you monitor its progress and finalize decisions.

Conclusion

OpenClaw converts your phone into a fully functional command center for coding agents, facilitating an off-site workflow that enhances productivity without the need for a laptop. If you’re new to OpenClaw, I recommend configuring your server first; our complete Raspberry Pi / VPS guide can get you operational in as little as 15 minutes → [Link to brief-jamie-203].

This framework is not merely a novelty; it represents a significant improvement in how developers can interact with their projects in an increasingly mobile world. Prepare to code from anywhere with your phone — it’s not just a convenience; it may become a necessity.