Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.modelcode.ai/llms.txt

Use this file to discover all available pages before exploring further.

Why build environments can’t be switched after setup Switching between Self hosted and Modelcode hosted build environments isn’t supported once a project has been configured. The reason is largely technical: each environment comes with its own conventions around how dependencies are resolved, installed, and cached, as well as how setup and runtime scripts are executed. These differences are baked into the project’s configuration early on, and switching mid-flight would require re-deriving a significant portion of that setup - which can lead to subtle inconsistencies that are hard to detect and even harder to recover from. To keep builds reliable and reproducible, the environment choice is treated as a foundational decision rather than a toggle. If you’d like to move a project to a different environment, the recommended path is to create a new project under the desired setup. We’re continuing to evaluate ways to make this more flexible in the future. Why daemons can’t be switched after setup For Self hosted projects, the same principle applies to the specific ModelDaemon you connect to. When a daemon is first selected, your project’s dependencies are installed and prepared on that daemon’s host. Switching to a different daemon would require re-running that installation step on the new host so it ends up in a comparable state - and that re-installation isn’t something the platform performs automatically today. Until that step is supported, the daemon you pick when setting up a Self hosted project is the daemon that project stays on. If you need to move a project to a different daemon, the recommended path is the same as above: create a new project and connect it to the daemon you’d like to use. This is on our roadmap to make more flexible in the future.