Projects

A project is a folder on your computer plus the teams that work on it and a lead. Everything you do inside a project stays with that project: tasks, chat, runs, decisions, reports, files and project memory. Agents and teams belong to the organization and can be reused in any number of projects.

What a project contains

• Folder: where CLI agents read and write files, and where new shells open.
• Teams: the units assigned to the project. Selecting a unit also includes its sub-units, so every member of the unit and its sub-units works on the project.
• Lead: the agent you talk to in the project chat.
• Name, description and color. The lead and agents see the description as context, so use it for the project’s goal and scope.

Everything else is per project. The Office shows only that project’s team, and the Kanban board only its tasks. Organization-wide memory is the one thing shared by all projects (see Memory).

Agents are shared: the same agent can be a member of several projects, but works on one task at a time. In the Office, a member that is busy in another project appears faded and labelled as working in another project.

Project tabs and sections

Open projects appear as tabs in the top bar, like browser tabs: color dot, name, number of running jobs and a close button. Use + for a new project and the project switcher for Open project… and Open folder….

Inside a project, the second row of the top bar holds the project sections, which you can reach with Ctrl+1 to Ctrl+9:

Key	Section	What it is for
1	Chat	Talk to the lead in #general, message agents directly, read task threads. See Chat.
2	Office	The project’s team in the pixel office. See Office.
3	Team	Units, members and lead of this project.
4	Terminal	Agent terminals and shells. See Terminals.
5	Tasks	The Kanban board. See Tasks.
6	Reports	Statistics, task reports, daily report, token usage. See Reports.
7	Decisions	The project’s decision log. See Memory.
8	Browser	An in-app browser for you (agents can’t use it).
9	Files	Uploaded files, agent output and changed files in the folder. See Files.

Ctrl+Tab and Ctrl+Shift+Tab switch between project tabs. You can close the last tab too; you then see the No open project screen with your recent projects.

Creating a project

1. Click + in the top bar, or press Ctrl+P and choose New project or Open folder….
2. Enter a Name and, if you like, a Description.
3. Choose a Folder. If you start from Open folder… and that folder already belongs to a project, that project opens instead.
4. Under Teams, select the units that should work on the project. A live preview shows how many agents will work on it.
5. Leave Project lead on Automatic (team lead) or pick a specific agent.
6. Click Create project.

If you select no team, only the lead replies in chat. You can add teams later in the Team section with Add team, or from a unit’s Add to project… on the Organization page.

To change a project later, double-click its tab, or click the project name in the status bar, to open Project settings.

The project lead

The lead answers your messages in #general, turns them into tasks for project members and reviews finished work. Agentbits picks the lead in this order:

1. The lead you chose in the project settings.
2. The lead of the first assigned unit that has one.
3. The organization lead.
4. The first project member.

The lead does not take unassigned tasks in its own project; it plans and reviews. See Tasks.

Project folder rules

The folder must:

• exist and be a folder;
• not be the Agentbits app folder itself;
• not already be used by another project;
• not be too broad: a drive root, your home folder or a folder that holds Agentbits’ data is refused.

A folder is required when your agents use Claude Code CLI or Codex CLI. Without one, CLI tasks in that project are refused and an amber No folder selected chip appears next to the sections. For Demo and API providers a folder is optional, because those agents don’t edit files.

If a folder is moved or deleted on disk, the project is marked “folder not found” and you choose its new location in the project settings.

Warning: Agents really change files in the project folder, and several agents can edit the same folder at the same time with no conflict handling. Use a git branch or a copy for important work.

Opening projects at startup

When Agentbits starts, it asks Which projects should we open? Projects are sorted by when you last opened them, with search when there are more than six and an Archived group. The tabs from your last session are preselected. Click to select, double-click to open one right away, Enter to open the selected ones.

Tick Don’t ask at startup, open the last open projects to skip this, or change it later in Settings → General → On startup.

Archiving and deleting

Archive closes the project’s tab and stops new work from starting in it; autopilot ignores archived projects. Open it again from the project picker and it is unarchived.

Delete project permanently removes the project’s tasks, runs, chats, decisions, reports, file records and project memory. Agents and teams stay. The project folder and the files in it are never deleted.

There is always at least one project, so the only remaining project can’t be deleted. If you delete the default project, that role moves to the project you opened most recently.

To keep a project but clear part of its history, use Clear memory and history → Manage data in the project settings. See Settings.

Note: Closing a tab only hides the project. Agents keep working in all active projects even with no tab open. To stop work, use Pause all in the top bar or archive the project.