The code editor is somehow broken using Chrome on Windows - the cursor editor on screen does not correspond to the actual cursor position. Works fine on Chrome on macOS. Makes editing code a PITA on Windows as I have to guess where the cursor actually is. Like in this example, the cursor is actually at the end of the line !
Question : is it possible to change the custom node inputs without having AI touch the whole code and potentially mess it up ? Or does adding an input necessarily imply having AI regenerate the whole custom node code ?
I wonder if I should maybe use the “Run Code” node instead to keep full control ?
Hey @cdromain! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
Hey @cdromain, Thank you for flagging the issue with the custom node on Windows. Sorry for the hassle there. I’ll try to reproduce it and then cut a ticket so we can get it fixed.
On your second point, you can edit the code on the custom node, but you’ll need to go through the prompt and node configuration via AI. Once you’re in the custom node window, there’s an option to edit the code directly. I’ve explained that process in the Loom video below. That said, if you’re looking for more flexibility or quicker control, Run Code node might be a better fit.
Thanks for your reply @Wasay-Gumloop
Looking forward to a fix for a smoother custom node editing experience on Windows - and will give Run Code node a try !
Cheers, Romain
