v6.2.1 May 25, 2026 Features and Improvements Agent : Tabnine CLI
:
Provenance & Attribution Enforcement: Enforced provenance and attribution checks in the CLI so code origin constraints apply consistently across environments Tools and Skills : /memory inbox : Added /memory inbox to review, approve, edit, and patch skills extracted automatically from sessions directly inside the CLI. Unified invoke_subagent Tool : Subagent dispatch is now unified under a single invoke_subagent tool, improving reliability and traceability of multi-agent workflows. MCP : Agent definitions now support an auth block for authenticating MCP servers, with support for Google credentials and custom OAuth 2.0 providers. Core Tools List : Shell command validation now enforces a configurable core tools allowlist; use tools.confirmationRequired in settings to always require confirmation for specific tools. Keyboard Shortcuts : CTRL+Shift+G: Keyboard Shortcut to open current prompt or plan in an external editor CTRL+backspace : Word deletion in Windows Terminal Plan Mode : activate_skill Confirmation : Activating a skill now requires explicit user confirmation Content Visibility : Full plan content is now surfaced in the chat when you ask to review or agree on a plan. Silent Model Fallback : Now silently falls back to an available model if the preferred high-reasoning model is inaccessible Workspace Trust Enforcement : Headless mode now enforces workspace trust before loading .env files, preventing credential exposure from untrusted directories. Bug Fixes
Agent:
Fixed issue where the Apply action stripped escaped characters (e.g., """ → "" ) from applied code Fixed submit_change tool description that always required /testbed/ file paths; corrected to apply only during SWE-bench background evaluation ( Analytics: Fixed following bugs: Incorrect Agent user count displayed in the Admin Console Analytics charts appearing empty when viewing the next month Agent analytics data being cleared after upgrade CSV report download error ( MCP Governance: Fixed intermittent 401 error on first auth-server query after node server initialization, which caused all MCP servers to incorrectly fall back to blocked status