# Should debug nodes be capable of passing the message forwards?

**URL:** <https://discourse.nodered.org/t/should-debug-nodes-be-capable-of-passing-the-message-forwards/95044>\
**Category:** Core Development\
**Created:** [1 February 2025 12:19 UTC](https://discourse.nodered.org/t/should-debug-nodes-be-capable-of-passing-the-message-forwards/95044 "2025-02-01T12:19:20Z")\
**Posts on this page:** 1\
**Showing post:** 47

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [2 February 2025 11:04 UTC](https://discourse.nodered.org/t/should-debug-nodes-be-capable-of-passing-the-message-forwards/95044/47 "2025-02-02T11:04:20Z")

</div>

> [@dceejay](#):
>
> looks really fugly

😄

I agree - unfortunately, there is a need. Short of redesigning nodes appearance (e.g. inset buttons) or adding a feature (like hover to reveal or right click context menu options) to nodes, we have little choice.

TBH, I really dislike that we have to deploy after toggling a button (especially the debug node). Dont get me wrong, i understand why it is the way it is but there are ways we could solve this. For example, a local store (of overrides) that can be updated without deploy would make the situation a lot smoother (storage on systems permitting) but I'm not trying to solve that here and now.

---

_[View the full topic](https://discourse.nodered.org/t/should-debug-nodes-be-capable-of-passing-the-message-forwards/95044)._