Aiola Workspaces

Give every project a home.

Switching repositories means rebuilding context when plans and settings live elsewhere. Aiola keeps each repository’s context, schedules, and agent defaults in a workspace. Pick up the right project with its setup ready.

How it works

01

Add a repository

Starting agent work should not mean rebuilding your project setup. Aiola opens local folders, clones Git repositories, or imports through the terminal.

02

Describe your project

Agents need your project goals and conventions. Project Info edits the profile, brief.md, and existing rules.md, with codebase analysis and Markdown preview.

03

Start from Workspace Home

You need a starting point for today’s work. Workspace Home combines repository chat, today’s calendar, seven-day upcoming schedules, and connected Analytics totals.

Workspace overview

Group workspaces in folders

A long project rail makes repositories hard to find. Aiola groups workspaces into draggable folders you can reorder, rename, remove, or give images.

Follow project completion

It is easy to forget unfinished setup. The completion checklist records progress across project context, GitHub, threads, tasks, automations, and monitoring.

Generate rules and scaffold projects

A new project needs consistent stack choices before coding starts. Onboarding generates editable rules from your selections and can launch a scaffolding thread.

Review notifications and setup health

Missed updates and incomplete integrations delay your next step. Home shows setup findings and workspace notifications you can mark read or dismiss.

Configure Git workflows

Repeated branch and GitHub decisions slow fixes. Git settings control branch prefixes, action worktrees, summary comments, issue closure, and duplicate handling.

Workspace preferences

Manage workspace identity

Similar project names make the wrong repository easy to open. Workspace settings edit names and logos, show paths, and offer deletion cleanup choices.

Choose thread defaults

Choosing the same agent settings for every thread wastes time. Workspace defaults save agents, providers, models, and supported reasoning, permissions, context windows, or Fast Mode.

Configure task execution

Task runs need a consistent checkout and review workflow. Task settings choose Local or Worktree execution and automatic pull request creation after completion.

Configure workspace MCP servers

Your agent workflow may need tools beyond the repository. Workspace MCP settings add, enable, remove, and inspect tools from stdio or HTTP servers.

Connect integrations and project keys

Monitoring needs project connections and credentials. Settings connect Stripe, Google Search Console, and Bing, with project key creation, one-time copying, regeneration, revocation, and last use.

Customize dashboard quick prompts

You should not need to retype frequent starting prompts. Instructions lets you edit text and icons, restore defaults, and show up to five shortcuts.

Write analysis and fix instructions

Repeated analyses and fixes need the same project guidance. Instructions stores separate prompts for GitHub, Feedback, App Logs, Analytics analysis, and indexing fixes.

Restore archived conversations

Past conversations should stay recoverable after clearing your active list. Archived Threads lets you find and restore workspace conversations.

Environment and commands

Scan and edit environment files

Environment differences and exposed secrets are easy to miss. Environment settings scan, edit, compare, reveal, and filter variables, check Git exposure, and add ignore rules.

Create toolbar actions

Running the same setup or test command means repeated typing. Environment settings save named toolbar commands you can run, edit, or delete.

Set up an existing repository

  1. Open a local repository or clone it from Git.
  2. Choose I already have code to start a codebase analysis thread.
  3. Review the generated project context in Project Info and save your edits.
  4. Choose thread defaults and start work from Workspace Home.

Problems Aiola solves here

Switching repositories loses your project context. Workspaces keep each repository’s threads and planning records together. Project Info stores its profile, brief, and rules.

Starting a new project means repeating setup decisions. Onboarding generates editable rules from stack and design selections. It can start a scaffolding thread with those choices.

You need to see what is due without opening every task. Workspace Home shows today’s calendar and upcoming work. Its completion checklist records setup progress.

Repeated prompts produce inconsistent fixes. Instructions saves analysis and fix guidance for project records. Workspace defaults reuse your preferred agent and supported model settings.

Environment differences can derail otherwise working code. Environment settings compare variables across files and check Git exposure. Saved toolbar actions reuse your project commands.

Common questions

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.