Aiola 2.1 brings the iPhone and iPad app to the App Store, plus desktop changes through version 2.1.1. Desktop gains a Usage popover, Settings in the icon column, Claude Fable 5.2 and Windows fixes. The Aiola changelog lists the November 7 and November 10 releases covered here.
What can you do with the iPhone and iPad app?
Version 2.1.0 makes the iPhone and iPad app public in every App Store country. In desktop Settings, open Connections for its QR code and Download on the App Store button. The button sits next to the Google Play one, so installation starts from your desktop.
The Aiola iPhone app is a full remote for your running desktop. Start threads, run several agents, answer approvals and use terminals from your phone. You can review diffs, commit, push and open pull requests. Voice dictation, photo attachments and push notifications support work away from your desk. Live Activities are available on iPhone.
The phone and tablet app also runs on iPhone Duo and Android phones, tablets and foldables. On iPad and an open iPhone Duo, threads sit on the left and chat on the right. Android tablets and unfolded foldables use that layout too. Folded devices show one screen at a time.
The mobile setup guide explains pairing by QR code over LAN or Tailscale. There is no cloud relay, and the desktop must stay on and awake. Agents run on your desktop.
Analytics, App Logs, Feedback, Tasks, Notebook, GitHub pages, Automations and Calendar remain desktop features. Reviewing a diff remotely does not bring those desktop pages into the phone app.
Where do you check provider usage now?
Version 2.1.1 adds a Usage button at the bottom of the left icon column. It opens a compact popover with every provider's limits. The bars match those in Settings, then Usage, so the quick view uses a familiar presentation.
Open it before starting another agent when you want to check your remaining provider limits. The popover loads when opened and scrolls inside itself. It also reuses information the Usage page already fetched. You can check the bars without opening the full settings page.
The Usage page shows the limits and reset times each provider reports. Aiola uses your own provider subscriptions, with no token markup or model resale. The popover does not give you extra provider capacity.
For example, check the reported limits before assigning another task to Claude Code or Codex. Use that information when choosing where to start work. The change puts the existing bars within reach from the icon column.
Where did Settings move?
Settings now sits at the bottom of the left icon column. Its menu includes Suggest a feature, Report a problem, pinned pages, Help and Settings. The chat list can use the full height of the sidebar.
If you previously looked for Settings alongside the chat list, look in the icon column instead. This is also where you find the menu's help and reporting actions. Open Settings, then Appearance, to see the new layout.
Workspace icons scroll independently when you have many projects. They never cover Usage or Settings. That keeps both controls reachable while you move through a long workspace list.
For daily work, the change separates browsing projects from reaching these controls. Scroll the workspace icons to find a project, then use the fixed controls below them. Your chat list has more vertical room because the Settings menu has moved.
What changed for Claude Code and Windows?
Claude Fable 5.2 is available with Claude Code 2.1.290 and later. Check your Claude Code version when looking for the model. This release adds availability; it makes no benchmark or speed claim.
Claude chats also load project MCP servers from .mcp.json after you approve them in Claude Code. This matches loading in the terminal. Aiola's own MCP server always loads. Project approval remains a condition for loading those project servers.
On Windows, the file viewer and diffs stop replacing letters with symbols or dropping letters in the code font. For example, the fixes address “ª” appearing instead of “a” and “°” instead of “o”. That makes the code you inspect readable while reviewing an agent's changes.
The Windows updates also address provider setup and usage:
- Cursor limits use the account signed in inside Aiola, without requiring the Cursor CLI.
- Antigravity installation handles Windows file locks and explains failures. Pressing Install twice no longer produces an incorrect “already running” message.
- Grok updates through npm, and OpenCode shows the correct upgrade command.
- Claude usage finds Claude Code outside PATH and shows the plan name once.
Files and folders containing characters such as & or % now open in File Explorer. Each turn's changes are recorded on fresh installs even without a Git user name or email.
Other changes tighten specific workflows. Codex's Allow for session covers the same command in the same folder. A different command asks again. Thread summaries are generated without running tools, and long tooltips wrap within their bounds.
Tasks and automations from cloned or pulled repositories start after you save them once in Aiola. Existing ones keep running. Revoking a phone in Connections stops it loading from that desktop immediately.
Read the 2.1.1 release notes for the complete desktop changes.
Try it in Aiola
Your coding agents need the error, report, number or task before they can act on it. Aiola brings that project context into one app to build, run and support your products. Download Aiola, start an agent on your desktop, and review its work from there or your phone.
