Core concepts

Four ideas carry the whole app: profiles isolate who is working, worktrees isolate where, workspaces group what, and the session host keeps it all alive.

Profiles — isolated identities

A profile bundles a complete developer identity: git author name/email, an SSH key, a GitHub token and gh config, agent API keys, and optionally Jira credentials. Secrets live in Windows Credential Manager, never in files. When AIOAT launches an agent or runs git, it injects exactly one profile's identity into that process — nothing global on your machine changes, and your Work agent can't accidentally push as you.

• The active profile shows in the status bar (click it to cycle). Repos and workspaces can be bound to a profile, which then wins for anything launched there.
• Wrong-account guard: each profile lists allowed remote patterns (e.g. github.com/your-org/*). Launching an agent, pushing, or opening a PR against a repo whose origin doesn't match asks for explicit confirmation first.
• Each profile can have a default agent CLI, terminal look, and its own default panel layout.

Repos & worktrees — isolated working copies

Register a repo once (Code → Repositories) and every agent launched on it gets, by default, an isolated git worktree: its own branch (like agent/20260824-1130) checked out in its own folder. Two agents on the same repo never edit the same files; your own checkout stays untouched. When a session ends you can keep the worktree, delete it, or merge its branch through the review flow.

Don't need git at all? Launch with No repo (scratch) — a fresh folder per session — or point the agent at any folder. A scratch session can later be promoted to a real repo (git init + register) with one click when the work turns out to matter.

Workspaces — separate worlds

A workspace groups repos, sessions, settings, automation rules, and its own panel layout. Switch between Client A, Client B and Personal without their agents, repos or notifications mixing. A workspace can be bound to a profile (switching workspace switches identity), can require human sign-off before merges, can mute notifications, and can be exported as a .aioat-workspace file.

The session host — terminals that survive

Terminals don't run inside the window. A small detached process — the session host — owns every PTY. Close AIOAT, reopen it, and your agents are still running with their scrollback intact. The status bar's ● Host dot shows the connection. Agent state (running / waiting for input / idle / done) is inferred live from each session's output and drives the colored dots everywhere in the UI.

Where your data lives