Aiola v2.0.5: OpenCode 2 support, providers found anywhere, and skills for Claude, Cursor and OpenCode

OpenCode 2 is detected and works: OpenCode's 2.x line (Homebrew opencode, npm @opencode/cli) reports opencode v2.x, speaks a new API and requires a server password, so Aiola 2.0.4 greyed the provider out with "Couldn't check login status". Aiola now recognises both lines, starts and authenticates the 2.x server, streams its tool calls, approvals and questions, lists its models, and shows an "OpenCode 2" badge in Settings → Providers.

Providers are found wherever you installed them: The desktop app, the local server and the diagnostics page now share one PATH resolver: your login shell on macOS and Linux (plus launchctl), PowerShell on Windows, with Homebrew, npm, bun, nvm and Cargo locations appended as fallbacks. A freshly installed CLI shows up within 30 seconds without pressing Re-check.

Cursor no longer flips to "Not authenticated" on a stale session: The login check trusts cursor-agent status and keeps the cached model list when the account email is missing.

The Skills page showed nothing for Claude, Cursor and OpenCode: Skills synced from claude.ai live one folder deeper (~/.claude/skills/synced/…) and are now found; Cursor has its own section (~/.cursor/skills, a project's .cursor/skills, and Cursor's built-ins); OpenCode 2 skills are read from its server, since the old debug skill command is gone.

Skills in a Cursor thread: The / menu and the skills panel now list what the Cursor CLI actually loads (Cursor and Claude skills) and label them "Cursor" instead of "Claude".

OpenCode threads get the Aiola MCP tools: (app logs, feedback, tasks, analytics), as Claude Code, Codex and Cursor already did.

OpenCode updates through Homebrew: when that is how it was installed, instead of npm.

Model lists refresh more reliably: OpenCode 2 reports an empty catalog for a few seconds after start; Aiola now waits for it instead of caching an empty list.