guild sync [OPTIONS] [RUN...]
Synchronize remote runs.
A remote run is an operation that runs on another system. Guild keeps track of where each remote run is located and can synchronize with it. This includes downloading files generated by the run as well as updating run status.
By default, Guild synchronizes once with the remote run and exits. If you want to automatically synchronize with the run while watching its output, use the
You can only watch one running operation at a time. If you don’t specify a RUN with the
--watch option, Guild will watch the most recently started running operation.
When a remote status stops (it finished successfully, is terminated, or exits with an error), Guild will no longer synchronize with it.
You can synchronize specific runs using
RUN arguments. For more information, see SPECIFYING RUNS and FILTERING topics.
You may use one or more
RUN arguments to indicate which runs apply to the command.
RUN may be a run ID, a run ID prefix, or a one-based index corresponding to a run returned by the list command.
Indexes may also be specified in ranges in the form
START is the start index and
END is the end index. Either
END may be omitted. If
START is omitted, all runs up to
END are selected. If
END id omitted, all runs from
START on are selected. If both
END are omitted (i.e. the
: char is used by itself) all runs are selected.
RUN argument is not specified,
: is assumed (all runs are selected).
Filter by Operation
Runs may be filtered by operation using
--operation. A run is only included if any part of its full operation name, including the package and model name, matches the value.
--operation multiple times to include more runs.
Filter by Label
--label to only include runs with labels containing a specified value. To select runs that do not contain a label, specify a dash ‘-’ for
--label multiple times to include more runs.
Filter by Tag
--tag to only include runs with a specified tag. Tags must match completely and are case sensitive.
--tag multiple times to include more runs.
Filter by Marked and Unmarked
--marked to only include marked runs.
--unmarked to only include unmarked runs. This option may not be used with
Filter by Run Start Time
--started to limit runs to those that have started within a specified time range.
IMPORTANT: You must quote RANGE values that contain spaces. For example, to filter runs started within the last hour, use the option:
--started 'last hour'
You can specify a time range using several different forms:
between DATETIME and DATETIME
last N minutes|hours|days
N days|weeks|months|years ago
DATETIME may be specified as a date in the format
YY-MM-DD (the leading
YY- may be omitted) or as a time in the format
HH:MM (24 hour clock). A date and time may be specified together as
between DATETIME and DATETIME, values for
DATETIME may be specified in either order.
When specifying values like
hours the trailing
s may be omitted to improve readability. You may also use
min instead of
hr instead of
between 1-1 and 4-30
between 10:00 and 15:00
last 30 min
last 6 hours
3 weeks ago
Filter by Source Code Digest
To show runs for a specific source code digest, use
--digest with a complete or partial digest value.
||Watch a remote run and synchronize in the background.|
||Seconds to wait in between sync when
||Filter runs with operations matching
||Filter runs with labels matching VAL.|
||Filter only runs without labels (deprecated - use ‘-Fl -’).|
||Filter runs with TAG.|
||Filter runs with comments matching VAL.|
||Filter only marked runs.|
||Filter only unmarked runs.|
||Filter only runs started within RANGE. See above for valid time ranges.|
||Filter only runs with a matching source code digest.|
||Show this message and exit.|
Guild AI version 0.7.3