Six coding agent CLIs. One Aiola workspace.

GitHub supplies issues and pull requests; Stripe connects checkout revenue with Analytics journeys. Search Console brings search queries and indexing reports into the workspace. Hosted MCP exposes project Analytics, App Logs and Feedback to compatible assistant clients.

Claude Code in Aiola uses the local claude runtime and your Anthropic/Claude account access. Authenticate with the CLI in a terminal, then let Aiola detect it. Start project threads, choose Local or Worktree execution, and inspect changes before committing. Aiola supplies the desktop workspace around that CLI, while the authenticated provider determines available models and account limits.

Codex CLI in Aiola uses the local codex runtime and your OpenAI/ChatGPT access. Complete codex login in a terminal and re-check provider detection. Keep a Codex thread beside work using another supported provider when you want to compare approaches. Select a separate worktree for independent edits, and evaluate the resulting diff and checks before integrating the branch.

Cursor Agent in Aiola connects the cursor-agent CLI using your Cursor account. This integration runs the agent CLI inside Aiola’s project workflow. Authenticate in the terminal, re-check detection, and select the available provider and model in a thread. Your editor can remain part of the development workflow while Aiola organizes project threads, tasks, and review.

Grok CLI in Aiola uses the installed grok binary and your xAI access. Aiola discovers the models exposed by your installed, authenticated CLI; availability depends on its version and your account. Re-check providers when authentication or installation changes. Choose from the discovered models rather than assuming a fixed fallback model roster is bundled with the desktop app.

OpenCode in Aiola uses the opencode CLI and the model-provider access configured within OpenCode. Authenticate using opencode auth login and choose the provider there. Aiola does not sell that model access. The desktop workspace organizes OpenCode threads beside other CLIs. Model selection, authentication and available usage information still differ by provider.

Antigravity in Aiola uses Google’s agy CLI with your Google account access. Run agy in a terminal to sign in, then re-check providers in Aiola. Repositories stay on your machine. Prompts and file context go to your chosen provider through its authenticated CLI.

Install your chosen CLI and authenticate it in a terminal. Then open Central provider settings and select Re-check. The Providers page does not accept provider API keys. An installed provider must be authenticated before it can be enabled. Expand a provider to show, hide, or reorder its models in pickers.

Provider availability is app-wide; workspace defaults choose from that set. Available controls, models, usage fields, and skills differ by provider and account. Central Usage shows provider information where available, including OpenCode Go usage; Zen pay-as-you-go has no usage view. Workspace agents keep their reusable instructions and memory within that workspace.

Connect the workspace repository in Git settings, then use GitHub to work with its issues and pull requests. Central GitHub combines records while retaining the owning workspace. Choose worktree settings for issue actions. Separate settings control issue comments, closure and PR review comments. Review the configured write-back behavior before triggering an action.

Hosted Analytics can connect Stripe per site. Attributed Checkout Sessions need aiola_visitor_id and aiola_session_id metadata. Google Search Console and Bing Webmaster connections are account-level. Map each Analytics site to its property or site in Search Keywords settings. Search Console data is delayed about 48 hours. These integrations belong to Analytics.

Use phone pairing with the same Aiola account on desktop and phone. Open Central Settings, then Connections, and enable Allow LAN connections. Choose Add under Devices and scan the secure QR code. Tailscale candidates are preferred when discovered; LAN provides another route when reachable. Both devices need the same tailnet for Tailscale.

Android is live on Google Play. Aiola for iPhone is available on the App Store. Repositories and agent processes remain on the desktop; the paired phone receives messages and diffs directly. Optional push notifications use notification delivery services.

Compatible assistant clients can connect to Aiola hosted MCP at https://aiola.app/api/mcp using Streamable HTTP and OAuth 2.1. Claude, ChatGPT, and Cursor are documented clients. Hosted tools expose project-scoped Analytics, search, App Logs, and Feedback. Most tools read data; the documented writes update App Log and Feedback statuses.

Aiola supports macOS 12 or later and Windows 10 or later (64-bit). The download is free. Local desktop access excludes hosted features. Hosted Analytics, App Logs, Feedback, hosted MCP and Setup Health need Pro or the 7-day trial. Compare plans on the pricing page.

Use the provider documentation for detection and usage, mobile pairing guide for networking, and MCP connector guide for client setup.