Skip to main content
With automatic deploys on, a push to your agent’s branch builds a new version and, if it passes its smoke test, puts it live. It is on by default for a new agent.

​
Which pushes deploy

  • A push to the agent’s branch. Pushes to other branches, and branch deletions, are ignored.
  • For an agent in a folder, only a push that changes something in that folder. A push that touches only apps/website does not rebuild the agent in apps/agent. If Onecortex cannot tell what a push changed, it deploys rather than risk skipping a real change.
  • A configuration change, too: saving a secret or variable deploys, so the change takes effect. See Configuration and secrets.
A push to a new branch has nothing to compare against, so every agent on that branch deploys. The build shows triggered by push and the commit that started it. A build that fails leaves the live version serving, as every build does. See Builds. A change to code outside the agent’s folder that the agent depends on, such as a shared package elsewhere in a monorepo, does not trigger a deploy. Click Deploy after it.

​
Turn it off

On the agent’s Settings tab, turn off Deploy automatically on push. Pushes and configuration changes then deploy nothing, and Deploy on the agent’s page deploys the head of the branch when you choose.

​
Change the branch

On the agent’s Settings tab, choose another Branch. Changing it does not deploy: the next push to the new branch does, or Deploy.

​
Pushes while a build runs

One agent builds one commit at a time, and an organization runs three builds at once. A push that arrives when there is no free slot fails at Fetch source with This agent is already deploying. Wait for it to finish and deploy again. or Your organization is already running 3 deployments, the most it can run at once. Wait for one to finish and deploy again. Push again, or click Deploy, when it finishes.
Last modified on September 28, 2026