Tasks

Projects & todos

A Project groups related work and mints short ids like ENG-42 from its key. Inside a project, todos move through six statuses — backlog, todo, in_progress, in_review, done, cancelled — in either a list or a drag-and-drop board view. Each todo carries:

Assignee

A human member or an AI employee. New todos default to whoever created them — explicitly clear the picker to leave one unassigned.

Reviewer

Who signs the work off. Moving a todo to in_review notifies the reviewer; the cross-project Review queue collects everything waiting on you.

Priority & due date

Five priority levels and an optional due date, both visible on cards and rows.

Repeat

Daily through yearly cadences. Completing a recurring todo schedules the next occurrence automatically.

Discussion

A comment thread on every todo. Mention an AI employee and it reads the todo plus the thread and replies inline.

Subtasks

Open any todo and use Add a subtask in its panel to break the work into steps. Subtasks are real todos — their own status, assignee, and discussion — nested one level under a parent:

• The parent shows a progress bar and a 2/5 chip wherever it appears; subtask rows carry a ↳ ENG-42 chip that jumps back to the parent.
• One level deep by design — a subtask can't have subtasks of its own, which keeps boards and review flows legible.
• Deleting a parent deletes its subtasks with it.

Who has access

A project is open by default: every Member and every AI employee in the company can edit it. To narrow that, open the project's settings, pick the Access tab, and switch Who has access from "Anyone in the company" to "Only people and AI employees you add". From then on, only the people and AI employees on the list reach the project — no entry, no access.

Use Add to put a Member or an AI employee on the list at "View only" or "Can edit", and Remove to take someone off it again. The setting covers the whole project — the list and board views are two ways of looking at the same project, not separate things to share — and todos and comments inherit it. There is no per-todo setting.

• Restricting a project adds you to the list with "Can edit", so you can't lock yourself out with one click.
• A restricted project always keeps at least one human with "Can edit" — the UI refuses to remove the last one.
• Company owners and admins reach any project in their company. That is the way back in if a project ends up locked down too far.
• On a restricted project you can't assign a todo to someone who lacks access — otherwise they'd get a notification for a todo they can't open.

How AI employees use it

AI employees manage tasks through the built-in genosyn MCP server — list_projects, create_project, list_todos, create_todo, and update_todo — subject to each project's access settings: list_projects only returns the projects an employee can reach, and create_todo and update_todo require "Can edit". When an employee creates a todo it assigns itself by default, and it can pass parentTodoId to decompose a big item into subtasks — so "plan the launch" in chat turns into a tracked checklist you can watch from the Home page.