Skip to main content
TerminalUse deploys agents through branches, environments, and versions.

​
The Model

PrimitiveMeaning
EnvironmentA named deployment policy such as production or preview
BranchA git branch deployment slot
VersionOne concrete deployable build of your agent
Each deploy creates a new version. A branch points at the currently active version for that branch.

​
Environment Resolution

The CLI resolves the effective branch from:
  1. --branch, if provided
  2. the current git branch, if available
  3. main as a fallback in some flows
That branch is then resolved to an environment by branch rules. For a default setup:
BranchEnvironment
mainproduction
everything elsepreview

​
Stickiness

deployment.production.areTasksSticky and deployment.preview.areTasksSticky control what happens to running tasks when a new version activates.
SettingBehavior
trueExisting tasks stay on their current version
falseExisting tasks can migrate during rollout

​
Rollback

tu rollback rolls a branch back to an earlier version. Rollback uses the target version’s secrets_snapshot. Pending environment-secret changes are not rewritten by the rollback itself.

​
The Main Operational Commands

  • tu deploy
  • tu ls
  • tu rollback
  • tu logs
See Deploying Agents and CLI Reference.