Keep agency client work in separate workspaces
Aiola puts client repositories, GitHub and client reports beside coding agents in one macOS and Windows desktop app. Keep each client's instructions and agent memory in its own workspace.
Key facts
Open the right client project
Add the retailer storefront and the consultant website as separate workspaces. Keep each client's instructions and agent memory with its repository. If the projects are your own companies, Manage several businesses in one desktop app fits better.
Find the work waiting for you
Central GitHub lists issues and pull requests with each workspace name. Central App Logs and Feedback do the same for client errors and user reports. You check one list instead of a separate dashboard for each client.
Check the change before delivery
Ask an agent to fix the retailer's failing check in a worktree. Run the checks, inspect the diff and open a pull request. Keep the consultant's content changes in a separate thread and branch.
Follow the workflow
- Connect each client repository in Workspace Settings under Git.
- Create workspace agents with each client's role, skills, instructions and memory.
- Use Central GitHub to find pending work, then open the matching workspace.
- Choose Local or Worktree for the thread and ask the agent to make the change.
- Schedule a weekly repository summary, keep the desktop on and awake, and read its run history.
- Read client error reports and feedback in Central before you act.
What to review at the end
- Client instructions stay with the matching repository.
- Each proposed delivery has changes and check results to review.
- Client work is arranged by workspace and connected repository.
See all workflows and guides.
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.