Organize 20 AI Coding Agents: Workspaces, Wings & Rooms

Organizing AI coding agents shouldn't mean living in someone else's layout. Here's the full hierarchy atrium uses to keep 20+ sessions findable. Most dev tools give you a sidebar, a folder, maybe a Kanban board — and then expect you to run everything their way. atrium was built the opposite way: organization is the pillar every other decision was made around, and you compose it yourself. This walkthrough goes top to bottom through the whole structure. Workspaces group your projects. Projects map to a folder on disk (and hold their git worktrees). Wings are folders for your rooms. A room is a mosaic that holds any pane type you want — an agent session, a task list, a git view, a browser, the observatory, achievements — split, resized, or stacked as tabs inside a single pane. Then it gets loose on purpose: move a pane to a new room, merge it into another room to create a split automatically, lock a layout so new splits don't resize it, or pin a resident pane into the sidebar across every workspace. If you're running Claude Code, Codex, or a fleet of agents in parallel and losing track of which session lives where, this is the part of atrium that fixes it. Recorded on macOS. ⏱ Chapters 0:00 Why rigid dev tool layouts break with 20 agents 0:43 Workspaces: a container for your projects 1:05 Projects and git worktrees 1:27 Wings: folders for your rooms 1:43 Rooms: a mosaic of any pane type 2:07 Stacking panes as tabs inside one room 2:20 Moving and merging panes between rooms 2:47 Locking a layout so splits don't resize it 3:19 Residents: pinned panes in the sidebar 🔗 Links Try atrium: https://getatrium.dev #AIcoding #ClaudeCode #devtools #AIagents atrium is a resumable development environment for AI coding agents. → https://getatrium.dev