Cline SDK v0.0.72: durable session state across aborts, MCP startup no longer blocks
Reliability release for the Cline SDK centred on interrupt and restart semantics: prompts queued during a turn survive an abort, session context persists across aborts and hub restarts, and failed queued turns now report run.failed instead of completing silently. A hung or unconfigured MCP server can no longer stall session creation, and LiteLLM traffic moves from the Responses API to Chat Completions.
PUBLISHED2026-08-09
OBSERVED2026-08-11
AGE2d
SOURCES1
- Queued prompts preserved across user aborts and self-aborts; edits made inside the abort window are applied, not dropped
- Session context durable across aborts and hub restarts — interrupted sessions resume with prior state
- Failed queued turns reported as
run.failedrather than silently completing - Hung MCP server no longer blocks session creation; never-configured stdio servers get a 30s initialize budget
- Remote SSE MCP: 401 raises an OAuth authorization prompt instead of failing; pre-registered OAuth clients supported where dynamic registration is unavailable
- LiteLLM routed through Chat Completions instead of the Responses API
- Mid-stream network interruptions before any model output are retried instead of failing the turn
- Vertex ADC token refresh uses the configured fetch (works behind proxies/custom transports)
- Checkpoint diffs include files untracked at snapshot time; checkpoints picked up when git is initialized mid-session
- Plugin settings/contributions centralized in the hub with host-aware snapshots and atomic toggles
- Scheduled run reports carry headers, schedule metadata, durations, and lifecycle error details
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.