alt Hacker NewsI don't understand the value proposition. It “works great for local models” (they all do) so you’ve got more RAM than you possibly need for any TUI you might want to run. Are people really fretting over a few MB of memory rather than evaluating these tools on their ergonomics and features?
Replies
Typical coding agents of today consume hundreds of MBs of RAM. Once you add GUI into the mix, that could easily slip into GBs. You might feel the difference, when you're trying to fit a capable local model into small amount of local RAM.
Even on 64 GB RAM machines you could easily get memory pressure on the system when trying to work with a chonky local model. Consider also resource-constrained cases like small VPS servers or SBC computers (like Raspberry Pi).
Ergonomics and features are included too here. The point is that these can coexist with small resource footprint.
I already found myself being limited by Memory used by Claude code, about 300MB per session. With 40 sessions that eats up quite a good chunk of my laptop's memory
Not a big deal since most of my sessions were parked so I just found a way to have them exit without losing the screen content (I took a screen dump from herdr) and a simple wrapper script that waits until hit enter to resume the session.
I don't _ have _ to switch to a lighter weight harness, but I'm not oblivious to memory usage