# Feature request - Access OS command line option in Change node

**URL:** <https://discourse.nodered.org/t/feature-request-access-os-command-line-option-in-change-node/76807>\
**Category:** Feature Requests\
**Created:** [22 March 2023 09:33 UTC](https://discourse.nodered.org/t/feature-request-access-os-command-line-option-in-change-node/76807 "2023-03-22T09:33:55Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [22 March 2023 12:03 UTC](https://discourse.nodered.org/t/feature-request-access-os-command-line-option-in-change-node/76807/5 "2023-03-22T12:03:57Z")

</div>

The examples I gave above directly relate to changing a message; except for counting NR deploys you can do them with Javascript in a function node.

I struggle to understand this objection.  
People use Node-red in different ways for example [some-parental-control-with-nodered-and-a-windows-pc](https://discourse.nodered.org/t/some-parental-control-with-nodered-and-a-windows-pc/76808/2) or  
[integrating-node-red-mcu-edition-into-the-node-red-editor](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/68)  
Do you object to these on the basis that it's somewhat different to "normal" Node-red philosophy?

Yes it might allow me to run some application which would be _better_ launched from an exec node. I wouldn't choose to start an xterminal and open a browser from a change node, but if I did, so what?

What it would do is allow me to more easily use my knowledge of the shell as an alternative perhaps to learning yet another language - JSONata.

The long dropdown of change node options is certainly a problem but if necessary it could be broken down into categories.

---

_[View the full topic](https://discourse.nodered.org/t/feature-request-access-os-command-line-option-in-change-node/76807)._