- Reliability 4/20
- No server manifest was provided (marked [not cached]), and there is no tool list, init/handshake trace, or test evidence in the material reviewed. The README frames AionUi as a desktop Cowork app that itself aggregates/manages many external CLI agents and MCP tools ('MCP Unified Management') rather than being a single MCP server whose declared tools can be checked against behavior. Under the static-review rule, reliability is capped at 12 without verifiable CI/test evidence; with zero manifest or handshake evidence at all, this sits at the low end (4).
- Security and permissions 6/20
- The app manages API keys for 30+ platforms, performs local file read/write and code execution, exposes remote access (WebUI, Telegram, Lark, DingTalk, WeChat), and explicitly offers 'YOLO Mode'/'Full-Auto Mode' that the README says 'bypass all permission prompts' for unattended agent action. This is opt-in rather than an unconfirmed default, so it does not strictly trigger the irreversible-default red line, but combined with cron scheduling and multi-channel remote access it creates a large attack surface, and the README discloses no credential-storage encryption, scope isolation, or data-flow details — so a high score is not warranted.
- Maintenance 15/20
- The repo is Apache-2.0 licensed, not archived, and the README shows ongoing releases, active community channels (Discord/WeChat/X), a CONTRIBUTING.md, and a multi-language wiki — signs of a maintained project with clear ownership (star count itself is excluded from scoring). However, open issues stand at 737, a sizeable backlog with no visible triage policy or dedicated security-response channel (e.g., SECURITY.md), which keeps this below full marks.
- Documentation 11/20
- The README is extensive and links to a wiki covering installation, LLM configuration, ACP/MCP setup, WebUI configuration, and FAQs, plus a CONTRIBUTING.md and dev guide; but the linked wiki content itself is outside the reviewed evidence and cannot be verified. The README itself is heavily marketing-oriented (many screenshots/badges/taglines) and lacks concrete technical detail on tool parameters, rate limits, cost, or error handling, and no server manifest accompanies it.
- Setup experience 8/20
- The README gives a simple 3-step end-user flow (download installer or brew install → enter an API key → start coworking) with clear cross-platform support (macOS/Windows/Linux). However this is a full desktop app install, not a standard MCP-server configuration example for a mainstream client (no claude_desktop_config.json or npx/uvx snippet), and no in-repo CI or test evidence was supplied. Per the static-review rule, setup is capped at 15 absent verifiable execution evidence, and the thin evidence here places it in the low-to-mid range.