Michael Schmidt

> Could we commit text box changes to the undo history No. As Kim rightly pointed out, that's just a bad UX. We don't do that for other inputs (number)...

@joeyballentine This is not a duplicate. #748 fails because of `IpcMainImpl.handle`, so [here](https://github.com/joeyballentine/chaiNNer/blob/3d57f4ddd379b1df32f04c1f3573cf0827ef0a7e/src/main/main.ts#L37). But this issue fails at `loadURL`, so [here](https://github.com/joeyballentine/chaiNNer/blob/3d57f4ddd379b1df32f04c1f3573cf0827ef0a7e/src/main/main.ts#L532). They are different.

What's your chain? Did this spike in memory usage occur before, during, or after running the chain?

That sounds like a good idea. We could add a node that accepts any value (not just images) and returns it as is. I'm just not sure what to name...

We have a feature called "passthrough" planned already (#373), so we can't use that name. Yes, they are totally different, but this would get confusing.

The problem is that they have the same name. I wouldn't be able to tell people: "You can solve this by using passthrough," because it wouldn't be 100% clear which...

I think blender allows you to minimize nodes like this:  It would be pretty useful to have that as a general feature instead of a special property for one...

I think this might be easy to solve once we have tabs. We could simply have a "Welcome" tab that shows things like templates, recently opened/saved chains, and so on.

I think [fs watchers](https://nodejs.org/api/fs.html#fspromiseswatchfilename-options) would be the easiest way.

It's smart. OSes have a built-in functionality for this, and `fs.watch` API just exposes it to us.