Skip to main content
​
September 19, 2026

​
Folders and favorites saved per account

Folders and favorites are now saved to the account, instead of depending on browser or editor local storage.
  • Personal organization is separate from each workspace’s organization.
  • Folders can be created, renamed, recolored and reordered.
  • Applications and databases can be placed in folders and favorited independently.
  • The dashboard, workflows, CLI, MCP and VS Code extension all use the same persisted organization.
  • The project list and Flow show the same folder and favorite state; Flow’s own canvas groups remain local and independent.
  • Actions are logged to activity history, including when performed via an API key.
Flow’s groups remain a separate thing: they organize elements on the local canvas. There’s no sync or migration between Flow groups and resource folders.

​
Restart flags: reinstall dependencies and force build

Restart Application now accepts two optional body fields:
  • reinstall_dependencies reinstalls the application’s dependencies from scratch, ignoring the install cache — the same as “Reinstall dependencies” in the dashboard’s file manager.
  • force_build runs the application’s build command again even if no source file changed since the last build — the same as “Force build” in the dashboard.
This replaces the separate dependency-install route. Sending either flag counts one slot against the plan’s hourly deploy limit.

​
VS Code extension 1.0

The Vertra Cloud VS Code extension reaches version 1.0, available on the VS Code Marketplace and Open VSX, plus a .vsix file for manual installation.The vertracloud.config file in the linked folder now gets dedicated support: field completion, hover descriptions and inline warnings when a value is missing or malformed. Real-time logs now go to an editor output channel instead of an integrated terminal.The rest of the application management actions remain available on the dashboard.See Manage Vertra Cloud from VS Code for the full list of features.