# autoreload for runworker?

**URL:** <https://forum.djangoproject.com/t/autoreload-for-runworker/19609>\
**Category:** Django Internals\
**Created:** [March 18, 2023, 2:57pm UTC](https://forum.djangoproject.com/t/autoreload-for-runworker/19609 "2023-03-18T14:57:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [March 18, 2023, 2:57pm UTC](https://forum.djangoproject.com/t/autoreload-for-runworker/19609/1 "2023-03-18T14:57:52Z")

</div>

Question for the brain-trust here - am I the only one who would get significant value from adding an “autoreload” options for the channels “runworker” command?

I realize it’s not quite the same situation as using “autoreload” for “runserver” in that “runserver” should never be used in production, while I have any number of deployed “runworker” instances.

But, having that as an option would remove a bit of friction in my development environment.

Thoughts anyone?