What is a project?

A project is everything a single initiative needs: tasks, artifacts, workflows, context, and the team that ships it.

In Busy Bee, a project is the long-running home for related work. One project per launch, one per campaign, one per ongoing engagement. You'll spend most of your day inside one or two of them.

The shape of a project

Every project has:

• A name and description - what this initiative is, in your own words.
• Tasks - the individual pieces of work the team has done, is doing, or will do.
• Artifacts - the deliverables that came out of those tasks: docs, designs, code, images, anything shipped.
• Workflows - templated multi-step processes you can fire against the project.
• Env vars - encrypted secrets and config (API keys, account IDs) scoped to this project only.
• An assigned team (optional) - a Hive of agents Queen Bee prefers when routing work here.
• A linked GitHub repo (optional) - required for Builder-mode work, otherwise nice-to-have.

For the actual UI of the Projects tab, what each section looks like and where the buttons are, see the Projects surface page in Introduction.

When to create a project

If a request is one-and-done, "summarize this article," "draft this email", leave it on the Work board as a standalone task. The Work board is built for one-offs.

Spin up a project the moment you have one of these signals:

• Two or more tasks are going to belong together.
• The work spans days or weeks: not minutes.
• You'll want to come back to a deliverable later without hunting through your Work history.
• A teammate needs to follow along. Projects share context; standalone tasks don't.
• You need secrets or env vars specific to this work - those live on the project, not the workspace.

Erring on the side of creating a project is fine. Empty projects don't cost anything, and they make it easy to add the second task without re-establishing context.

Project lifecycle

• Active - the default state. Visible in the project list, runs scheduled work, accepts new tasks.
• Archived - preserved but hidden. All tasks, artifacts, and conversations remain accessible; nothing runs automatically; the project doesn't clutter your default view.
• Deleted - only on explicit confirmation. Removes the project and its contents irrevocably.

Most projects end up archived, not deleted. Archived projects are a great audit trail.

What's next

Now that you know the container, dig into Tasks: the work that fills it.