fix(analytics): add SDK 0.2.x Task tools to plan-activity classifier - #587
fix(analytics): add SDK 0.2.x Task tools to plan-activity classifier#587bradbrok wants to merge 1 commit into
Conversation
fa7c95b to
0510b01
Compare
|
Heartbeat maintenance (2026-05-28): rebased onto current Rebased cleanly — no conflicts in Tests: 🤖 Heartbeat maintenance Generated by Claude Code |
0510b01 to
28174a1
Compare
|
Heartbeat maintenance (2026-05-28 ~18:30 UTC): rebased onto current 🤖 Heartbeat maintenance Generated by Claude Code |
28174a1 to
d2eb878
Compare
|
Heartbeat maintenance (2026-05-30): rebased onto current 🤖 Heartbeat maintenance Generated by Claude Code |
TaskCreate/TaskUpdate/TaskGet/TaskList replace TodoWrite in SDK 0.2.82 headless/SDK sessions. Add them to _PLAN_TOOLS so turns using the new Task API continue to classify as "planning". TodoWrite kept for backward-compatibility with historical analytics events.
d2eb878 to
f31cffa
Compare
|
Heartbeat maintenance (2026-05-31): rebased onto current Tests: 🤖 Heartbeat maintenance Generated by Claude Code |
|
Heartbeat maintenance (2026-06-04): Tests: Force-push from this environment is blocked (proxy 403), so no rebase commit here. 🤖 Heartbeat maintenance Generated by Claude Code |
Summary
TaskCreate,TaskUpdate,TaskGet,TaskListtoAnalyticsStore._PLAN_TOOLSso turns from SDK 0.2.82 agents (which use Task tools instead ofTodoWrite) continue to classify as"planning"activity.TodoWriteis kept for backward-compatibility with historical analytics events already in the DB.Why
SDK 0.2.82 (now pinned via #577) replaces
TodoWritewith Task tools in headless/SDK sessions. Without this patch, any planning turn from an upgraded agent would fall through to"general"classification, causing the dashboard and burn analytics to misattribute planning work.Test plan
_PLAN_TOOLSset contains all four Task tool names after mergeTaskCreatecall through a dev agent and verify the analytics row showscategory = "planning"Generated by Claude Code