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
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.
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.
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.
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.