fix(claude): emit plan events for TodoWrite during input streaming by TimCrooker · Pull Request #1541 · pingdotgg/t3code

TimCrooker · 2026-03-29T16:19:10Z

What Changed

Claude's TodoWrite tool calls now emit turn.plan.updated events during input streaming so the plan sidebar shows task progress in real-time. The plan event fires alongside the existing tool lifecycle events, not instead of them.

Related fixes:

item.completed activities now forward the data field to the UI, matching item.updated
task.completed entries show up in the work log (previously filtered out with task.started)
Task activity labels use payload.summary when available instead of the generic activity summary
Agent/subagent tool summaries show the human-readable description instead of raw JSON
Plan state persists across follow-up turns so tasks don't vanish when you send a message
Sidebar auto-opens when task steps arrive, respects user dismiss
Sidebar shows "Tasks" outside plan mode, "Plan" inside it -- context-aware, no new UI components

Closes #1539

Why

TodoWrite gets classified as file_change in classifyToolItemType because the name contains "write". It renders as a generic "File change - TodoWrite: {raw JSON}" line in the work log. No turn.plan.updated event gets emitted, so the plan sidebar never activates for Claude sessions. This is core functionality that works for Codex but is completely broken for Claude.

There's an existing PR for this (#1387) that intercepts at tool result time and replaces the normal item.updated/content.delta emissions. This PR takes a different approach:

Doesn't suppress existing events. The plan event fires alongside normal tool lifecycle, so downstream consumers aren't affected.
Streams in real-time. Emitting during input_json_delta means the sidebar populates as Claude writes the input, not after the full round-trip.
Persists across turns. deriveActivePlanState falls back to the most recent plan from any previous turn. Without this, the sidebar clears every time you send a follow-up.
Context-aware labeling. Instead of forcing users into plan mode to see tasks, the sidebar dynamically labels itself "Tasks" vs "Plan" based on whether you're in plan mode. Same component, same UX, just the right label for the context.

Validated with bun fmt, bun lint, bun typecheck, and bun run test (all passing).

UI Changes

Before -- TodoWrite is invisible to the sidebar

Tasks exist but are completely invisible. There is no way to see them.

Before: no sidebar, TodoWrite tasks hidden

After -- Tasks stream in live without plan mode

Tasks are now streamed in real-time and persist between turns.

After: sidebar open showing task steps with status

After -- Button label adapts to context

When the session has tasks but no plan, the button shows "Tasks":

When the session is in plan mode, the same button shows "Plan":

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

When Claude calls TodoWrite, emit turn.plan.updated events during input streaming so the plan sidebar displays Claude's todos the same way it already works for Codex plan steps. Events are emitted alongside existing tool lifecycle events, not as a replacement. Also passes through the data field on item.completed activities to match item.updated behavior, and auto-opens the plan sidebar when plan steps arrive. Closes pingdotgg#1539

coderabbitai · 2026-03-29T16:19:17Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 4879f8fb-81ed-4036-a433-a1f1d0d6482d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Plan state now falls back to the most recent plan from any previous turn when the current turn has no plan activity, so TodoWrite tasks stay visible across follow-up messages. Simplified redundant isTodoTool check.

Copilot

Pull request overview

This PR wires Claude’s TodoWrite tool into the existing plan sidebar by emitting turn.plan.updated events during Claude input streaming, and includes several related UX/data-flow fixes so todos and task activity render consistently in the UI.

Changes:

Emit turn.plan.updated during Claude input_json_delta processing for TodoWrite, without suppressing existing tool lifecycle events.
Persist/restore plan state across turns and auto-open the plan sidebar when plan steps arrive.
Improve work log rendering (include task.completed, prefer task payload summaries) and forward data for item.completed activities.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
apps/web/src/session-logic.ts	Persist active plan across turns; include `task.completed`; adjust task entry label/tone logic.
apps/web/src/session-logic.test.ts	Add coverage for plan fallback and updated work log filtering/label behavior.
apps/web/src/components/ChatView.tsx	Auto-open plan sidebar when an active plan appears (respecting dismiss state).
apps/server/src/provider/Layers/ClaudeAdapter.ts	Emit `turn.plan.updated` events for `TodoWrite` during streamed tool input parsing; improve tool request summaries for agent tools.
apps/server/src/orchestration/Layers/ProviderRuntimeIngestion.ts	Forward `payload.data` for `item.completed` tool lifecycle activities.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

apps/web/src/session-logic.test.ts

apps/web/src/session-logic.ts

Only force "thinking" tone for task.progress, not task.completed, so failed tasks preserve their error tone. Also check payload.detail for task labels since task.completed stores its summary there. Add regression test for failed task.completed rendering.