Task Management

Overview

Track your development work with built-in tasks. Create tasks, set priorities and due dates, and let Claude Code update progress as it works. Tasks can be created from the UI, or the AI can create them during sessions.

Creating Tasks

There are two main ways to create tasks:

Via the UI — use the Tasks panel in the project view. Click New Task and fill in title, description, priority, and optional due date.
Via AI — during Claude Code sessions or in the AI Chat, the AI can create and update tasks automatically.

Example Workflow

Create a task "Add login page" with priority High.
Start a session linked to that task.
Claude Code works on the task in the terminal.
When the session completes, Open Poet generates a verification report.
Review and approve — the task moves to Done.

Task Properties

Field	Type	Description
`title`	string	Task title (required)
`description`	string	Detailed description (markdown supported)
`status`	string	`todo`, `in_progress`, `awaiting_approval`, `done`
`priority`	string	`low`, `medium`, `high`, `urgent`
`due_date`	datetime	Optional due date

Status Workflow

Tasks follow a defined lifecycle:

Task lifecycle

todo  ──►  in_progress  ──►  awaiting_approval  ──►  done
                                  │                         │
                                  │         (reject)        │
                                  ◄─────────────────────────┘

todo — default status when a task is created.
in_progress — work has started on the task.
awaiting_approval — work is complete and ready for review. This triggers AI verification document generation.
done — task has been approved and completed.

When a task is rejected from awaiting_approval, it moves back to in_progress so the assignee can address feedback.

Subtasks

Tasks support parent-child relationships for breaking down complex work:

Set the parent_id field to create a subtask under any existing task.
Progress tracking automatically rolls up from subtasks to the parent.
Subtasks can be reordered independently within their parent.

AI Verification

When a task transitions to awaiting_approval, Open Poet automatically generates a verification document using AI. This document provides evidence of task completion based on the session output and code changes.

Task status changes to awaiting_approval.
The system asynchronously calls GenerateVerificationDoc().
AI analyzes session context and produces a completion report.
The reviewer can approve (task moves to done) or reject (task returns to in_progress).

If verification document generation fails, an explicit error is returned rather than a silent fallback.

Task History

Every significant change to a task is recorded in its history log:

Event Type	Description
`task_created`	Initial creation of the task
`status_change`	Status transition (records old and new values)
`priority_change`	Priority update (records old and new values)
`title_updated`	Title was modified
`description_updated`	Description was changed

Each history entry includes an actor field (user or ai) and an optional session_id linking it to a Claude Code session.

Memory Documents

Each project can have a memory document stored as CLAUDE.md in the project root. This file:

Tracks project goals, progress notes, and key architectural decisions.
Is synced to the project directory alongside skills so Claude Code can read it.
Can be edited from the Open Poet UI or directly in the project files.