Skip to main content
A project groups the work of one product or line of work: its threads, its library folder, its GitHub repositories and its routines. Every thread started in a project gets the project’s brief, memory, folder and repositories, so the teammate knows what it is working on without being told again. A project organizes work; it is not a wall. Teammates, computers, AI accounts, Apps, Secrets and members stay shared by the whole workspace, and a teammate works across all projects. When you need separate people, secrets or billing, make another workspace instead.

​
Create a project

1

Open the dialog

Choose + next to Projects in the sidebar, or New project on the Projects page.
2

Give its website, or start without one

Paste the product’s address: Brigade reads the site, finds its logo, and writes a name and brief with your own AI account. You can choose Fill it in myself at any time, or Start without a website.
3

Check the name and brief

Edit the fields, then choose Create project. Its page opens.
Any member can create and edit a project. Writing the brief uses your Claude or ChatGPT plan on one of your computers; with no computer online, or no usage left, Brigade fills in the site’s own description and says why.

​
The brief

The brief is given to every thread in the project. Say what the product is, who it is for, its stack and how the team works on it, in a few lines:
Customer storefront. Next.js on acme/web, Stripe live. Customers are small coffee shops.
Edit it in the project’s settings (the gear at the top right of its page), under About, along with its name, icon, website and logo.

​
Repositories

In the project’s settings, under Repositories and previews, add the GitHub repositories the project works on. You can only pick repositories your GitHub App reaches (see Apps). A repository can be in several projects. Threads in the project get these repositories to check out by default. The section also shows each repository’s saved preview (see Code and previews). A repository GitHub no longer lets Brigade reach shows as not reachable: reconnect GitHub, or add it to the GitHub App’s installation.

​
Library folder

Each project has a folder in the library, Projects/<name> by default. Its threads are told to save what they make for it there. Change the path in Settings → Library folder; moving or renaming the folder in the library keeps it linked. The folder focuses a teammate, it doesn’t limit it: the teammate still reads every folder of the library it has access to.

​
The project page

Open a project from the sidebar. Clicking it also filters the sidebar’s threads to that project. Its page shows only what is the project’s own:
  • At the top, its name, brief and library folder (click the folder to open it in the library), and a gear for its settings.
  • A box to start a thread in the project.
  • Lists: the project’s lists, with how far each is and what is on.
  • Runs on its own: its playbooks, schedules and triggers, with when each runs and last ran.
Its pull requests and routines are on the Pull requests and Routines pages, filtered on the project (the All link opens them that way).

​
Settings

  • Preferred connections: when several Apps could do the job (two Stripe accounts, two inboxes), the project’s threads use these. It’s a hint, not a permission: what a teammate may use still comes from its access.
  • Code review: The teammate decides whether a pull request needs a review by another teammate, or a review starts Only when someone asks.
  • Email: the project’s mailboxes, such as one for support. You set them up in Mail settings › Mailboxes, the gear at the top of the Inbox (see Email).
  • Memory: what threads learned about the project, loaded by every thread in it. When a thread goes quiet, facts about the project go here rather than into a teammate’s own memory. See Memory.

​
Which threads are in a project

  • A thread started from a project’s page is in that project.
  • In any other new-thread box, a project picker sets it. It starts on the project you picked last in this browser, and it’s never required.
  • A thread started from a routine, or from lines of a list in a project’s folder, is in that project.
  • Mention a project in a message with @ to point a teammate at it. A mention doesn’t move the thread.

​
Move a thread

In a thread’s details, the project menu shows its project, or No project. Pick another project under Move to, or Out of the project. Any member can move a thread. The thread’s next turn gets the new project’s context; earlier turns stay as they were. Its sub-threads, and the schedules that report to it, move with it.

​
Archive or delete

  • Archive takes the project off the sidebar, and nothing new starts in it. Its schedules and triggers keep running: pause them yourself if you want them to stop. The Projects page lists archived projects, and Unarchive brings one back.
  • Delete keeps its threads, routines, library folder and repositories, in no project. Its repository links and its memory are deleted.