Aiola's App Store app supports iPhone Duo coding as a full remote for your running Mac or Windows desktop. On the open foldable iPhone, the thread list sits beside the chat; folded, Aiola shows one screen at a time. Start Claude Code or Codex, answer approvals, and review changes while your desktop runs the agents.
What changes when you open iPhone Duo?
Open iPhone Duo and Aiola places your threads on the left, with the selected chat on the right. You can keep the list visible while reading the agent's work. Select another thread to follow a different agent without returning to a separate list screen.
This is the split layout described on Aiola for Tablet. It gives several running threads a place beside the conversation you are reading. You can hide the thread list when you want more room for the open thread.
Fold the device and Aiola returns to the phone layout, showing one screen at a time. The desktop still runs the work in either layout. Opening the device changes how you navigate that work.
For example, keep a bug-fix thread selected while other agent threads remain in the list. Read the fix, inspect its diff, then switch to another thread when it needs attention. The layout shows a thread list and one selected conversation, rather than several open chats at once.
The Aiola for iOS page covers the same App Store app for iPhone, iPad, and iPhone Duo. You do not need a separate Duo app.
What can you do with Claude Code and Codex?
Start a new thread from the phone, choose the project and model, and write your request. Run several agents and move between their threads as they work. Claude Code and Codex use their authenticated desktop sessions and your own provider subscriptions.
Aiola also supports Cursor, Grok CLI, OpenCode, and Antigravity through the desktop. Model choices and provider options depend on the provider you use. Aiola does not resell models or add token markup.
When an agent asks permission, read the request and approve or deny it from the phone. You can also answer the agent's questions. Push notifications let you know when an agent needs attention, so checking progress need not mean keeping the chat open.
Use the remote terminal to run checks on your computer. The terminal belongs to the desktop, even though you type from the foldable. Review the resulting diff file by file before deciding what to keep.
From the same app, you can commit changes, push the branch, and open a pull request. Starting work, answering an approval, and reviewing the result are all part of the remote workflow. The mobile overview describes these controls across phones and tablets.
As a practical workflow, ask Claude Code to fix a bug in one thread. Start a separate Codex thread for another piece of work. Review each diff against its request, use the terminal for relevant checks, and commit the changes you accept.
How do you pair iPhone Duo with your desktop?
Install Aiola on your Mac or Windows PC and set up the coding providers there. Install the App Store app on iPhone Duo. Sign in to both apps with the same Aiola account before pairing.
Then connect the devices:
- On the desktop, open Central Settings, then Connections.
- Turn on Allow LAN connections and wait for connection URLs to appear.
- On Windows, allow Aiola through Windows Firewall on private networks when prompted.
- Under Devices, select Add and keep the QR dialog open.
- Open the phone app's QR scanner and scan that code.
The phone tests the connection addresses supplied by the desktop. On your local network, it can connect over LAN. For Tailscale, sign both devices into the same tailnet. When both routes are available, the phone tries Tailscale before LAN.
There is no Aiola cloud relay between the phone and desktop. Tailscale supplies the encrypted route; the LAN connection is not encrypted. Use the connection URLs Aiola generates rather than guessing a port or typing a fixed address.
If pairing fails, check the account match, network reachability, and Windows private-network permission. Generate a fresh QR code if the previous code is rejected. The phone pairing guide covers connection routes, device status, and removing access.
What stays on the desktop?
Your desktop hosts the repositories, provider logins, terminals, and running agent sessions. It must stay on and awake for remote work. The phone does not run Claude Code or Codex locally. Aiola does not move those agents into a vendor cloud.
Aiola is one app to build, run, and support your products. Its desktop workspace gives agents production errors, user feedback, analytics, GitHub records, and tasks for each project. Agents can only fix what they can read, so that context matters alongside the coding session.
The phone app has a narrower scope. Analytics, App Logs, the Feedback inbox, Tasks, Notebook, GitHub pages, Automations, and Calendar remain desktop features. Opening the foldable does not add those pages to mobile. Mobile Git controls still let you commit, push, and open pull requests.
The direct phone connection also does not mean prompts stay entirely on your computer. Prompts go to your chosen provider, and optional push alerts use notification delivery services. Keep that distinction in mind when choosing what to send to an agent.
Try it in Aiola
Give Claude Code or Codex a clear request on your desktop, then review its progress from iPhone Duo. Download Aiola, pair the App Store app, and open a thread. Keep the desktop awake while you answer approvals, inspect diffs, and run checks from the foldable.
