List all projects accessible to the authenticated user. Returns project names, IDs, status, and task counts.

Create a new project. A TOP-LEVEL project requires product_id; a sub-project (parent_project_id set) inherits its parent's product. Returns the created project with its ID.

Update project details like name, description, or status.

Get details of a specific project including name, description, status, and task statistics.

List all tasks for a specific project. Returns task titles, status, estimates, and time logged.

Get detailed information about a specific task including description, acceptance criteria, time entries, and status.

Create a new task in a project. Returns the created task with its ID.

Update task details like title, description, estimates, or acceptance criteria.

Change the status of a task (todo, in_progress, done). This triggers a real-time notification to users viewing the project.

Log time spent on a task. This triggers a real-time notification showing time was logged.

Search for tasks across all projects by title or description.

Quick workflow for logging completed work: creates a task, marks it done, and logs time in one call. Ideal for recording work that has already been completed.

Mark that you are actively working on a task. This shows other team members that the task is being worked on and by whom.

Mark that you have stopped working on a task (break or switching tasks). Optionally capture your state on the way out: pass note to append a work note and/or resume_context to overwrite the resume block, so the next session can pick up where you left off. Both are recorded as author_kind="ai".

Append a timestamped work note (status update) to a task's activity log. Use this to record progress so a future session can pick up where you left off (e.g. "finished auth handler, tests green, next: wire the callback"). Notes are append-only and never overwrite each other. Set author_kind="human" ONLY when you are relaying a note dictated by the human user; use "ai" (the default) when leaving your own status update.

Add a comment to a task's discussion thread. Unlike work notes (progress journal), comments are for communication and are customer-visible by default. Set author_kind="human" when relaying the user's words; use "ai" (default) for your own.

Set (overwrite) the task's resume context — a single pinned block describing the current state, what is done, what is next, and where to look. This is read first when a work session restarts cold (e.g. via start_working) so you can re-orient immediately. Update it at the end of a work session. Set author_kind="human" only when relaying the user's words; default "ai".

List all products accessible to the authenticated user. Products are top-level containers for organizing related projects.

Get details of a specific product including linked projects, team members, and statistics.

Create a new product. Products are top-level containers for projects. Every product belongs to a customer (customer_id is required) — use an internal/own-company customer for internal work. Find customer ids via list_products (each shows its customer_id).

Link an existing project to a product.