v4.2.0

agno-agi/agent-uiv4.2.0Jul 20, 2025by ravitemer

AI Summary

This release adds comprehensive VS Code configuration compatibility and enhances the configuration system with support for VS Code-style variables and JSON5.

Key Highlights

Full support for `.vscode/mcp.json` configuration format
Support for 'servers' key alongside existing 'mcpServers' key
VS Code-style environment variable syntax: ${env:VARIABLE_NAME}
VS Code predefined variables support
JSON5 support for config files (comments and trailing commas)

New Features

VS Code Configuration Compatibility with full support for `.vscode/mcp.json`
VS Code-style environment variable syntax: ${env:VARIABLE_NAME}
VS Code predefined variables: ${workspaceFolder}, ${userHome}, ${pathSeparator}, ${workspaceFolderBasename}, ${cwd}, ${/}
JSON5 support for config files (comments and trailing commas)
Seamless migration path for existing `.vscode/mcp.json` files

Full Release Notes


### Added

- **VS Code Configuration Compatibility**: Full support for `.vscode/mcp.json` configuration format
  - Support for `"servers"` key alongside existing `"mcpServers"` key
  - VS Code-style environment variable syntax: `${env:VARIABLE_NAME}`
  - VS Code predefined variables: `${workspaceFolder}`, `${userHome}`, `${pathSeparator}`, `${workspaceFolderBasename}`, `${cwd}`, `${/}`
  - VS Code input variables via `MCP_HUB_ENV`: support for `${input:variable-id}` syntax
  - JSON5 support for config files: comments and trailing commas now allowed
  - Seamless migration path: existing `.vscode/mcp.json` files work directly with MCP Hub

### Enhanced

- **Configuration System**: Enhanced environment variable resolution with VS Code compatibility
  - Proper priority system: predefined variables → process.env → MCP_HUB_ENV
  - Predefined variables available for placeholder resolution but not passed to server environments
  - Comprehensive test coverage for all VS Code variable types and scenarios