Mobile App: Manage Sessions and Dispatch Tasks from Your Phone

Download the Claude Code app from the Apple App Store (iOS) or Google Play Store (Android). Open the app, sign in with your Anthropic account, and authenticate with GitHub when prompted. The app indexes your recent repos and displays them with a 'Quick Start' button.

The app works on both iPhone and iPad, adapting the UI to the screen size. On first launch, you'll grant permissions for camera and notification access (optional but recommended). The app stores authentication tokens securely using the platform's keychain, so you only sign in once.

The core mobile workflow is: open the app, tap a repo, and describe a task. For example, tap your backend repo and type 'Check the database migration logs.' Claude Code runs on a cloud server, reads your logs, and reports back—all while you're waiting in line at the coffee shop.

Alternatively, tap 'Dispatch Background Task' to ask Claude Code to run tests or a build and notify you when done. You're not waiting for results; you're just giving Claude Code work to do.

The mobile app shows all your active sessions on your computer(s). You can see what Claude Code is currently working on, check test results in real-time, and approve or reject proposed changes.

Example: you ask Claude Code (on desktop) to refactor a module. The mobile app shows the diff as it's being prepared, so you can approve it from your phone while you're in a meeting.

Enable push notifications in app settings, and Claude Code alerts you when: a dispatched task completes, a test suite finishes, your dev server starts, or a build succeeds/fails. This is critical for on-call rotations—you know immediately when something breaks or when Claude Code has a fix ready.

Notifications are rich and actionable: tap to see results, approve proposed changes, or dismiss. You can tune the frequency—immediate for critical alerts, hourly digest for low-priority tasks, or silent mode during meetings. Notifications work even when the app is in the background, making the mobile app a true on-call companion.

You're on-call. A production alert fires at 11 PM. Open the mobile app, tap your backend repo, and ask 'Check the error logs and fix the database connection issue.' Claude Code reads logs, diagnoses the issue, proposes a fix, and if you approve from your phone, the fix is staged on your workstation.

You get a notification when the fix is ready. Tap to see the PR, and your CI/CD pipeline deploys it automatically.

The mobile app has a chat interface to talk with Claude Code—same as the desktop app, but phone-optimized. You can @-mention files and folders (use search to find them), and Claude Code uses that context to understand your codebase.

The chat is conversational and iterative: ask a question, get an answer, refine, and ask follow-ups. For complex tasks, the mobile app still dispatches the work to cloud servers—you're not trying to run intensive computations on your phone. The mobile chat is for direction, monitoring, and approval, while heavy lifting happens in the cloud.

It's midnight. You're asleep. A production database alert fires. Your phone buzzes: 'Database connection pool exhausted.' You open the Claude Code app in bed and tap your backend repo.

You type: 'Database connection errors in production—what happened?' Claude Code reads your recent deployment logs, identifies a connection leak, and proposes a fix: increasing the pool size and adding explicit connection close calls.

You tap 'Accept Fix' from bed. Claude Code stages the change on your workstation. You get another notification: 'Fix staged and tests passing.' You approve the PR from your phone and go back to sleep. Your CI/CD deploys the fix automatically.

The mobile app is optimized for battery and data. Most work runs on cloud servers; your phone just sends requests and receives notifications. With moderate use (checking status, dispatching tasks), the app uses ~5% battery per hour.

Data usage is minimal because you're not transferring large code files—just text chat and status updates. A typical 10-minute debugging session uses less than 1MB of data. Even on slow 3G or spotty coffee-shop WiFi, the app remains responsive because cloud work is decoupled from your phone's connectivity.

Most mobile app issues are auth or network related. If you can't access a repo, re-authenticate GitHub in app settings. If notifications aren't working, check OS settings—iOS and Android can block app notifications even if enabled in Claude Code settings.

The mobile app logs are available in the app's Settings menu. If you hit an issue, check the logs for error details and consider restarting the app. Most issues are transient network hiccups or temporary auth expirations that resolve with a retry.