Skip to main content

​
Description

Upload local weights for a registered model release. Both arguments are optional inside a workspace:
  • With no <model>:<release>, the identity is read from the nearest enclosing reactor.yaml’s model.name and model.version (walking up from the current directory, stopping at the repository root).
  • With no <path>, the source defaults to runtime.weights_path from the same reactor.yaml (the path reactor model publish and reactor run use), else ./weights/.
  • A single argument is treated as <model>:<release> when it contains a colon and no such file exists on disk; otherwise it is the <path>.
<path> may be a single file or a directory of files. When it is a directory, the CLI walks the entire tree, computes a SHA-256 manifest, uploads every file preserving its relative path, and finally writes the manifest as the “bundle complete” sentinel. The model release must already be registered (use: reactor model publish). Files are uploaded directly to object storage via presigned URLs. Dedupe: when a previous bundle with identical content already exists for the target release, the upload is skipped with a clear message. Pass --force to bypass the check and re-upload unconditionally. Carry-over (--from): assert that this release reuses the bundle of an existing release of the SAME model, with no local bytes. The CLI fetches the source release’s manifest from the server and asks the server to copy each weight file into the new release’s prefix server-side. No <path> is read; --from is mutually exclusive with <path> and --force. The source release must still be reachable via the server’s per-file dedupe window (typically the 8 most-recent prior releases for the same model). Symlinks are rejected (resolve them with cp -L or tar --dereference first). Examples:

​
Options

​
Global options

​
See also