← Back to blog

Connect to a Workspace: New Wizard, No Second Password

On 26 July 2026, MainPath simplified connections to its workspaces with a setup wizard and the shared platform password.

WorkspacesRemote development
Connect to a Workspace: New Wizard, No Second Password

Joining a project with the workspaces available at the time involved several setup steps: a VPN client, the right configuration and credentials. Alongside the MainPath login, there was a separate workspace password. The wizard released on 26 July 2026 brought these steps together and removed the need for that additional password.

Historical context: This article describes that release. Today’s MainPath workspaces run in containers. The VPN, remote desktop and virtual machine details below belong to the architecture used at the time.

The connection dialog guided setup

The wizard divided setup into steps. Navigation showed the current step and let users return to earlier steps without beginning again.

Ubuntu and macOS each had a separate path through VPN setup, client installation and connection. The dialog therefore showed the instructions for the operating system in use.

The platform password replaced a separate secret

Connections now used the regular platform password. Users no longer had to manage a separate workspace password. Windows workspaces no longer required an additional RDP password either.

For the cloud workspaces available at the time, the release also removed the separate VPN login before use after creation.

Work locally or in the cloud?

Entirely your call. We give you the ideal setup for both paths.

Local MainPath Toolbox
  • Git & repos
  • Flutter SDK
  • Node.js
  • Docker

The MainPath Toolbox detects tools and starts everything with one click.

Cloud Remote workspace
  • Ubuntu VM
  • VS Code in browser
  • From anywhere

Ready-made dev environment. No local setup required.

Local work and cloud workspaces were part of the project workflow at the time.

Reachability determined readiness

Connections used a dedicated domain for the VPN and fixed gateway URLs. These were intended to support repeat connections through the same addresses.

A workspace was reported as ready once its agent was reachable. If it was offline, the platform displayed a readable error page instead of the previous raw technical response. The readiness status therefore reflected whether the environment could be reached.

Browser, IDE and remote desktop access were available

The options at the time included VS Code in the browser, JetBrains IDEs and remote desktop over RDP and VNC. There were also macOS machines for building iOS apps. These covered different ways of working, from making changes in the browser to using a familiar development environment.

A shared configuration for project work

The wizard simplified part of the process of joining a prepared environment. Runtimes and tools followed a shared configuration instead of being assembled separately on each computer. This made differences in setup easier to trace.

Separate workspaces with project credentials and data also supported the separation of client projects. At the end of a project, teams could review which environment and credentials needed to be retired.

Plan how your team works today

For project work today, see the guides to choosing a program, working locally and using Git and deployments. They cover the tools and workflows around a project.

Choose how your team will work on the project

Choose a program that suits your team and review how you will manage code and changes together. The guides cover setup and the workflow within your project.

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab