Skip to main content
Your CI pipeline builds the agent container from a regular Dockerfile and publishes it to your container registry. Before you roll out a new version, you register a deployment in Tilde. The flow is the same for direct and sidecar agents. Only the type differs. Release pipeline from a push in CI, through deployment registration and rollout, to the router sending new conversations to the release
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.
Tilde works with any CI system. We provide a GitHub Action that registers a deployment, and every other system can call the same API.

How a release works

  1. Push or merge to your release branch.
  2. Build and test the agent image: your code, your framework, the core SDK, and its adapter. Node and Python images follow the same steps.
  3. Push the image to your private registry.
  4. 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.
  5. Deploy. Your pipeline stores the token in your secret manager and rolls out the new release with your usual tooling.
  6. Agent replicas start. They dial the gateway with the token and send ready heartbeats. The deployment becomes serving.
  7. 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.

Deployment tokens

Tilde shows a deployment token once and stores only its hash. Your pipeline passes it straight to your secret manager, and every replica of the release uses it. Registration is safe to retry, and you can rotate a token at any time.

Verify the release

Open the agent’s Deployments tab. The release shows as serving, with the commit linked. Run a test conversation, then check its session and traces.