Projects
Long-running containers for related work.
A project is a place for everything a single initiative needs: tasks, artifacts, workflows, and context.
Once you've used Work for a while, you'll notice some requests belong together. A product launch isn't one task. It's a brief, a landing page, a launch post, a press list, a follow-up sequence. Projects are how Busy Bee groups all of that under one roof so the team (and you) have shared context across every task in the initiative.
The project list
Open the Projects tab to see everything you have in flight. A search box up top filters by name or description; an Archived toggle reveals projects you've wrapped up. Click + New project to create one, give it a name, an optional description, and you're in.
📸 Screenshot: the Projects list with several active projects and the New project button visible.
The 5 tabs
Open any project and the right pane breaks the work into five tabs:
- Overview - vitals at a glance. Status, agent assignments, recent activity, top-level deliverables.
- Tasks - every task scoped to this project. Same controls as the Work tab, just filtered.
- Artifacts - completed deliverables in one place: docs, briefs, designs, code, images. Each artifact stays linked to the task that produced it.
- Workflows - multi-step templates you've imported or built. Trigger one with a click and Queen Bee will run the entire sequence.
- Env Vars - secrets and configuration the project's agents can use (API keys, account IDs, etc.). Stored encrypted, scoped to this project only.
📸 Screenshot: a project detail page with the 5-tab bar visible and the Overview tab selected.
Connecting a repo and a team
Two optional but powerful steps. Link a GitHub repository to a project and your developer agents get push access, branch management, and PR drafting, useful for any Builder-mode work. Assign a team (Hive) to the project and Queen Bee will preferentially route tasks to that squad's specialists.
You don't have to wire either up to get value. They unlock specific surfaces once you do.
📸 Screenshot: the project settings panel showing a linked GitHub repo and an assigned team.
Archiving
When a project wraps, click Archive. It disappears from the default list but stays fully accessible: tasks, artifacts, conversations, everything. Toggle Show archived to bring it back into view. Nothing is ever deleted unless you explicitly say so.
Where to go next
Most projects pull in data from somewhere, a CSV of leads, a folder of internal docs, an external system. That's what Data is for.