Projects and Tasks

Use Projects for lasting context and Tasks for concrete work with shared files.

Projects hold continuing context

A Project belongs to one Workspace and can represent a product, team channel or repository. Projects may be connected to Git, but do not require a repository. A Project can contain many Tasks, each with its own working branch and shared work area.

Tasks hold the work

Create a Task for one objective, such as fixing a bug or building a feature. Authorized collaborators and Sessions on that Task use the same editable files. A Task may have at most one pull request; Sessions do not create separate branches or pull requests by default.

Choose the boundary before you start

• Continue the same objective in the current Task, even if you add another Session.
• Create a new Task for independent work that needs its own files and branch.
• Create a new Project for a different lasting topic or repository context.

Creating a Task does not copy the current Task’s files. Review independent changes before applying them to shared files.