Workspaces

​

What a workspace contains

A workspace is Aiola’s unit of isolation. One workspace maps to one project and holds:

• the local project folder
• project-specific settings
• project chat and threads
• API key
• feedback data
• app log issues
• analytics site configuration
• integrations
• Git and MCP configuration

​

Central views vs project views

Aiola gives you both:

• Per-project pages like /feedback, /app-logs, and /analytics
• Central pages that aggregate data across workspaces

Central pages are useful when you want one place to review feedback or analytics across multiple projects. Project pages are where you configure and act on a single app.

​

What is shared and what is not

Shared across Aiola:

• account
• subscription
• central preferences
• timezone
• installed providers

Scoped per workspace:

• API key
• feedback schema
• app logs data
• analytics tracking site
• Stripe, GSC, and Bing mappings
• Git remote and GitHub behavior
• MCP server configuration
• custom instructions

​

Switching projects

Switching workspaces should be treated as switching products, not just folders. The app keeps each project’s operational setup separate so analytics, feedback, logs, and repository settings do not leak across projects.

​

Folders

Workspace folders organize the left workspace rail without changing the project folders on disk.

​

Create and manage folders

Use the dashed + button at the bottom of the workspace rail and choose New folder. From a folder’s controls, you can:

• rename the folder
• add, replace, or remove a custom folder logo
• delete the folder

Deleting a folder removes the grouping, not its workspaces.

​

Move workspaces and reorder the rail

Drag a workspace onto a folder to add it to that folder. You can also move a workspace back out of a folder. Drag workspace and folder icons to reorder the rail. Folder membership and the rail order are saved together.

​

Where folder data is stored

Folder metadata is local-first. Aiola applies it locally for immediate rendering, then synchronizes the same document to the desktop server. The desktop server persists it in workspace-folders.json so paired mobile clients can read the layout.