# Delete debug message or hide message
**URL:** https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629
**Category:** Feature Requests
**Tags:** debug, todolists
**Created:** [12 August 2026 11:14 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629 "2026-08-12T11:14:53Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@gregorius](https://discourse.nodered.org/u/gregorius)
#### Post date: [12 August 2026 11:14 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/1 "2026-08-12T11:14:53Z")
Hi there,
Just wondering whether there is support fo this idea:
in the drop down for a debug message, add a delete message option?
Why?
I'm currently working through a bunch of debug messages that are all actually todos - each one is slightly different, requiring slightly different actions. So in fact, the debug panel is being missed used as a todo list. For that, it would be helpful if I could remove those messages that I have already dealt with ... (it's an awfully long list - enough to create a procrastination moment, hence this post!)
As alternative, is there anyway to add the menu option via a plugin that extends the menu automagically?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [12 August 2026 12:53 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/2 "2026-08-12T12:53:17Z")
I also think that the ability to remove individual debug messages would be useful. There are lots of times where I would have found this helpful in seeing the wood for the trees.
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [12 August 2026 14:33 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/3 "2026-08-12T14:33:07Z")
I would like to see this implemented as a right click on the debug node name, with options
- Delete this messge.
- Delete all messages from this node.
- Delete All messages from this node and disable it.
The current options to filter selected nodes and delete filtered messages are incomprehensible to me.
In principle I could use this to show only messages from a single node, clear them and go back to showing the rest.
In practice this is absurdly difficult, hence the right click option suggested above.
---
### Author:  [@gregorius](https://discourse.nodered.org/u/gregorius)
#### Post date: [13 August 2026 07:16 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/4 "2026-08-13T07:16:13Z")
> [@jbudd](#):
>
> - Delete this messge.
This can be ambiguous when multiple messages have been sent. Which message is meant - the last, the first, the middle, the second to last ...
Also something that I find useful from the message tracing is a highlight of messages generated by the debug node. In the message tracing, that is done with a red border around the messages:
In this case, the node highlighted was reached 6 times and the messages it got are sent to the debug panel and two of these messages have now been highlighted.
This can be done with the filter but I prefer the border solution because it also shows the message around the ones of interest.
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [13 August 2026 08:09 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/5 "2026-08-13T08:09:57Z")
> [@gregorius](#):
>
> > [@jbudd](#):
> >
> > - Delete this messge.
>
> This can be ambiguous when multiple messages have been sent. Which message is meant - the last, the first, the middle, the second to last ...
I don't think that's a problem, at least in my browser it seems pretty clear which message is in focus.
In the right hand panel the mouse pointer is a basic triangle pointer, but if you pass it over a debug message content it changes to the pointing finger and that message is highlighted with a different background colour.
Over the node name it changes to the pointing finger and a tooltip is shown.
An extra bonus from the right click approach:
Often when trying to debug a flow you clear the debug panel, deploy and debugs from other flows pop up.
Handy to be able to disable them without navigating away from the flow you are working on.
I know, ideally there are no active debug nodes except on the flow[s] you are working on, but in life debug happens.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [13 August 2026 09:04 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/6 "2026-08-13T09:04:55Z")
> [@jbudd](#):
>
> Often when trying to debug a flow you clear the debug panel, deploy and debugs from other flows pop up.
You can select Current Flow instead of All Nodes at the top of the debug pane.
---
### Author:  [@gregorius](https://discourse.nodered.org/u/gregorius)
#### Post date: [13 August 2026 09:10 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/7 "2026-08-13T09:10:46Z")
> [@jbudd](#):
>
> at least in my browser it seems pretty clear which message is in focus.
Message in focus isn't from the debug node with the delete message button? So this is an extra cognitive process to establish the connection between highlighted debug message and the corresponding debug node - if I understand your approach correctly.
But that's not for me to decide, I've found my workaround for my original issue. I've extended the [scratchpad](https://github.com/gorenje/node-red-scratchpad#execute-code-in-the-browser) plugin with an "execute in browser" functionality. Which now allows me to execute JS snippets in the browser to do things in the editor:
After all, the entire editor is one giant jQuery application with some pixie dust sprinkled over it! 😉 This is of course not a proper solution and shouldn't be done at home but it works for me and allows me to save some cognitive energy for more important things in life.
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [13 August 2026 09:23 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/8 "2026-08-13T09:23:38Z")
> [@gregorius](#):
>
> Message in focus isn't from the debug node with the delete message button? So this is an extra cognitive process
I'm sorry but I have no idea what that means.
In my imagination one sees a sidebar full of debug messages. _In the sidebar_ you right click on the name of a node which spawned a message and are offered the choice to delete the message, others from the same node or to turn that particular node off (I'm not sure if there is a proper word for the effect of clicking on the button on the node itself. Not disable because debug nodes can also be disabled in the config.)
---
### Author:  [@gregorius](https://discourse.nodered.org/u/gregorius)
#### Post date: [13 August 2026 09:53 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/9 "2026-08-13T09:53:24Z")
> [@jbudd](#):
>
> _In the sidebar_ you
Well that solves the mystery - I thought that menu was _on the debug node_, now it all makes sense. Sorry for the confusion & thanks for the explanation and patience.
---
### Author:  [@herman34](https://discourse.nodered.org/u/herman34)
#### Post date: [13 August 2026 12:06 UTC](https://discourse.nodered.org/t/delete-debug-message-or-hide-message/101629/10 "2026-08-13T12:06:47Z")
Yeah find this useful too. The debug panel is not really designed as a todo list, but I think having a `Delete/Clear this message` option would make it much easier to manage when using debug messages as temporary reminders. Also a per message hide option would be handy as well.