[Bug] TodoWrite todos not displayed: TodoItemSchema requires fields that Claude doesn't send

[GeT-LeFt]

Description

Claude's TodoWrite tool sends todo items with {content, status, activeForm}, but the TodoItemSchema in shared/src/schemas.ts requires priority (enum) and id (string) as mandatory fields. This causes TodosSchema.safeParse() to fail silently, and the web UI never displays any todos.

Expected behavior

Todo items created by Claude's TodoWrite tool should appear in the web UI's todo list panel.

Actual behavior

The todo list is always empty. safeParse() returns { success: false } because:

• priority is required but Claude never sends it
• id is required but Claude never sends it
• activeForm is sent by Claude but not in the schema (rejected by strict parsing)

Root cause

// shared/src/schemas.ts — current (broken)
export const TodoItemSchema = z.object({
    content: z.string(),
    status: z.enum(['pending', 'in_progress', 'completed']),
    priority: z.enum(['high', 'medium', 'low']),    // ← required, but Claude never sends this
    id: z.string()                                   // ← required, but Claude never sends this
})

In hub/src/sync/todos.ts, all three extraction functions use TodosSchema.safeParse() which silently returns null on validation failure.

Suggested fix

Make priority and id optional with sensible defaults, and add activeForm as an optional field:

export const TodoItemSchema = z.object({
    content: z.string(),
    status: z.enum(['pending', 'in_progress', 'completed']),
    priority: z.enum(['high', 'medium', 'low']).optional().default('medium'),
    id: z.string().optional().default(''),
    activeForm: z.string().optional()
})

This is backwards-compatible — existing data with all fields present will still parse correctly.

[github-actions]

Thanks for the clear report. I could verify the main mismatch in the current codebase.

TodoItemSchema currently requires both priority and id, so Claude TodoWrite payloads that only include content and status will fail validation. Both Claude and Codex TodoWrite extraction paths call TodosSchema.safeParse() directly and return null on failure, and I did not find any normalization step that fills those fields before validation. Once extraction returns null, the hub does not persist session todos, so the session summary has no todoProgress and the session list shows no todos.

One detail I could not verify from the code: activeForm does not look like the blocker here. The schema in shared/src/schemas.ts uses plain z.object(...) and is not marked .strict(), so unknown keys are ignored by default.

Relevant code:

• shared/src/schemas.ts:90 - TodoItemSchema requires content, status, priority, and id
• hub/src/sync/todos.ts:28 - Claude TodoWrite input parsed with TodosSchema.safeParse()
• hub/src/sync/todos.ts:50 - Codex TodoWrite input parsed with TodosSchema.safeParse()
• hub/src/socket/handlers/cli/sessionHandlers.ts:96 - session todos only saved when extraction succeeds
• hub/src/sync/sessionCache.ts:111 - stored todos are parsed again; failed parse means session.todos is omitted
• shared/src/sessionSummary.ts:44 - todoProgress is derived from session.todos
• web/src/components/SessionList.tsx:273 - session list only shows todo progress when todoProgress exists
• hub/src/sync/todos.ts:74 - ACP plan extraction does generate a fallback id, but that logic is not used for Claude TodoWrite

---

HAPI Bot