Choose a tool and its scope
A coding agent is a private terminal workspace. Choose the provider and grant only the app or service context required. No grant means no private resource context.
MolternDeploy agent-built code
Guides
Give generated code a reviewed path to production.
Use a scoped coding workspace, inspect the result and deploy it as an application.
Flight paths artwork / 20
An agent’s ability to generate code does not decide what it should access. Grant only the resources required for the task and review changes before deployment. Confirm the app’s configuration, test its main workflow and keep the production environment separate from experimentation.
Deploy agent-built code
Configure the first application
Connect a repository and branch, review the build and start commands, then set the runtime port and health check. Static sites and web services have different operating needs.
Choose the environment boundary
Organize development, preview, staging and production work explicitly. Review the variables and connected services for each environment rather than assuming they share data.
Detailed instructions are maintained in the product documentation.
Questions before you start
Do I need to change coding agents?
Moltern documents several provider CLIs and a generic terminal workflow. Provider sign-in and usage terms still apply.
Can I keep my existing framework?
Use a supported runtime or a Dockerfile. Review the application guide for your build output and server requirements.
Does a preview copy production data?
Do not assume it does. Configure appropriate test services and verify which data and variables the preview can access.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗