Enable tools.enableWebFetchTool and upgrade Tabnine CLI to 0.35.0
v6.5.4 keeps Tabnine CLI provenance attribution after VS Code diff or external-editor tool-input edits, and makes direct web fetch the default when tools.enableWebFetchTool is enabled so results are not LLM-hallucinated. Upgrade CLI to 0.35.0 and the matching IDE plugins.Why this loop
Tabnine v6.5.4 (30 Aug 2026) changes two CLI workflows already in use. Provenance & Attribution feedback was dropped after tool inputs were edited via VS Code diff acceptance or an external editor; CLI 0.35.0 keeps that feedback, so keep using those edit paths instead of avoiding them. When tools.enableWebFetchTool is enabled, Web Fetch now defaults to a direct path instead of the previous LLM-mediated path that hallucinated content—so turn that flag on wherever the agent fetches the web. Pair the CLI bump with the published 6.5.4 plugin matrix (Engine 4.340.0, VS Code & Cursor 3.362.0, JetBrains 1.318.1, Eclipse 1.190.2, Visual Studio 2022 & 2026 1.298.17, Skills 0.1.4). On this same 6.5.x train, Plan Mode saving plan files was fixed in 6.5.3 and the WebStorm 2026.2/build 262 startup crash in 6.5.2; do not assume truncated or +15 unlisted changes.
Proposed actions
- Upgrade Tabnine-CLI from 0.33.0/0.34.0 to 0.35.0 and keep Tabnine Skills at 0.1.4 so provenance attribution is retained after tool inputs are edited via VS Code diff acceptance or an external editor.
- Set tools.enableWebFetchTool to enabled in Tabnine CLI so Web Fetch uses the direct-fetch path (now the default when this flag is on) instead of the previous LLM-mediated path that hallucinated content.
- Update IDE plugins to the 6.5.4 matrix: Visual Studio Code & Cursor 3.362.0, JetBrains IDEs 1.318.1, Eclipse 1.190.2, Visual Studio 2022 & 2026 1.298.17, Engine 4.340.0.
- After upgrading, accept or edit a CLI tool input via the VS Code diff UI (or an external editor), then submit provenance/attribution feedback—that signal is no longer dropped in 6.5.4.
- If Plan Mode failed to persist files before 6.5.3, save a plan again on this train; JetBrains users on WebStorm 2026.2 / build 262 should be on plugin 1.318.1 so the 6.5.2 startup-crash fix is included.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costCopilot Chat / Agent mode
DevAgentRadar → GitHub Copilot
You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.
Context
Assistant: Tabnine Proposal: Enable tools.enableWebFetchTool and upgrade Tabnine CLI to 0.35.0 Summary: v6.5.4 keeps Tabnine CLI provenance attribution after VS Code diff or external-editor tool-input edits, and makes direct web fetch the default when tools.enableWebFetchTool is enabled so results are not LLM-hallucinated. Upgrade CLI to 0.35.0 and the matching IDE plugins. Primary source: https://docs.tabnine.com/main/administering-tabnine/release-notes#v6-5-4
Why it matters
Tabnine v6.5.4 (30 Aug 2026) changes two CLI workflows already in use. Provenance & Attribution feedback was dropped after tool inputs were edited via VS Code diff acceptance or an external editor; CLI 0.35.0 keeps that feedback, so keep using those edit paths instead of avoiding them. When tools.enableWebFetchTool is enabled, Web Fetch now defaults to a direct path instead of the previous LLM-mediated path that hallucinated content—so turn that flag on wherever the agent fetches the web. Pair the CLI bump with the published 6.5.4 plugin matrix (Engine 4.340.0, VS Code & Cursor 3.362.0, JetBrains 1.318.1, Eclipse 1.190.2, Visual Studio 2022 & 2026 1.298.17, Skills 0.1.4). On this same 6.5.x train, Plan Mode saving plan files was fixed in 6.5.3 and the WebStorm 2026.2/build 262 startup crash in 6.5.2; do not assume truncated or +15 unlisted changes.
Suggested actions
- Upgrade Tabnine-CLI from 0.33.0/0.34.0 to 0.35.0 and keep Tabnine Skills at 0.1.4 so provenance attribution is retained after tool inputs are edited via VS Code diff acceptance or an external editor.
- Set tools.enableWebFetchTool to enabled in Tabnine CLI so Web Fetch uses the direct-fetch path (now the default when this flag is on) instead of the previous LLM-mediated path that hallucinated content.
- Update IDE plugins to the 6.5.4 matrix: Visual Studio Code & Cursor 3.362.0, JetBrains IDEs 1.318.1, Eclipse 1.190.2, Visual Studio 2022 & 2026 1.298.17, Engine 4.340.0.
- After upgrading, accept or edit a CLI tool input via the VS Code diff UI (or an external editor), then submit provenance/attribution feedback—that signal is no longer dropped in 6.5.4.
- If Plan Mode failed to persist files before 6.5.3, save a plan again on this train; JetBrains users on WebStorm 2026.2 / build 262 should be on plugin 1.318.1 so the 6.5.2 startup-crash fix is included.
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/tabnine-v6-5-4-enable-tools-enablewebfetchtool-and-upgrade-tabnine-cli-t and mark Applied, Skipped, or Failed. Proposal id: 3d577f4b-f9ee-46c0-a04c-1c07f630cedf
Your job
- Restate the change in one sentence.
- Propose a minimal plan for my repo (or a throwaway pilot).
- Implement only what I approve; prefer small diffs and tests.
- Call out risks (permissions, breaking APIs, cost).
Start by confirming you understood the proposal.
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.