How to Run AI Coding Agents on Your Phone

You can run Claude Code, Codex CLI, OpenCode, and Gemini CLI on your phone right now. Install Cosyra for iOS or Cosyra for Android, add your API keys, and you get a full Ubuntu container with all four agents pre-installed. No SSH setup, no always-on laptop, no browser tabs that time out. We built this because we kept wanting to check on agent work from the couch or approve a Claude Code permission request while walking the dog, and the existing options were either fragile SSH chains or monitor-only dashboards.

This guide covers why phone-based AI coding works, how each agent runs on mobile, three approaches you can take, and step-by-step setup on Cosyra. If you want the broader context first (any terminal, not just AI agents), the mobile coding terminal pillar sets the stage. 1 hour free on signup, no credit card.

What do the four mobile AI coding agents actually do?

Claude Code is best for deep codebase understanding and multi-file refactors; Codex CLI is best for quick edits and sandboxed execution; OpenCode is the open-source option that works with 75+ providers including local models; Gemini CLI brings Google's 1M-token context window for large codebase navigation. Cosyra pre-installs all four and all four use BYOK, so you pay Anthropic, OpenAI, or Google directly at their standard rates.

Cosyra pre-installs four AI coding agents. All of them use BYOK (bring your own key), you connect your own Anthropic, OpenAI, or Google API key and pay the provider directly at their standard rates. Cosyra itself charges for compute, not AI tokens.

You don't have to pick one. All four are installed in the same container. Start a task with Claude Code, try a different approach with Codex, use OpenCode with a local model for private code. The container state is shared , they all see the same files, same git history, same environment variables.

Why do AI coding agents change the phone equation?

Because you direct the agent in short prompts instead of typing code character by character, and agents do most of the typing for you. Your job shifts to review and approve, which is a reading-heavy, tap-heavy interaction that fits a 6-inch screen. The standard "phone keyboards are too small to code on" objection is fair only when you are the one writing every semicolon. Agents flip that ratio, and the phone becomes viable for real engineering work.

With Claude Code or Codex CLI, you describe what you want in plain language and the agent writes the code, runs the tests, and proposes a diff. Your job is to direct, review, and approve. That interaction model, short prompts in, long outputs out, works on a phone because you're reading more than you're typing.

We think the phone keyboard is fine for agent-driven coding. Most developers who disagree haven't tried it with a properly set up agent that handles the boilerplate. When you're on the train reviewing a PR, or between meetings approving a Codex refactor, the phone is not a compromise. It's the fastest path between "I have five minutes" and "that shipped."

The practical scenarios where this matters:

• Monitoring long-running agent tasks. Claude Code working through a large refactor takes 10-20 minutes. You don't need to stare at a laptop for that. Check in from your phone, approve the permission it's waiting on, and get back to your coffee.
• Quick fixes and reviews. A bug report comes in while you're away from your desk. Open the terminal, point Claude Code at the issue, review the fix, push. Done before you get home.
• Learning and experimentation. You read about a new library on the bus. Spin up a scratch project, ask the agent to scaffold it, poke around. The container persists, pick it up later on any device.

What are the three approaches to AI agents on your phone?

The three approaches are SSH from your phone to a desktop or VPS that runs the agent, installing the agent directly in a local terminal app like Termux, or running the agent in a mobile cloud terminal like Cosyra. Each has a real trade-off: SSH needs an always-on machine, Termux hits x86_64 ABI issues and Android's phantom process killer, and a cloud terminal costs a subscription but removes both problems.

1. SSH from phone to a desktop or VPS

The classic approach: run the agent on a "real" machine and SSH in from Blink Shell (iOS) or Termux (Android). Add Tailscale for networking and tmux for session persistence.

• Upside: Full control, use your existing dev machine, free if you already have the hardware.
• Downside: Requires an always-on machine. If your MacBook sleeps or your VPS reboots, the session dies. Setup takes 15-30 minutes per machine. You're debugging networking instead of writing code.

This is the approach described in most existing guides, SSH + Tailscale + tmux + Blink. It works if you have a reliable server. We used it ourselves for months before building Cosyra.

2. Browser-based cloud IDEs on mobile

GitHub Codespaces and code-server run VS Code in a mobile browser. You get a full editor, terminal, and extensions.

• Upside: VS Code ecosystem, extensions, GitHub-native integration.
• Downside: Browser UIs on mobile are painful, tiny targets, constant mis-taps, Safari's address bar eating screen space. Codespaces free tier gives 120 hours/month (as of 2026-04-15) but the browser experience on a phone is optimized for desktop screens, not 6-inch touch displays.

3. Native cloud terminal with agents pre-installed

This is what we built with Cosyra. A native iOS and Android app that connects to a persistent Ubuntu container in the cloud. Claude Code, Codex CLI, OpenCode, and Gemini CLI are pre-installed. The terminal UI is designed for touch, with larger tap targets, swipe gestures, and a toolbar row for common keys.

• Upside: Zero setup for agents, native mobile experience, container persists across sessions (30 GB storage, session hibernation).
• Downside: Paid service ($29.99/month after free trial). Requires internet, no offline mode. You're running on our infrastructure, not your own.

How do you set up each AI agent on Cosyra?

You set up each agent in about two minutes: install Cosyra, open the app to land in the Ubuntu container, paste the corresponding provider API key into your shell, and run the agent's command (claude, codex, opencode, or gemini). All four are already on PATH. You pay the provider directly at their standard token rates; Cosyra never touches your AI billing.

The setup takes about two minutes per agent. Here's what it looks like.

Step 1: Install and start a container

Download Cosyra from the App Store or Google Play. Create an account (email or Sign in with Apple/Google). The app provisions your Ubuntu container on first launch. In our testing, that took about 15 seconds.

Step 2: Add your API keys

Each agent needs its own API key. In the Cosyra terminal, set them as environment variables. They persist across sessions.

For OpenCode, configure your provider in its config file, it supports 75+ LLM providers including local models. See the OpenCode docs for provider setup.

Step 3: Clone a repo and start coding

That's it. The container has git, node, python, go, rust, and common dev tools pre-installed. Your files persist on 30 GB of storage. If the app goes to background, session hibernation keeps your work intact.

Step 4: Switch between agents in the same container

All four agents are regular CLI tools. Switch between them like you would on a laptop:

What does a real mobile AI coding session look like?

A real session looks like six minutes of phone time: open the app, the container is already running, cd into the project, run claude with a short "review the diff between main and this branch" prompt, read the structured review, approve the PR, and push a small fix. The agent does the heavy reading; you make the decisions. Below is a PR review we ran on the 8:40 AM train before standup at 9.

Here's a scenario we run through regularly. It's 8:40 AM, you're on the train to the office, and a teammate tagged you on a PR that needs review before standup at 9.

1. Open Cosyra on your phone. Your container is still running from yesterday.
2. cd into the project. git fetch && git checkout pr-branch.
3. Run claude and ask: "Review the diff between main and this branch. Focus on security issues and missing tests."
4. Claude Code reads every changed file, checks the test coverage, and gives you a structured review with specific line references.
5. You read the review on your phone, approve the PR with a comment referencing Claude's findings, and push a small fix Claude suggested.
6. You walk into standup at 9 having already reviewed and improved the PR. Total phone time: 6 minutes.

The agent did the heavy reading. You made the decisions. That's why the phone works, it's a command interface for an agent that does the actual typing.

What are the best tips for phone-based AI agent work?

The best tips are: let the agent do the typing with short descriptive prompts, bring an external keyboard only for sessions longer than twenty minutes, use tmux for split panes, commit and push from inside the container instead of switching devices, and rely on session hibernation so you can come back hours later with everything intact. Those five habits cut phone session friction more than any app setting.

• Use agent-first workflows. Don't try to write code character by character. Describe what you want in a sentence, let the agent generate, review the output. This is faster on a phone than manual editing on a laptop for many tasks.
• External keyboard is optional. For sessions longer than 20 minutes, a Bluetooth keyboard helps. For quick reviews and approvals, the phone keyboard is enough. We've shipped production fixes from the waiting room at the dentist with just a thumb.
• Use tmux inside the container if you want multiple terminal panes. Cosyra's container includes tmux pre-installed. tmux new -s work gives you split panes, one for the agent, one for watching test output.
• Commit and push from the container. The container has full git support. Connect your GitHub account via the Cosyra app (see Docs) and push directly.
• Session hibernation saves your state. Close the app, come back hours later, and your terminal session, running processes, and files are exactly where you left them. No reconnecting, no tmux reattach.

How does mobile agent work on Cosyra compare to other mobile coding options?

Cosyra wins on pre-installed AI agents, native iOS and Android apps, persistent cloud compute that does not depend on your laptop being awake, and zero Android phantom-process-killer risk. SSH plus Blink or Termux is cheaper if you already run a server; Codespaces is deeper on GitHub integration; Termux is free but exposes you to ABI issues and phantom process killer on Android 12+. The table below lays them side by side.

Each option wins somewhere. Termux is unbeatable on price and offline capability. Codespaces is free and integrates with GitHub. SSH gives you maximum control. Cosyra's edge is that the agents work out of the box on a phone, no server maintenance, no browser compromises, no ARM compatibility issues. For a deeper look at Claude Code specifically, see our guide on how to run Claude Code on your phone, or the matching walkthrough for Codex CLI. For Google's free-tier agent (60 rpm / 1000 rpd on Gemini 2.5 Pro), see Gemini CLI on your phone; for the open-source agent that pairs with any provider key you already have, see OpenCode on your phone. On iPad with a Magic Keyboard, the workflow opens up with Split View and Stage Manager — covered separately in Claude Code on iPad. On Android, the Bionic-vs-glibc ABI gap and Android 12+ phantom process killer change the setup story enough to deserve its own walkthrough — Pixel, Galaxy, foldables, and Samsung DeX are covered in Claude Code on Android. Zoomed out one level, the question "which AI pair programmer fits a phone" splits into three working paradigms (remote-control your desktop, cloud container, local Termux), compared honestly in AI pair programmer on your phone. And if you arrived here searching for "vibe coding," we untangle the developer version of that term — agents editing your real repo — from the no-code app builders in vibe coding on your phone.

Frequently asked questions