Aiola’s task board tracks work through statuses, including In Progress, Human Review, and Create PR. A workspace board shows one project, while Central combines tasks across projects.
What does the task hand to the agent?
Open Tasks in the workspace that owns the code. A workspace means one project in Aiola. The board and the list show the same tasks. Columns group them by status, and the list shows them in rows.
Write the request on the task. Attach the files that matter and write the acceptance notes you want checked. Set a priority or add labels to describe the work. A task can also hold a scheduled date and time.
Mention a record when the work starts from it. You can mention an app log or a feedback item. A file, another task, an agent, a workspace, an issue, or a pull request can be mentioned too.
The detail panel edits fields, comments, subtasks, links, and attachments. You can attach files and images. The timeline records status changes and other activity. The task chat retains the task context.
Hosted App Logs and hosted Feedback need Pro, or the 7-day trial. The trial is for first-time Pro Monthly customers, and a card is required. Tasks have no public collection key and no ingest endpoint. You create or import them in the app.
Which statuses are on the board?
Tasks move through nine statuses. They are Backlog, Todo, Scheduled, In Progress, Blocked, Human Review, Create PR, Complete, and Cancelled. Use In Progress to start execution and Create PR to begin pull-request creation.
Board columns are these workflow statuses, and you can drag the columns. Aiola saves the board or list choice for that workspace. Central saves its own choice.
| Move the task to | What happens |
|---|---|
| In Progress | The configured agent workflow starts. |
| Human Review | You review the changes and run checks. |
| Create PR | Pull-request creation starts. |
What starts the coding agent?
Moving a task to In Progress starts its configured agent workflow. The move works on the workspace board and in Central.
Configure providers through Central Settings, then Providers. Install the CLI and authenticate in a terminal, then select Re-check in Aiola. An installed provider must be authenticated before you can enable it.
Providers and model availability apply across the app. Workspace defaults select from globally enabled, visible models. Changing a workspace default does not install or authenticate a provider.
Aiola supports Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity. You use your own subscriptions, with no token markup.
Where does the task run?
Each task uses Local mode or Worktree mode. Local runs in the workspace checkout. Worktree runs in an isolated Git worktree. The task can override the workspace default. Choose the mode before you move the task to In Progress.
Open Project Settings, then Tasks, in the owning workspace to set the default for new tasks.
Open Workspace Settings, then Git, and paste the remote URL if the workspace is not connected. The connection is a Git remote. It is not limited to a GitHub-specific field. Under Branches, set a branch prefix. Aiola applies that prefix when an AI workflow creates a branch.
After connection, check the Connected status and remote URL. The page also shows a contribution graph for repository activity.
The same Git page has worktree toggles for other actions. Separate toggles run App Logs, Feedback, and GitHub issue actions in a fresh worktree. Those toggles are not the task run mode.
When does the pull request start?
Move the task to Create PR when you want pull-request creation to start. Review the resulting changes in Human Review first. Run the checks that apply to the change. Compare the diff with the acceptance notes on the task.
You can turn on automatic PR creation under Project Settings, then Tasks. A successful run can then go to Create PR instead of Human Review. Review the diff before merging. On GitHub pull requests, Fix failing checks addresses failed checks from the list or action menu.
GitHub in the workspace operates on the connected repository. Central, then GitHub, combines records from connected workspaces. Each record keeps its owning workspace. Pull-request details include changed files, diff statistics, comments, and a timeline.
Comment on PRs after review is a separate Git setting. Turn it on to post an AI summary after a pull-request review. That setting is separate from the Create PR status. The Chat action on an open pull request is separate too.
How do you see tasks across projects?
Open Central, then Tasks, to work with records from several projects. Each record keeps its project context, and actions target the workspace that owns it.
Central loads workspace task files and maps task IDs back to their workspaces. Equal local task IDs from different projects do not collide.
How do you fill the backlog?
You create tasks in the app, or you import a CSV. Append mode adds records to the current board. Replace mode swaps that board for the file you import.
For example, append a CSV of checkout fixes to an existing backlog. Open the empty-cart task. Attach the relevant files and write the acceptance notes. Choose Local or Worktree. Move the task to In Progress when the request is ready. Review the changes in Human Review and run the relevant checks. Move the task to Create PR when you want a pull request.
Add subtasks or linked tasks when the work has more than one part. Leave comments for decisions you want on the task.
You can undo and redo a deletion with the standard keyboard shortcuts. Those shortcuts apply when focus is outside a text editor.
How do you start on your own project?
Try it in Aiola. The desktop download is free for macOS 12 or later, and for Windows 10 or later. Get it from the download page. Open Tasks in a workspace and move the task when you want the agent to start.
