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 Tabnine CLI and IDE Beta Agent under Teams > Features Summary: Tabnine v6.6.0 ships the OpenCode-powered Enterprise Agent CLI to all customers (one installer for macOS/Linux/Windows) and the same agent as a VS Code/JetBrains beta. Enable Agent org-wide, turn on Beta agent under Teams > Features, then use Agent Usage by MCP server and tool. Primary source: https://docs.tabnine.com/main/administering-tabnine/release-notes#v6-6-0

Why it matters

v6.6.0 is the first release where Tabnine's Enterprise Agent CLI (powered by OpenCode) is available to all customers, with one installer for macOS, Linux, and Windows. The same agent ships as a VS Code and JetBrains beta, but it stays off until an installation administrator enables Agent for the organization and an admin or team lead turns on Beta agent under Teams > Features (Agent must already be enabled for that team). Those two switches plus the CLI install are the workflow change: one agent in terminal and IDE. After enablement, the Agent Usage page breaks tool activity down by MCP server and by tool, with active users and a trend against the previous period, so you can keep MCP servers the agent actually calls. Upgrade promptly for security: CVE-2026-64642 (high-severity authorization bypass) is fixed via a Next.js upgrade, team managers can no longer grant Admin through an invitation or user update, and usage reports no longer expose another user's model usage. Installation administrators can also change which analytics events are collected without a new image or pod restart.

Suggested actions

1. Upgrade this Tabnine installation to v6.6.0 now to apply the Next.js upgrade that fixes high-severity CVE-2026-64642 (authorization bypass), stop team managers from granting the Admin role via invitation or user update, and stop usage reports from exposing another user's model usage.
2. Ask the Tabnine installation administrator to enable the Enterprise Agent for the organization, then have an admin or team lead turn on Beta agent under Teams > Features (the Agent must already be enabled for that team).
3. Install Tabnine CLI v6.6.0 with the single installer for this OS (macOS, Linux, or Windows) so the OpenCode-powered Enterprise Agent is available in the terminal, then use the same agent in VS Code and JetBrains as the IDE beta.
4. Open the Tabnine Agent Usage page and review tool activity broken down by MCP server and by tool, including active users and the trend against the previous period; keep only MCP servers the agent actually calls.
5. Have the installation administrator update analytics event filtering for this Tabnine install (v6.6.0 allows changing which events are collected without a new image or a pod restart).

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-6-0-enable-tabnine-cli-and-ide-beta-agent-under-teams-feature and mark Applied, Skipped, or Failed. Proposal id: 95533ef4-68ba-47bd-a722-a1ba2cf8b4f0

Your job

1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.