type differs.
Click to zoom
What your pipeline needs
- A management API key, stored as a CI secret. Expose it only to trusted deploy jobs.
- Private network access to the gateway, for example a self-hosted runner inside your network.
- The agent ID of the agent you are releasing.
How a release works
- Push or merge to your release branch.
- Build and test the agent image: your code, your framework, the core SDK, and its adapter. Node and Python images follow the same steps.
- Push the image to your private registry.
- Register the deployment. Your pipeline registers the release with its repository, commit, branch, and author. Tilde returns a deployment ID and a one-time token. The release is registered but offline.
- Deploy. Your pipeline stores the token in your secret manager and rolls out the new release with your usual tooling.
- Agent replicas start. They dial the gateway with the token and send ready heartbeats. The deployment becomes serving.
- Routing moves traffic. New conversations go to the new release according to your routing mode. Existing conversations stay pinned to their original deployment, so keep the old release running until they drain.