$ the-wire · showcase
Cline desktop stops false hub-update nag, shows device sign-in code
By RepoJournal · Filed · About AI Agents
9 people shipped this
dependabot
@dependabot
2 cited
saoudrizwan
@saoudrizwan
2 cited
abeatrix
@abeatrix
2 cited
warrenatchison-wk
@warrenatchison-wk
2 cited
John Kennedy
@jkennedyvz
1 cited
malhotra5
@malhotra5
1 cited
dudanogueira
@dudanogueira
1 cited
langchain-oss-model-profiles[bot]
@langchain-oss-model-profiles[bot]
georgeglarson
@georgeglarson
Cline fixed a desktop hub-update false positive that pestered every CLI user on launch, and llama_index tools now keep images and files on Responses API and Gemini function results.
Cline's desktop app will stop showing the "Cline Hub was updated" dialog on every launch and reconnect when the bundled core version matches the CLI's, even if the builds come from different commits [1]. The same dialog now only renders when an update is actually staged to download, and the "Later" dismissal persists, so users no longer hit a dead-end "Update and restart" with no release available [2]. Separately, the device-code sign-in flow now displays the confirmation code in-app instead of a bare spinner, so users can match it against the browser page and won't stall if the verification URI is missing [3].
llama_index tool results that return an `ImageBlock` or `DocumentBlock` were silently dropped before reaching the OpenAI Responses API, so the model answered as if the tool returned only text. Those blocks now make it into the request; the same fix lands for Gemini function responses [4][5]. Weaviate integrations now tag both REST and gRPC clients with an `X-Weaviate-Client-Integration` header (value `llama-index-python/<version>`), best-effort so telemetry never breaks the store [6].
Cline also documented a hook-based replacement for the deprecated `.clineignore`, shipping `sdk/examples/hooks/PreToolUse_ClineignoreGuard.sh` for gitignore-style file blocking [7]. OpenHands bumped its default automation package to `openhands-automation==1.10.0` for local and Docker stacks, reporting "more reliable task outcome results from the agent" [8]. LangChain raised a Pygments transitive constraint in Chroma development dependencies from 2.20.0 to 2.21.0 to clear a published security advisory, plus routine dependency bumps for orjson and langsmith across partner libs [9][10][11].
Action items
- → If you run Cline desktop with the CLI installed, update to a build containing the hub-version fix to stop the repeated update dialog cline/cline [immediate]
- → If you use llama_index with OpenAI Responses API or Gemini tool calls returning images/files, pull the image- and file-preservation fixes run-llama/llama_index [plan]
- → If you use Cline's .clineignore, review the new hook example as the built-in feature is deprecated cline/cline [monitor]
- → Refresh Chroma dev dependencies to pull Pygments 2.21.0 for the security advisory langchain-ai/langchain [immediate]
References
- [1] fix(hub): never prompt about a hub running the same core version ↗ cline/cline
- [2] fix(desktop): show the newer-hub dialog only when an app update is staged, and persist Later ↗ cline/cline
- [3] Show device sign-in confirmation code in desktop app while waiting for browser ↗ cline/cline
- [4] fix(openai): keep images and files on Responses API tool results ↗ run-llama/llama_index
- [5] fix(google-genai): keep images on Gemini function responses ↗ run-llama/llama_index
- [6] feat(weaviate): tag client with LlamaIndex integration telemetry header ↗ run-llama/llama_index
- [7] docs: add .clineignore hook example ↗ cline/cline
- [8] chore: Bump automation default to 1.10.0 ↗ OpenHands/OpenHands
- [9] chore(chroma): bump Pygments security constraint (#40162) ↗ langchain-ai/langchain
- [10] chore(deps): bump orjson from 3.11.6 to 3.12.0 in /libs/partners/fireworks ↗ langchain-ai/langchain
- [11] chore(deps): bump langsmith from 0.10.16 to 0.12.1 in /libs/partners/chroma ↗ langchain-ai/langchain
