Projects, rooms & navigation
Understand the hierarchy and find your own work or a teammate’s room.
On this page
How the workspace is organised
| Level | Purpose |
|---|---|
| Organisation | Your team, its membership, and administration |
| Project | A collaboration space containing rooms, shared repositories, and project context |
| Room | A member’s working space, with its own access rules and repository checkouts |
| Repository / conversation space | Files for a particular codebase, or a starting point without files |
| AI chat | A conversation targeting one selected room repository or conversation space |
A project can have no repositories or several repositories. A chat targets one selected repository; selecting another repository does not make the chat operate across all repositories.
The four room panels
- Left: repositories, conversation spaces, AI chats, and teammate navigation.
- Centre: the active AI conversation or file contents. The chat header carries Briefing, Activity & checkpoints, and Providers, so the conversation itself stays prompts, replies, and tool calls.
- Top right: All files and Changes, with task assignment, handoff, and AI review actions.
- Bottom right: the terminal panel, when opened. Interactive shell availability depends on the environment.
Drag the panel dividers to resize the workspace. Each area scrolls independently. On smaller windows, some controls wrap or panels collapse; use their visible controls to reopen them. Room guide offers a short walkthrough.
Public and private rooms
A public project room is visible to members of that project; it is not publicly accessible on the internet. A private room requires explicit room access.
Open the room’s Room privacy & members settings from the project sidebar to review its name, visibility, and members. Only authorised users can change these settings. Review the scope before sharing a repository from a private room: sharing it makes that saved code available to the project.