# Tip: The "cylc set" command

**URL:** <https://cylc.discourse.group/t/tip-the-cylc-set-command/970>\
**Category:** Tips\
**Created:** [June 19, 2024, 10:43am UTC](https://cylc.discourse.group/t/tip-the-cylc-set-command/970 "2024-06-19T10:43:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![oliver.sanders](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/oliver.sanders/32/110_2.png) [@oliver.sanders](https://cylc.discourse.group/u/oliver.sanders)\
**Post date:** [June 19, 2024, 10:43am UTC](https://cylc.discourse.group/t/tip-the-cylc-set-command/970/1 "2024-06-19T10:43:28Z")

</div>

### At Cylc 8.3.0, the `cylc set` outputs command has been replaced by `cylc set`.

The new command is more straightforward and intuitive to use:

- It can set task prerequisites (without setting the corresponding outputs on the upstream task).
- It can set task outputs (the task will now change state accordingly making it clearer).

For Cylc 7 users, the `cylc set` command will feel familiar to `cylc reset`.

Because the new command will update the task’s status (e.g. if you set the `succeeded` output on a task, then it will go into the succeeded state), it is no longer necessary to manually remove tasks to prevent them from clogging up the workflow’s runahead limit.

For more information and a side-by-side comparison of `cylc set` against the older `cylc set-outputs`, see the [changes page](https://cylc.github.io/cylc-doc/stable/html/reference/changes.html#manually-setting-task-outputs-and-prerequisites) in the Cylc documentation: