Use MainPath from your terminal
Work on your projects with the mp CLI. For local development, mp run-local starts the appropriate environment.
MainPath gives you a prepared development environment in your browser. Work from the same project foundation as your team and keep your changes in the repository.
You decide where to develop. The MainPath Toolbox supports work on your computer, while a workspace provides a prepared environment in the cloud.
A workspace handles recurring setup. Its foundation and access still need to fit your project.
Your chosen environment includes its development tools. Which ones you need depends on your project.
A suitable prepared foundation helps your team avoid setting up the project again on every laptop.
Roles and project membership determine who can work on the project. Credentials belong in the settings intended for them.
Record changes as commits and push them. Your team can then follow the project’s progress.
Open an existing MainPath project or create a new one. For existing code, your agent first checks whether the project is supported.
Start a suitable workspace and open its prepared development environment in your browser.
Develop your application, record changes in the repository and let the pipeline check tests and builds.
Work on your projects with the mp CLI. For local development, mp run-local starts the appropriate environment.
Connect Claude Code, Cursor or Codex to MainPath. Project rules give your agent a shared foundation.
Your code is versioned in the repository. See what changed instead of copying work between computers.
Create a project and see how a workspace fits the way you work with MainPath.
No. You can work locally with the MainPath Toolbox or use a workspace. Both start from the same project foundation. Share changes through the repository.
MainPath provides prepared development environments. Your chosen foundation determines which tools are available. Choose an environment that fits your project.
Yes. Claude Code, Cursor and Codex can connect to MainPath through the agent plugin. Follow your tool’s instructions for connecting and signing in.
A workspace is intended for development. Tests, builds and delivery run through the project pipeline; the application runs in the environment configured for hosting.
macOS build machines are available for iOS pipeline builds. They are a separate part of the build workflow, not an interactive Mac desktop in the workspace. Signing and store uploads need the appropriate developer accounts and credentials.