Excessive CPU Usage in v2 / Repeatedly failing to parse Claude transcripts

[JoeyEamigh]

Since the v2 upgrade, wakatime has been using ~8% CPU on my 9950X. There is an instance of wakatime running every time I open or edit a file, and it seems it will attempt to parse claude transcripts repeatedly, but fail to do so. With 2 claude instances and vscode running, this spawns 3 wakatime instances, each trying to parse this data.

Environment:

• OS: Arch Linux
• Platform: x86_64

Logs:

This is spammed in the log a few thousand times:

{"level":"warn","now":"2026-03-29T01:18:51-04:00","caller":"ai/claude.go:176","func":"github.com/wakatime/wakatime-cli/pkg/ai.Claude.parseTranscript","message":"failed parsing claude transcript line from: "[claude file]": json: cannot unmarshal string into Go struct field claudeLogLine.toolUseResult of type ai.toolUseResult","version":"v2.0.0","os/arch":"linux/amd64","file":"[editor file]","time":1774761416.714,"plugin":"vscode/1.113.0 vscode-wakatime/30.0.0","lineno":5,"is_write":true}

[mochafreddo]

I think PR #1289 fixes one of the Claude transcript parsing failures, but not all of them.

It should handle:

• json: cannot unmarshal string into Go struct field claudeLogLine.toolUseResult of type ai.toolUseResult

However I’m still seeing parse failures for a different shape after that fix:

• json: cannot unmarshal array into Go struct field toolUseResult.toolUseResult.content of type string

My environment:

• macOS arm64
• Cursor 1.105.1
• vscode-wakatime 29.0.3
• wakatime-cli v2.0.0

This still causes repeated warnings and keeps the extension host hot because the same Claude transcript files are parsed over and over.

It looks like pkg/ai/claude.go still assumes toolUseResult.content is always a string, but some Claude transcript lines now emit content as an array.

I can put together a follow-up PR if helpful. My current thought is to make content tolerant to both string and array shapes, similar to what #1289 did for toolUseResult.

[alanhamlett]

Let's check if v2.0.5 fixes it. To force an update, run this command then restart your IDE:

rm ~/.wakatime/wakatime-cli*

[alanhamlett]

@mochafreddo it's working for you now?

[JoeyEamigh]

No it does not, nor v2.0.5 - seeing unsupported toolUseResult type now, and still quite high CPU - still that ~8%. Only respite is terminating the process. Setting sync_ai_disabled in ~/.wakatime.cfg will also make the CPU usage return to normal.

[alanhamlett]

Is this still happening after v2.0.10?

[alanhamlett]

Closing for now, can re-open if it's still happening in the latest version.