Skip to main content
Watches for source code changes and applies live patches to a development deployment. This enables rapid iteration without redeploying.
You can create a development deployment and start watching in one step with truss push --watch.

Options

PATH
Path to a custom config file. Defaults to config.yaml in the Truss directory.
TEXT
Name of the remote in .trussrc to patch changes to.
TEXT
Name of the team to deploy to. If not specified, Truss infers the team based on your team membership and existing models, or prompts for selection when ambiguous.
The --team flag is only available if your organization has teams enabled. Contact us to enable teams, or see Teams for more information.
BOOLEAN
default:"true"
Keep the development model warm by preventing scale-to-zero while watching. Default is true. Pass --no-sleep=false to disable.
Apply model code changes by swapping the model class in-process without restarting the inference server. Preserves in-memory state like loaded weights and caches, but does not re-run __init__() or load(). If your changes add new instance state that predict() depends on, do a full reload instead. When creating a new deployment with truss push --watch, use --watch-hot-reload instead.
TEXT
Temporarily overrides the model name for this session without updating config.yaml.
Stream deployment logs while watching.
humanfriendly | W | WARNING | I | INFO | D | DEBUG
default:"humanfriendly"
Logging verbosity. humanfriendly (default) is pretty-printed; INFO, DEBUG, WARNING produce structured logs.
Disable interactive prompts. Use in CI/automated contexts where stdin isnโ€™t a TTY.

Arguments

TEXT
A Truss directory. Defaults to current directory.
Examples: Watch for changes in the current directory:
You should see:
When you edit a file, Truss detects the change and applies a live patch to the running deployment. Watch a specific Truss directory:
Watch with a custom config file: