VSCode 0.840.7 Release Notes
New Features
- Added `/settings` built-in slash command to quickly open extension settings from chat
- Added connectivity check to Augment servers before completing login to surface network issues early
- Added recovery of forked conversations so the parent conversation's exchanges leading up to the fork point are restored alongside the forked exchanges
Bug Fixes
- Fixed auth header lookup being incorrectly attempted for stdio MCP servers
- Fixed MCP OAuth and env-var secret key casing to use uppercase consistently
- Fixed token counting failures with gpt-tokenizer by adding character estimation fallback
- Fixed prompt enhancer not receiving conversation context in webview
- Fixed plan mode tools incorrectly appearing in cloud agent sessions
- Fixed dropped code selection when sending a chat message after clicking into the chat input
- Fixed settings drawer missing padding on narrow viewports
- Fixed first line of chat code blocks being clipped under the sticky header
- Fixed pinned open files not being included in retrieval context or surfaced to the agent
- Fixed update notifications pointing pre-release users at stable versions instead of newer pre-release builds
- Fixed repository allowlist rejecting Bitbucket Server URLs with ports, bare hostnames, or `/scm/` / `/git/` path prefixes
- Fixed MCP OAuth refresh failing when the authorization server omitted `refresh_token` from a refresh response
- Fixed MCP server headers being lost when exporting servers via "Copy JSON"
- Fixed checkpoints not being created in some conversations after conversation-ID migration
- Fixed checkpoint display index being off-by-one (first checkpoint showed as "Checkpoint 0")
- Fixed the Edits tab dropping updates during bursts of refresh dispatches
- Fixed summarized text being shown as the user message when recovering summarized conversations
- Fixed stale local git repository info (branch, remote, root) being injected into the GitHub API tool description and cached for an hour
- Fixed noisy "Failed to load hooks configuration" toast appearing on webview open for users who had never configured hooks
Improvements
- Added 'service unavailable' to retryable gRPC error patterns for improved connection resilience
- Improved accessibility across common UI components (buttons, navigation, dropdowns, text areas)
- Improved error messages by surfacing fetch error cause details (code, message) in logs and user-facing errors
- Improved data table column sizing and layout
- Show a recovery banner when no chat history is found in the backend for the current conversation
- Show the prompt enhancer (rewrite prompt) button while an exchange is in progress
- Surface hooks load errors inline on the Hooks settings page
- Sort built-in commands alphabetically in Settings → Commands
- Make the stream interruption error message generic instead of incorrectly attributing interruptions to token limits