Quick Verdict
AionUi is a free, open-source Cowork application maintained by iOfficeAI. It includes its own ready-to-use agent and can also detect and unify installed command-line agents such as Claude Code, Codex, Qwen Code, OpenCode, Goose, and Gemini CLI. It is not a language model. It is a cross-platform control surface for macOS, Windows, Linux, and WebUI deployments, where users connect cloud API keys, gateways, or local Ollama and LM Studio endpoints.
The official repository showed v2.1.38 as the latest release on July 21, 2026, and the AionUi code is licensed under Apache-2.0. “Free” applies to the application, not to model tokens, servers, messaging channels, or subscriptions required by third-party CLIs. AionUi is compelling for users who want file operations, Office generation, MCP tools, scheduled jobs, and several agents in one workspace. Its breadth also raises the operational stakes: a convenient Full-Auto mode can bypass approvals, and “local SQLite” does not mean prompts or file excerpts stay local when a cloud model or remote MCP server is selected.
Best For
AionUi fits developers who compare several coding agents, technical teams that want a common desktop around multiple providers, and power users automating document, spreadsheet, and file-management work. It can also serve a small self-hosted WebUI for supervised remote tasks. A person who only needs one terminal agent may find the Electron interface and integration surface unnecessarily heavy.
Organizations should define approved models, workspace owners, MCP allowlists, data classifications, spending controls, and log-retention rules before rollout. Team Mode gives agents a shared folder and separate permission dialogs, but parallel writers can still overwrite each other. Use isolated branches, sandboxes, or disposable copies for valuable repositories.
Key Features
- A built-in agent that works without a separately installed CLI, plus automatic detection of more than 20 supported CLI agents.
- Independent parallel sessions and a Team Mode in which a Leader delegates work to Teammates through a shared task board and mailbox.
- Provider support spanning OpenAI, Anthropic, Gemini, AWS Bedrock, Chinese platforms, unified gateways, Ollama, and LM Studio.
- Local application data and a file panel for PDF, Office files, code, Markdown, HTML, images, and diffs.
- Built-in assistants and skills for editable PPTX, DOCX, and XLSX output, with custom assistants, custom skills, and MCP management.
- WebUI and chat-channel access through Telegram, Lark, DingTalk, and WeChat, depending on configuration.
- Cron, fixed-interval, and one-time scheduled tasks, with model, workspace, and reasoning settings per task.
- Per-agent approval dialogs alongside optional YOLO or Full-Auto modes that deliberately bypass prompts.
Use Cases
- Compare Claude, Gemini CLI, Codex, OpenCode, and Goose without changing frontends.
- Give an agent a repository-scoped workspace, let it edit and run tests, then inspect the diff before any commit or release.
- Generate editable presentations, reports, and spreadsheets with built-in Office assistants.
- Organize a controlled folder, analyze tabular files, or run repeatable report tasks on a schedule.
- Monitor supervised work from a browser or messaging channel without granting unrestricted command execution.
Use a fresh test directory first. Never select a home directory, SSH directory, password vault, or entire corporate drive as an agent workspace. Keep secrets in an OS credential store or restricted environment variables, not in prompts, repositories, screenshots, or chat logs.
Pricing
| Item | Cost | What it covers |
|---|---|---|
| AionUi source and desktop/Web app | Free | Apache-2.0 code, subject to license notices |
| Official release downloads | Free | v2.1.38 was latest on July 21, 2026; packages cover major desktop platforms and WebUI |
| Cloud model APIs | Provider pricing | User-supplied keys, quotas, data terms, and token billing |
| Local models | Software may be free | Hardware, electricity, storage, and each model license still apply |
| Remote hosting and channels | Deployment-dependent | Servers, gateways, bot accounts, or messaging services may charge separately |
Apache-2.0 covers AionUi’s repository code. It does not relicense an integrated CLI, model weight, MCP server, proprietary API, or model output. Review every component independently before commercial distribution.
Pros
- One interface for a built-in agent, many CLIs, providers, local models, files, and MCP tools.
- Cross-platform installers and an actively maintained release stream.
- Strong desktop workflow: previews, editable Office output, scheduled tasks, and remote channels.
- Per-agent approval prompts make multi-agent activity easier to inspect than a single blanket permission.
- Apache-2.0 provides a clear, permissive license for the application code.
- Local-provider options can reduce, though not automatically eliminate, external data transfer.
Cons
- Electron and parallel agents can consume substantial memory, CPU, disk, and paid tokens.
- Local storage can be misunderstood; cloud models, MCP servers, web tools, and chat channels receive the data sent to them.
- A shared workspace introduces races, accidental deletion, prompt injection, and conflicting edits.
- Broad integration means more credential setup, provider failures, CLI version drift, and MCP compatibility work.
- Full-Auto and scheduled execution amplify bad commands, unexpected bills, and remote-access mistakes.
- It is a community application rather than a bundled model service with one vendor responsible for every dependency.
Alternatives
| Tool | Better for | Main difference |
|---|---|---|
| OpenCode | Terminal coding agents | Lighter terminal-first workflow without AionUi’s broad desktop and Office surface |
| Goose | Extensible local agents | Focuses on an agent and extensions rather than aggregating many agents in one desktop |
| Cursor | IDE-native editing | More polished editor workflow, but not a general multi-CLI Cowork console |
| Open WebUI | Self-hosted model chat | Stronger chat and knowledge workflows; desktop file agents are not the same focus |
| Dify | Publishing AI apps and workflows | Service orchestration and operations rather than interactive work on a personal computer |
FAQ
Is AionUi itself free?
Yes. The repository and application are Apache-2.0 licensed. Model API calls, servers, messaging platforms, and third-party CLI subscriptions remain separate costs, so configure provider budgets and alerts.
Must I install Claude Code or Gemini CLI first?
No. AionUi ships with a built-in agent. If supported command-line agents are already installed, it can detect and expose them in the same interface.
Does all data stay on my computer?
Not necessarily. Local application data can remain in SQLite, but prompts, file excerpts, search queries, and tool results go to whichever cloud model, MCP server, or messaging service you invoke. Use local models and disable external tools for sensitive work.
Is YOLO or Full-Auto mode safe?
It intentionally skips permission prompts, so it should not be the default. Limit it to an isolated directory, low-privilege account, reversible task, and hard API budget. Require human confirmation for deletion, publishing, credential access, and external side effects.
Can several agents work on the same project?
Team Mode supports a shared workspace, delegation, and per-agent approvals. Shared files can still collide. Assign non-overlapping tasks, use Git branches, review the final diff, and avoid simultaneous edits to critical files.
Does the Apache-2.0 license cover models and MCP servers?
No. It covers AionUi code only. Model weights, APIs, command-line agents, extensions, MCP servers, and generated outputs retain their own licenses and terms.
Bottom Line
AionUi is valuable because it combines a built-in agent, many CLI agents, model providers, local workspaces, Office skills, remote access, and scheduling in one cross-platform control plane. That concentration of capability also concentrates risk. Scope every workspace, isolate secrets, keep approvals enabled, cap API spending, restrict WebUI exposure, preserve logs and version history, and only automate unattended tasks after their commands and rollback path have been tested.