Use Render from Codex to deploy apps, validate render.yaml, debug failed deploys, monitor services, and work through common platform workflows.
- Bundled Render skills for deployment, debugging, monitoring, migrations, and workflows
- A helper script at
scripts/validate-render-yaml.shforrender blueprints validate - Plugin metadata and assets for Codex installation
Install the plugin from the Codex plugin library in the app when it is available there. That is the preferred install path for most users.
Use the local install flow below for development, testing, or pre-release access.
- Copy the plugin into
~/.codex/plugins/render:
mkdir -p ~/.codex/plugins
rsync -a ./ ~/.codex/plugins/render/- Add the plugin to
~/.agents/plugins/marketplace.json.
If the file already exists, add the render entry to the existing plugins array.
{
"name": "local-plugins",
"interface": {
"displayName": "Local Plugins"
},
"plugins": [
{
"name": "render",
"source": {
"source": "local",
"path": "./.codex/plugins/render"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Developer Tools"
}
]
}- Restart Codex.
- Open the plugin directory in Codex and install
Renderfrom your marketplace.
Use the plugin to:
- Deploy a project to Render
- Validate and troubleshoot
render.yaml - Debug failed deploys and check service status
- Work through common setup and migration tasks
Good first prompts:
Help me deploy this project to Render.Help me validate my render.yaml for Render.Debug a failed Render deployment.
Many Render workflows depend on the Render CLI.
- Install the Render CLI:
brew install render- Authenticate:
render login- Verify access:
render whoami -o jsonIf render whoami -o json fails, fix authentication before you rely on Render workflows in Codex.
Run the sync script to refresh skills/ from render-oss/skills:
./scripts/sync-skills.shGitHub Actions also runs .github/workflows/sync-skills.yml each day and opens a pull request when upstream skills change.
MIT. See LICENSE.