Run each Claude Code task in its own thread. A workspace is one project, and workspace chat stays on that repository.
Why several sessions get hard to follow
Several terminal windows can hide which task, branch, and folder you are in. Aiola keeps each thread in the workspace that owns the repository. You choose the execution location on the draft, before the thread exists.
Workspace chat uses that repository, its settings, and its agents. It can also use tasks, GitHub records, App Logs, and Feedback.
One thread for each task
A draft becomes a thread when you send its first message. The thread keeps its original workspace and execution context. An existing thread cannot be reassigned to another workspace.
On Central Home, select a target workspace before you start a draft. That choice scopes files, branches, agents, tasks, App Logs, Feedback, and GitHub mentions. The composer persists the workspace you selected.
A system-wide draft can show a workspace selector in its title bar. Choose before sending so agents, tasks, branches, and files come from that project. A popout opened inside a workspace keeps that workspace fixed.
Use the popout action to open a thread in a desktop window. The window keeps the same workspace, thread, and streaming response. Each real thread has one popout, and opening it again focuses that window. Closing the window does not archive or delete the thread. Hiding the window pauses its periodic refresh. An in-progress streaming response continues. Toggle Always on top in the popout title bar to keep that window above other windows.
Archive is separate from closing a window. It hides the thread from the active list and keeps its messages. Select Unarchive under Workspace Settings, then Data, then Archived Threads. There is no Central archive.
The new-thread shortcut is Command+N. Keybinds use Command on macOS and Ctrl on Windows. Pop out a thread with Command+Shift+O. A system-wide draft popout uses Ctrl+Alt+N.
Choose where the session runs
On a new thread, use Project or new worktree in the composer. That control selects the execution location. Branch controls select the branch or the worktree base and branch actions. The worktrees guide covers this choice for parallel Claude Code sessions.
Confirm the execution location and the branch before the first message. Context-defining choices can lock after the thread starts. Permission mode controls execution approval behavior.
On a task, Local runs in the workspace checkout. Worktree runs in an isolated Git worktree. The task can override the workspace default. Set that default under Project Settings, then Tasks. That page also controls automatic pull-request creation after task completion.
App Logs, Feedback, and GitHub issue actions each have a toggle for a fresh worktree. Those toggles are in Workspace Settings, then Git. Aiola applies the branch prefix when an AI workflow creates a branch. Set that prefix under Branches on the same page.
The pull-request tab shows changed files and diff statistics. Open Review to see the git diff. The Open Review shortcut is Ctrl+Shift+G.
Keep a terminal and a browser nearby
Terminals keeps persistent Split and Canvas layouts for the active workspace. Central Terminals owns an independent canvas. Its top-level modes are Split and Canvas.
Split mode stores panes in a horizontal or vertical tree. You can add, resize, swap, and move panes. Browser and terminal tabs can be reordered or moved between panes.
Canvas cards include a shell, persisted browser tabs, a chat, a file, and an image. The canvas persists positions, sizes, contents, and focus on an infinite pan-and-zoom surface. A columns layout places cards side by side.
The panel beside chat supports Review, browser tabs, Files, and Terminal. Tabs can be reordered and closed. The panel can be expanded, collapsed, or displayed fullscreen beside chat.
Toggle the terminal with Command+J, and open the browser with Command+T. A new chat pane in Terminals uses Command+Shift+N.
Run Claude Code beside other agents
Aiola supports Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity. Provider and model select the local AI runtime for that thread. You can apply a workspace agent, which packages instructions, skills, and memory.
Install the CLI and authenticate it in a terminal. Open Central Settings, then Connections, then Providers. That page does not accept provider API keys. Re-check probes the machine and reads the local authentication state. A failed probe is reported separately from an unauthenticated state.
The page can show installation, version, binary path, authentication, and models. An installed provider cannot be enabled until it is authenticated. You use your own provider subscription, and Aiola adds no token markup.
For Claude Code, run npm install -g @anthropic-ai/claude-code, then run claude login. Choose the provider and model separately on each thread.
Follow tasks across projects
Central Home shows cross-workspace cards for tasks, errors, GitHub, feedback, workspaces, and automations. Today and Upcoming combine scheduled tasks and automation occurrences. Notifications retain workspace ownership. Opening a notification resolves the associated workspace record.
The workspace Tasks page operates on the active workspace. Central Tasks combines project-aware records. Moving a task to In Progress starts its configured agent workflow in both views. Moving it to Create PR starts pull-request creation. Auto-create PR can route a successful run to Create PR instead of Human Review.
Create an automation in the workspace from scratch or from a preset. It runs a saved prompt with a fixed workspace and execution configuration. You can set a provider, a model, a Local or Worktree run mode, and an optional schedule. Automations run on your machine while the desktop app is open.
The detail page reports linked threads, status, duration, output, and errors. A manual automation has no automatic run. Editing stays in the workspace. Central Home and Central Calendar show automation activity across workspaces. Tasks and automation files are local workspace files.
Start two Claude Code sessions
Sign in with Google, Apple, or an email one-time code. Aiola checks this machine for a supported local provider.
Add the repository from the Open screen. Choose Local project, then Browse files, and select the repository root. Or choose Clone from Git for GitHub, GitLab, or a URL. GitHub browsing needs the GitHub CLI. If it is missing or not signed in, choose Use a Git URL instead. The workspace setup docs cover both paths.
Open Central Settings, then Connections, then Providers. Install Claude Code if needed, run claude login, and use Re-check. Enable the provider only after it is authenticated.
Create a draft, select Claude Code, and set the model and permission mode. Set Project or a new worktree, and set the branch. Send the first message to create the thread. Repeat those choices for the second task before you send.
Open a popout when you want the second thread in its own window. Use Terminals for a shell and browser tabs beside a chat card. Open Review when you want the git diff.
Try it in Aiola
Download Aiola free for macOS 12 or later and Windows 10 or later. Open your repository and create two Claude Code drafts with their execution locations set.
