Cline SDK v0.0.74: Claude Code provider fix, directional Hub upgrades, token telemetry correction
The Claude Code provider is fixed for agentic use — it declares its own native tools, anchors on the workspace directory, and loads permission rules. Hub daemons upgrade directionally instead of competing. Token telemetry reports disjoint per-request buckets instead of inflating totals ~5x on cache-heavy sessions.
PUBLISHED2026-08-13
OBSERVED2026-08-21
AGE13d
SOURCES1
- Fixed Claude Code provider: declares its own native tools instead of receiving unbridgeable tool definitions; session anchored on workspace directory; loads
~/.claudeand project settings so permission rules apply; file edits under workspace auto-approved, command execution gated by Claude settings - Fixed truncated tool-call JSON being silently repaired into wrong arguments; unterminated strings now rejected
- Fixed strict providers rejecting a turn with "user message must have content" when message content held only empty text parts
- Fixed mid-turn crash on streamed tool calls with non-zero/non-contiguous indexes through LiteLLM's Anthropic passthrough
- Managed Hub daemons upgrade directionally: when another install ships a newer Hub build, hosts attach to the newer daemon and prompt to update instead of repeatedly retiring each other's daemons
- Fixed Hub daemon logging
hub server close failedand exiting non-zero when a client was connected at shutdown; shutdown is now clean run.startedemitted only after the target session resolves, carryingrequestIdandclientIdfor multi-client host correlation- Token telemetry reports disjoint per-request buckets (uncached input, cache reads, cache writes) instead of re-counting the whole cached conversation, which inflated per-task totals ~5x on cache-heavy sessions
- Involuntary Cline logouts (rejected refresh token) are reported instead of clearing credentials silently
- Per-token stream deltas no longer mirrored into telemetry (~97% of all agent event volume with no analytical value)
COMMUNITY
No curated reactions recorded for this event. Facts and takes are kept in separate layers — community context is added by hand, never blended into the record above.