A desktop manager for the OpenCode CLI

OpenCode is an open-source AI coding agent CLI. Find the project at sst/opencode on GitHub. Run OpenCode from the shell and authenticate with opencode auth login. The agent plans and executes multi-step repository changes. OpenCode uses model access you bring: Anthropic, OpenAI or other configured providers. You can choose among providers instead of using one vendor’s subscription.

OpenCode ships a TUI for that single-session workflow. The terminal interface suits focused work in one repository. Prompts, tool calls and file edits stay in one surface. It does not provide a desktop manager across projects and parallel agents, with tools for shipped-product reports. That is the gap an OpenCode GUI fills.

An OpenCode GUI adds a graphical desktop interface above the OpenCode command-line tool. You can run the agent outside its terminal TUI. The CLI and TUI support one session in one checkout. Terminal interfaces make juggling repositories and comparing diffs side by side harder. They also need coordination for OpenCode, Claude Code and Grok working together. Product reports need to reach scoped agent tasks with their context intact.

Aiola is that graphical layer. It turns OpenCode into a local-first desktop workspace for macOS and Windows. Parallel threads, Central and tasks coordinate projects. Cron-style automations run with your existing subscriptions. Web analytics includes AI-bot crawl tracking and AI Assistants referrals; App Logs opens fix threads. Feedback and GSC/Bing indexing reports sit beside the code. Aiola provides a GUI and project tools above your existing CLI. Keep your editor and bring your own model access.

OpenCode's TUI solves the in-terminal experience well. Running OpenCode across repositories or beside Claude Code, Codex, Cursor, Grok CLI and Antigravity adds coordination work. Which project had which run? What did OpenCode change yesterday in the other service? Where is the task you meant to hand off? In a TUI-only workflow that state lives in your head and in a dozen tabs.

An OpenCode manager solves the coordination problem:

• One window shows every project's active threads, recent changes, and pending tasks.
• Threads organize each line of work. Optional git worktrees give concurrent OpenCode sessions separate working files.
• Queued turns let you line up follow-ups without losing context when a long run is still going.
• Sessions restore after restart, so work you left open is still there when you reopen Aiola.
• Task boards hand scoped work to OpenCode and return results for review.
• Automations let OpenCode run on a cron-style schedule with the provider access you already pay for.
• Terminals, a notebook, a canvas, diffs, and a built-in browser sit next to the agent instead of in other apps.

Aiola adds project and agent management above OpenCode’s TUI. Keep the TUI for focused work in one terminal session.

Aiola wraps the OpenCode CLI with the surfaces a multi-project workflow needs:

• Threads: each thread is an independent OpenCode session with chat, file-by-file diffs, branches, a terminal, and a built-in browser. Run several in parallel and split them side by side or lay them out on a canvas.
• Git worktrees: optionally give concurrent OpenCode threads separate working files within the same repository.
• Tasks: a per-project board that can trigger an OpenCode agent and hand the result back as a pull request.
• Automations: schedule recurring OpenCode jobs (triage, checks, summaries) that run on your machine with your own provider access.
• Agent personas and skills: reusable configurations with role, skills, and memory so OpenCode threads start with the right context.
• MCP server: connect tools and data sources the agent can call without leaving the workspace.
• GitHub, App Logs, Analytics, and Feedback: product reports and repository work beside agent threads.
• A central cross-project dashboard so you steer all your projects, not one repo at a time.

Authenticate OpenCode with opencode auth login, then download Aiola and point it at your projects. Pick OpenCode per thread and bring existing access for Anthropic, OpenAI or another supported provider.

Aiola runs OpenCode, Claude Code, Codex, Cursor, Grok CLI, and Antigravity in one app. Bring your own subscriptions. Pick the agent per thread or task without leaving the workspace. Try OpenCode for a refactor, Claude Code for security review, Grok for experiments and Codex for quick fixes. Aiola keeps these agents beside tasks, logs and product reports across projects. Read more about how Aiola orchestrates coding agents.

Aiola brings separate agent GUIs into one app. Six CLIs share threads, tasks, automations and Central. A manager lets OpenCode run beside agents from your existing subscriptions. You can coordinate work without six separate terminal sessions. Related: Claude Code GUI

OpenCode's terminal TUI supports single-session work in one repository. Stay in the TUI if you prefer terminal work, want to evaluate OpenCode first or use only one agent checkout. Authenticate with opencode auth login and point OpenCode at a repository. Check whether the agent fits before adding a manager.

Aiola helps when OpenCode spans repositories or needs context across sessions. It also runs beside Claude Code, Codex, Cursor, Grok CLI and Antigravity. Threads preserve each line of work, and worktrees separate working files. Tasks provide a queue; the central view shows activity across projects. Logs, feedback, analytics and GitHub help turn a shipped-product report into a scoped coding task. Keep the source context attached.

Aiola is also not a cloud runner, a model subscription, or an IDE. It will not replace the provider access OpenCode needs, hide usage limits, or check a change for you. Keep final review, tests, migrations, and merge decisions manual. The GUI coordinates projects and agents. You judge individual diffs.

Aiola runs the OpenCode CLI on your own machine, against your own repositories. Your code stays on your machine and goes to the AI provider you choose. Aiola never uploads it to its servers. There is no cloud runner, compute resale or API-key markup. You bring the provider access OpenCode already uses. Threads, tasks, notes and automations are stored locally. Optional Analytics, App Logs and Feedback send your shipped-product telemetry through Aiola’s cloud. Read more about how Aiola keeps your data yours.

Aiola is free to download. Pro starts at $24/month or $240/year, including 100k events. GUI Lifetime costs $49, $89, or $129 as a one-time payment. Hosted Analytics, App Logs, Feedback, hosted MCP and Setup Health need Pro or a trial; GUI Lifetime excludes them. The 7-day trial requires a card.

Automations run locally while Aiola is open and the desktop is on and awake.

Aiola runs on macOS 12 or later (Apple Silicon and Intel) and Windows 10 or later (64-bit). OpenCode is cross-platform. Download Aiola and authenticate OpenCode. Then point the app at your projects. See pricing for Pro plans and 7-day trial eligibility. Related: download Aiola

Does the OpenCode GUI work on Windows?

Aiola runs on Windows 10 or later (64-bit) and macOS 12 or later (Apple Silicon and Intel). OpenCode is cross-platform; Aiola gives Windows users the same multi-project graphical layer on top of the CLI.