There are fashion subscriptions. Some people do not value being able to continually rewear clothes and would prefer to constantly having new clothes to show off.
Hermes is huge and packed with features you probably don't need. I prefer smaller one I can extend as necessary, there are so many on github now and it is fun to test them but have been impressed with dirge (https://github.com/dirge-code/dirge) not affiliated.
I have one reading my second tier RSS feeds and newsletters and giving me news/market updates filtered for things important to me
I'm not contradicting this but offering a contrast, I like Hermes because it simultaneously lowers barrier of entry and shows you what possibilities are unlocked by agents. I don't think I would have the time, interest or creativity to jump into the deep end by either extending an existing harness or rolling my own from the start. This also isn't an argument for doing just that, I might do so in the future, but critically only after Hermes has shown me what's possible and my preferences are developed.
I completely agree. I started with aichat[0] before the current agent trend and hit all kinds of bumps implementing agentic loops on my own. Then goose[1] showed me what a whole team working toward the same idea could do right before the official Claude Code harness which had all the bells and whistles. Now I know better what I want and its mostly less ram usage and a small set of primitives.
I still use Claude code (and codex and other big contenders) because they know what they are doing and innovate in ways I don't want to miss. And sometimes they are better at tasks.
I had the same line of thought and spent a while with nanoclaw before realizing that adding the features I want back in would have made future updates too painful. I ended up switching to Hermes and aggressively disabling tools/skills and it's been pretty fine so far. I got more use cases set up than I did in my time with nanoclaw.
Totally fair, I still use Claude code for tasks since it is so polished. I think I just dont have that complicated of use cases so in the end performance should reflect my lightweight needs as the priority.
I feel the same but my preference is for Cecli (cecli.dev)
It does what I need it to do and since I invested so much time in setting it up and even contributing to development it is my go to for coding and even managing my VPS as well as business tasks
more developed countries are already prepared for what you describe: people would (continue to) take public transit, and rich people would (continue to) pay for the unemployed to live and retrain until they get new jobs. If a country was missing these basic features it would be scarier.
small correction: only individual contributions are meaningful. If I consume less and you consume less and many other individuals consume less there simply won't be as much demand for fossil fuels.
The only way I can understand your premise of helplessness is that it provides a convenient excuse for you not to do anything to help. Do you think companies will keep burning fuel at the exact same rate if a billion individuals dont incentivize them to?
Except you don't need a multiplexer for that. Essentially all modern terminals have tabs. Many have split-screen. Even windows ships with a half-decent terminal with tabs and multiple panes by default now!
A multiplexer's job is to do the whole multiple tabs/panes/windows thing independently of the terminal itself, but (a) the UX for eg. tmux is so much worse than that of a good terminal UI, and (b) you only need that if you plan on connecting remotely (see my other comment https://news.ycombinator.com/item?id=49108483).
