release aidev SIG 3/5

Cline CLI 3.0.52: queued-prompt and MCP durability fixes from SDK 0.0.72

Adds cline mcp uninstall and lets schedules inherit saved provider settings. The bulk is reliability work inherited from SDK v0.0.72: interrupted turns no longer silently drop queued prompts, a hung MCP server no longer blocks session creation, and LiteLLM traffic moves to Chat Completions so proxy setups work.

PUBLISHED2026-08-09
OBSERVED2026-08-11
AGE2d
SOURCES1
  • cline mcp uninstall removes an installed MCP server
  • Schedules reuse saved provider settings instead of requiring their own
  • Queued messages readable on light-theme terminals; MCP tool results render as text instead of escaped JSON; binary payloads survive expansion; malformed tool payloads degrade instead of throwing
  • Queued prompts preserved across aborts, drained after a self-abort, and the stop surfaced rather than dropping the queue silently (SDK v0.0.72)
  • Session context durable across aborts and hub restarts, so interrupted sessions resume with prior state (SDK v0.0.72)
  • Hung MCP server no longer takes down session creation; unconfigured stdio servers get a 30-second initialize budget (SDK v0.0.72)
  • Remote SSE MCP servers prompt for OAuth authorization on 401; pre-registered OAuth clients supported where dynamic client registration is unavailable (SDK v0.0.72)
  • LiteLLM requests route via Chat Completions instead of the Responses API (SDK v0.0.72)
  • Mid-stream network interruptions before any model output are retried instead of failing the turn (SDK v0.0.72)
  • Vertex ADC token refresh uses the configured fetch, working behind proxies and custom transports (SDK v0.0.72)
  • Checkpoint diffs include files untracked at snapshot time; checkpoints work when git is initialized mid-session (SDK v0.0.72)
  • Scheduled run reports include headers, schedule metadata, durations, and lifecycle error details (SDK v0.0.72)
fixfeatureapi-change

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.