Skip to main content
truss watch [OPTIONS] [TARGET_DIRECTORY]
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

​
--remote
TEXT
Name of the remote in .trussrc to patch changes to.
​
--config
PATH
Path to a custom config file. Defaults to config.yaml in the Truss directory.
​
--team
TEXT
Name of the team to deploy to. If not specified, Truss infers the team or prompts for selection.
The --team flag is only available if your organization has teams enabled. Contact us to enable teams, or see Teams for more information.
​
--no-sleep
FLAG
Keep the development model warm by preventing scale-to-zero while watching.
​
--hot-reload
FLAG
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.
​
--model-name
TEXT
Temporarily overrides the model name for this session without updating config.yaml.

​
Arguments

​
TARGET_DIRECTORY
TEXT
A Truss directory. Defaults to current directory.
Examples: Watch for changes in the current directory: 
truss watch
You should see: 
🪵  View logs for your development model at https://app.baseten.co/models/.../logs
👀 Watching for changes to truss at '/path/to/my-model'...
When you edit a file, Truss detects the change and applies a live patch to the running deployment. Watch a specific Truss directory: 
truss watch /path/to/my-truss
Watch with a custom config file: 
truss watch --config my-config.yaml