Markdown

Documentation

Documentation

Guides for getting started, daily work, and publishing your projects on MainPath, split into a beginner path and a developer path.

The quickstart takes you onto MainPath in four steps: CLI, agent plugin, project, publishing. If Git, the terminal, and servers are new to you, continue with the For beginners path; if you develop every day, take the shorter For developers path. Both link to the same reference below, where each topic is described once.

How the work fits together

You develop on your own computer or in a remote workspace, together with your AI agent. A push to main starts the pipeline: it checks, builds, and automatically updates the test environment. You try your changes, then approve the version for production.

From the first prompt to release
flowchart TB
  accTitle: From the first prompt to release
  accDescr: You and your AI agent work locally or in a workspace. After a push to main, the GitLab pipeline checks and builds your project. The test environment updates automatically. You approve production yourself.
  code["You + your AI agent<br/>Locally or in a workspace"]
  pipeline["GitLab pipeline<br/>Check · Build · Version"]
  dev["Test environment<br/>Try your changes"]
  prod["Production<br/>For your users"]
  code -->|Push to main| pipeline
  pipeline -->|automatically| dev
  pipeline -->|your approval| prod
  class pipeline accent
  class prod success

You stay in control of the release. Start production with the manual job in the same pipeline. Dev and production servers are separate, with a firewall and HTTPS. You can configure backups and monitoring for operations; connect and enable Sentry to collect errors there. Architecture explains how the technical pieces fit together.

The search at the top left covers headings and text of every page.

Quickstart

For beginners

What is MainPath?

MainPath takes care of repositories, pipelines, servers, and deployments so that you can concentrate on your application.

Terms you will come across

Repository, commit, pipeline, server, Docker, and workspace are terms you will meet constantly on MainPath, and each of them is explained briefly and in relation to MainPath.

Create your first project

You register, create an organization, and create your first project in the wizard, which MainPath generates with repositories in GitLab.

Bring in an existing project

A folder you built with Claude Code, Cursor, or Codex comes onto MainPath with one prompt, provided its tech stack is supported.

Set up your computer or work in the browser

You either work on your own computer, which the MainPath Toolbox prepares, or in a remote workspace in the cloud, and both paths lead to the same project folder.

Open and run your project

You open the project folder in the editor, start a terminal, run the application with mp run-local, and view it in the browser.

Work with an AI agent

Claude Code, Cursor, and Codex know MainPath's rules and talk to the platform directly through the agent plugin.

Save changes and publish

With a commit and a push your changes land in GitLab, the pipeline brings them to the dev server, and you release production with a click.

When something does not work

Most typical stumbling blocks when getting started can be checked yourself, and if that is not enough, support helps.

What is GitLab?

GitLab is where the code of your projects lives and where the pipelines run, and day to day you only need a few of its functions.

What are pipelines?

A pipeline tests, versions, builds, and distributes your application after every push to main, and you start the last step to production yourself.

For developers

Development environment

Editors and AI agents

Connections and services

Publishing

Advanced

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