Your workspace in the cloudYour path to a release

Building with AI in Codespaces? Look beyond the editor. Compare how code becomes part of your project, how changes are checked and how the application reaches its target server.

A prepared development environment within your MainPath project

Locally or in the cloudKeep the project in view

Codespaces can remain your workspace when the required tools, repository access and connections are configured there. MainPath also offers prepared workspaces and local development through the Toolbox. Test the combination on a supported project first.

  • Keep and share changes in the right repository
  • Choose the development environment separately from the application runtime
  • Configure the AI agent connection in the environment where the agent actually runs
Connect the CLI and your agent

Where you developAnd how the project moves forward

Codespaces and a release workflow can work together. Compare which parts you want to assemble and which project foundation you want to use.

Work with GitHub Codespaces

  • Open a cloud development environment from a repository or template.
  • Adapt tools and runtimes through a dev container configuration.
  • Run applications and forward ports for testing or sharing.
  • Set up CI and deployments with GitHub Actions when needed.
What Codespaces offers

Build a project with MainPath

  • Prepare repositories, project structure and a pipeline for supported stacks.
  • Keep building locally or in a suitable prepared development environment.
  • Connect tests, builds and delivery through the project workflow.
  • Attach suitable target servers and the required store accounts for mobile apps.
Explore the MainPath workflow

Forwarding a port for testing and operating a released application are different tasks.

After the first promptKnow the next step

Keep track of changes

Your code is versioned within the project. You and your team can see what changed instead of losing work between environments.

Check before releasing

The pipeline runs the configured tests and builds. Changes on main update Dev; you approve production after checking the result.

Run your application

Connect a suitable server for your project. MainPath sets up the environment with HTTPS and the connection for deployments.

Try one complete pathThen decide what to change

  1. Map the current workflow

    List the repository, dev container configuration, environment values and existing Actions workflows.

  2. Check project support

    Ask your agent to check the existing code against supported stacks. Importing does not automatically translate your GitHub workflows.

  3. Test the development environment

    Check repository access, tools and the agent connection in Codespaces, locally or in a suitable MainPath workspace.

  4. Go through a release

    Build a change, check it on Dev and try the manual production release. Then decide which parts to adopt.

Keep what works for youConnect the next steps

Try MainPath on a manageable project or talk to us about fitting it into your existing development workflow.

Questions about Codespaces and MainPath

Is MainPath a complete replacement for Codespaces?

There is no blanket one-to-one replacement. Codespaces is a customizable development environment in GitHub. For supported stacks, MainPath connects the project foundation with tests, builds and delivery and offers prepared development environments. Check the tools and workflow against your project.

Can I keep Codespaces as my workspace?

It can fit when you configure the necessary tools, repository access and connections there. For MainPath MCP, the mp CLI must be installed, signed in and reachable in the environment where the agent runs. Opening a Codespaces session in a browser does not establish that connection automatically.

MainPath CLI and agent plugin

Will my devcontainer.json be imported automatically?

An automatic conversion into an identical MainPath workspace is not promised. Codespaces defines its environment through dev container files. MainPath uses prepared development environments; check the tools, access and required configuration before switching.

GitHub dev containers

Can GitHub also run tests and deployments?

Yes. GitHub Actions can provide CI and deployment workflows. Codespaces and Actions are different parts of that process. The comparison with MainPath concerns the prepared project foundation and delivery path, not an alleged lack of deployment support in GitHub.

Deploy with GitHub Actions

Can I bring existing code into MainPath?

For supported stacks, your AI agent first checks the existing code and guides the import. Review GitHub-specific workflows, repository access and development configuration separately. Do not edit generated MainPath files such as .gitlab-ci.yml directly.

Project import and supported stacks

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