Projects

A project is a container for tasks with its own columns, members, settings and time analytics.

Structure

Projects don't float loose. The hierarchy is:

Life areas are the broad divisions of your life — Work, Health, Side project. Tracks are ongoing streams inside a life area. Projects are the concrete containers tasks live in. See Tracks and life areas.

You don't have to use every level. A single life area with one track is a perfectly reasonable setup, and the levels above the project mostly earn their keep once you're splitting attention across genuinely different parts of your life.

Columns and workflow

Each project defines its own status columns. There is no fixed global list of statuses — a design project and an engineering project shouldn't be forced into the same workflow. Anything that reads a task's status (the board, the VS Code extension's tree, FocusAI) reads the project's real columns.

Views

• Board — columns, drag between statuses.
• List — dense, sortable, good for triage.

Time analytics

Each project aggregates estimated versus actual time across its tasks, which is what feeds the time-by-project breakdown in Performance.

Project settings

Settings → Project controls the defaults new projects inherit: priorities, task types, and templates. Settings → Integrations → Project connects a project to Jira or Todoist.

Sharing

Inside an organization, projects can be shared with teammates. Who can see what is governed by org and team roles — see Roles and permissions.