Aiola GitHub

Move reviews toward
a merge.

Issues and pull requests stall when investigation, checks, and agent work live apart. Aiola connects GitHub records to contextual chats, reviews, and fixes. Inspect changes and act on ready pull requests beside your repository.

Download Aiola See pricing

Aiola

Monitor

Tools

Recents

Total Issues

Open

Closed

How it works

Connect or clone a repository

Agent work needs the right repository. Connect a remote in Workspace Settings under Git, or clone a new workspace from Open.

Aiola

Monitor

Tools

Recents

Total Issues

Open

Closed

Inspect an issue or PR

An issue title rarely explains the whole change. Open Issues or Pull Requests to inspect context before starting Chat or a fix.

Aiola

Monitor

Tools

Recents

Total Issues

Open

Closed

Review and act

Reviews stall when checks and decisions live apart. Read changes and checks, then comment, change status, or merge an eligible PR.

Aiola

Monitor

Tools

Recents

What is Aiola?

What is Aiola, in one paragraph?

Reasoning

I’ll inspect the relevant files and trace the current implementation before making a focused change.

Read 1 file, used 1 tool, and thought for 4 steps

Aiola is one desktop app where coding agents work next to your errors, feedback, GitHub, and analytics. Central shows every project.

48 unmodified lines

4949export function Hero() {

5050 return (

5151 <section className="relative overflow-hidden">

52- <h1 className="text-5xl font-bold">Ship faster</h1>

52+ <h1 className="text-5xl font-bold tracking-tight">

53+ One workspace for every product

54+ </h1>

5555 <p className="mt-4 text-lg text-muted-foreground">

56- A dashboard for your repos.

56+ Agents, tasks and shipping in one place.

5757 </p>

Every repository has its own workspace with isolated threads, tasks, automations and knowledge. Central brings projects together so nothing slips. Issues become tasks, then branches and PRs. Recurring maintenance runs on a schedule instead of depending on memory.

+40-13

48 unmodified lines

4949export function Hero() {

5050 return (

5151 <section className="relative overflow-hidden">

52- <h1 className="text-5xl font-bold">Ship faster</h1>

52+ <h1 className="text-5xl font-bold tracking-tight">

53+ One workspace for every product

54+ </h1>

5555 <p className="mt-4 text-lg text-muted-foreground">

56- A dashboard for your repos.

56+ Agents, tasks and shipping in one place.

5757 </p>

22 unmodified lines

2323 <nav className="flex items-center gap-6">

24- <a href="/docs">Docs</a>

24+ <a href="/product">Product</a>

25+ <a href="/docs">Docs</a>

2626 <a href="/pricing">Pricing</a>

2727 </nav>

60 unmodified lines

6161 <p className="text-4xl font-semibold">See plans</p>

62- <span className="text-sm">per month</span>

62+ <span className="text-sm text-muted-foreground">per workspace / month</span>

6363 <ul className="mt-4 space-y-2 text-sm">

Hero.tsx+8-3

Navbar.tsx+12-4

Pricing.tsx+5-1

page.tsx+7-3

globals.css+2-0

providers.ts+6-2

pnpm dev

server

git

alex@studio Aiola % bun test

bun test v1.2.4

✓ src/lib/providers.test.ts (4)

✓ src/lib/detect.test.ts (3)

✓ src/components/toolbar.test.ts (2)

9 pass, 0 fail, 9 expect() calls

Ran 9 tests across 3 files. [412ms]

alex@studio Aiola %

Issues and pull requests

Workspace and Central inboxes

Repository backlogs get scattered. Workspace and Central inboxes offer search, sorting, filters, refresh, bulk actions, workspace pins, and new item notifications.

Issue analysis and fixes

An unfamiliar bug needs investigation before implementation. Analyze or Chat adds repository context, while Fix it starts work on open issues.

Agent pull request reviews

Large pull requests take time to assess. Review PR starts an agent review, with optional summary comments controlled in Git settings.

Diffs and checks

Changed code and failed checks need inspection together. Read file diffs and check results, using split or stacked views.

Fix failing checks

Failed checks can block otherwise ready changes. Start a fix for one failed check or use Fix all.

Comments and record details

Review context gets lost across comments and edits. Read activity and reviews, post comments, edit titles or descriptions, and request reviewers.

Status and merge controls

Finished or paused discussions need clear status. Close, reopen, lock, unlock, choose issue close reasons, set drafts, or merge eligible PRs.

Delete issues or PR branches

Obsolete issues and branches clutter a repository. Delete issues, or close a PR and delete its branch while preserving its record.

Review markers and duplicates

Repeated reports waste investigation time. Scan for duplicates, close matching issues, and mark issues for review or clear review markers.

Work on the PR branch

PR conversations need the correct checkout. Chat and check fixes use the PR branch in a worktree and reuse existing branch conversations.

Write-back and worktree settings

Agent actions should follow your repository workflow. Git settings control summary comments, issue closure, duplicate closure, issue worktrees, and branch prefixes.

Local Git actions

Clone a workspace

Your repository may live outside GitHub. Clone GitHub, GitLab, or Git URLs, and browse accessible repositories after authenticating gh.

Stage, commit, and sync

Local edits still need a commit and remote sync. Stage, unstage, commit, inspect recent commits, fetch, pull, push, or Commit & Push.

Branches and stash

Unfinished changes can interrupt another branch of work. Create branches, merge local branches, stash changes, or pop the latest stash.

Create a pull request

Ready local work needs a reviewable proposal. Create a PR from workspace Git actions with a title and description.

Take an issue through review

Connect the repository in Workspace Settings under Git and open Issues.
Open Chat to investigate an issue, then choose Fix it when ready.
Inspect the resulting changes and run relevant checks.
Create a pull request, review its checks and comments, then merge when eligible.

Problems Aiola solves here

Every bug starts with rediscovering context. Issue Analyze, Chat, and Fix it carry the selected record into repository work.

A pull request is too large to assess quickly. Review PR starts an agent review, and split or stacked diffs support your own inspection.

Failed checks block a merge. Fix all or an individual check fix starts work on the PR branch in a worktree.

Duplicate reports consume the same attention twice. Duplicate scanning and review markers help you sort issues before starting another investigation.

Repository updates require too much switching. Comments, reviewer requests, status controls, and eligible merges are available beside GitHub records.

Common questions

Use Analyze or Chat on an issue, or Review PR for an agent review. Inspect diffs and checks before acting.

Central GitHub combines issues and pull requests across connected repositories. Items keep their workspace context.

Clone a GitHub, GitLab, or Git URL into a new workspace. You can also authenticate the gh CLI to browse your repositories.

Choose Claude Code, Codex, Cursor, Grok CLI, OpenCode, or Antigravity. Use your own provider access against your workspace repository.

Build, ship and fix in one app

Errors, user feedback, GitHub and analytics live next to your coding agents in one desktop app. Every issue becomes a task an agent can take.

Download Aiola

Move reviews toward a merge.

How it works

Connect or clone a repository

Inspect an issue or PR

Review and act

Issues and pull requests

Workspace and Central inboxes

Issue analysis and fixes

Agent pull request reviews

Diffs and checks

Fix failing checks

Comments and record details

Status and merge controls

Delete issues or PR branches

Review markers and duplicates

Work on the PR branch

Write-back and worktree settings

Local Git actions

Clone a workspace

Stage, commit, and sync

Branches and stash

Create a pull request

Take an issue through review

Problems Aiola solves here

Common questions

How do I investigate issues and review pull requests with coding agents?

Can I see GitHub items across repositories?

Can I clone repositories into Aiola?

Which providers can act on my repository?

Build, ship and fix in one app

Move reviews toward
a merge.