There are people NOW who use and appreciate it. There are also people who speak for others. I voted you up because you actually put thought into a response, not that the response is a good argument. Some of it is your opinion, and that's yours alone and not for anyone to judge. The rest of it is more focused on others and their actions, before your own. That I can attack, and do so gleefully.
I've been using LLMs for 5 years, sorry, 6 years (sigh). GPT-2 was a dumbass, but I still managed to get it to do primitive function calls - in 2020. I'm not slowing down. I'm increasing speed. It's 2026. Some of you are going to be obsoleted into oblivion if you don't start moving. I estimate I'm at least worth $600K a year now, probably a lot more. And, I don't have a masters. My dad did, and half a Phd, but I digress. I'm not him. Instead of working for the man, I'm doing my own thing, yet again. It is possible for one person to build an empire. I'm going to do it. Not ego. Intent.
The thing you describe here, about it being depressing, is a logical fallacy. I'm not even looking at an AI or Wikipedia. I don't know the proper name for it, but it's a fallacy based on thinking that others bring you value. You clearly have value, you said it yourself and said it well. If anyone sits around and let others define or tell them their value, they are a dumbass.
I've started using "get a horse!" as a shorthand meme for what you are feeling right now, maybe. I'm not here to speak for you or how you manage your emotions. I'm just pointing out the flaws in your thinking. This is what people on horses shouted at people driving the first cars. (the horse thing, although they probably thought driving a car was flawed thinking)
I will vouch for Simon. I do not know him personally. To me his posts are honest and inspirational.
> I have been overly critical and arguing in bad faith about your writing in the past
I think you are just critical without a stated valid reason. Arguing in bad faith seems to be a thing if HN history is the judge.
And this is coming from a critical thinker, who is a bit tired of people firing off "human slop" comments. The Internet is full of a lot of people, but even when a few are bad apples, it spoils the lot. Maybe that is the intent. Maybe you are just grumpy for your life's situation.
It is 100% possible to build software entirely with AI. If you don't do that, that's great! I still code by hand from time to time, and I'm reading a lot of Rust nowadays, and learning the ropes. I come from a strong Python and Javascript background, plus networking and operations, which I'm a whiz at. I don't do it anymore, but I know how to inform it is done properly.
With this power, I can build things nobody wants to build, but me. Doesn't mean one has to put it into production, or it has to pass some security test, although with me driving it probably will. It only need be what is important to the end user, the prompter, to matter.
I think Simon helps people with this mindset be better at what they love to do. And for that, we should all be grateful.
Ah, yeah, it's not called that anymore I guess (actually looking quickly it was called "HyperTerm" and is now just "Hyper"). Sorry for the confusion. I always have called Hyper "Hyper Terminal" because that's how I remember it on the Mac.
Again, you are right about the naming.
I would also say that HyperTerminal is a terminal for Windows. And, you do you! Use what you love, don't use what you don't.
I picked Hyper as a base because it's written in Electron and was cross platform capable. That said, I've changed a LOT in it to match my workflows and it hasn't given me any issues of late. I've literally seen it crash once the entire time I've been running the installed version (dev is a bit different). It's definitely not the same Hyper, is what I'm saying.
You seem intent on your opinion, and have every right to it.
Calling it an oversimplification isn't blame. It's just a fact. And you are the one that told someone they were wrong, and couldn't back it up with anything but the thing that over simplified from the beginning. That's just dumb gatekeeping.
I've been working on Hyperia, which is very similar: https://github.com/deepbluedynamics/hyperia. Hyperia is a fork of Hyper Terminal. Both are open source. Competition is good for this space, I think, especially for the user. There's also cmux and Intelligent Terminal (by Microsoft).
I do separation of concerns with the agent orchestrator (Nemesis8): https://github.com/deepbluedynamics/nemesis8. That can be run with or without Hyperia. I do not suggest anyone run agents on their bare metal. Putting them in a container gets a lot of wins, especially around log aggregation. Working now on a Splunk/Loggly-like interface for searching logs, tool runs (useful in tuning a custom local MoE drafter) and full session suspend, stop, detach, and search. It also does single MCP tool installs for all agents. Nemesis also supports dynamic port exposure to the host metal, for testing agent builds inside their containers.
Hyperia has a lot of extra features as well that I have found personally useful:
- Sticky notes (search too)
- addressable panes in addressable tabs, tabs in windows, multiple windows
- full ACLs across panes, notes, tabs, windows
- Poke-a-pane to keep an agent going (any agent, not just CC which has a timer function)
- webpanes with markdown extraction, JavaScript injection
- directory pickers for people who find cd'ing to things confusing or those weary of typing nearly the same directory path over and over again in new terminals (not perfect, but I'm iterating on it)
- a built in agent loop (in the Rust sidecar) that allows using local models for tool calls (needs a trained drafter to make it viable) or using a local model for token maxxing (compresses reads of panes by frontier models)
- pane splits down/up/left/right and quick layouts.
As for whether it was "vibe coded" or not, or Herdr for that matter, I don't think that term is useful, other than for quick judgment. No, this is not a one-prompt project. I've spent 100s of hours on it, started out with Hyper, and did a crazy amount of planning on how to architect it. I have done systems architecture for a living before, and have a strong search background. People who hate on AI, and therfore projects done with AI, are threatened. Nothing more. That's why they shortcut with "AI slop" or "Vibecoded. Nope". That's just ignorance speaking from a standpoint of fear.
Slop, whether AI or human, is an effort problem: https://deepbluedynamics.com/blog/ai-slop-effort-problem. Looking at Herdr, it looks solid. Judge the product by it's outcomes, it's use, not whether or not AI wrote it or not. That's the moment we're in though, for now, so downvote or not. I don't care.
The bowline has two variants, one being the cowboy version, which has the working bitter end on the outside of the loop, the "normal" bowline will have it on the inside of the loop.
To tie a bowline, make a loop in the working bitter end up about 2x the desired circumference of the loop you want to make. Your line is now segmented into the bitter end, and the standing line section.
Look at the loop. You want to put the bitter end through the same side of the hole where the bitter end overlaps the line/rope on the other side of the loop (standing section). If you use your right hand to twist the loop, and do so clockwise, you will insert the bitter end from the top. If you turn it counter-clockwise, then you will insert it from the bottom.
In this orientation, if you go around behind the right side of the standing part, you will form a normal bowline. If you go around behind on the left, this will form a "cowboy" bowline. Either works, but the cowboy one allows the bitter end to hang loose, which increases the odds of it getting caught up in other lines.
Finish by inserting the bitter end into the same hole from the other direction (obviously).
If you find the knot comes undone, you are putting it through the wrong side of the hole at the start. Just insert it in the other side and this particular problem solves itself. If you are on a boat, other problems may now be selected for attack. :P
Calling the framework "Retrieval-Augmented Generation" is actually an oversimplification. It's defensible, but inaccurate at best.
For RAG to succeed at scale, it relies heavily on sophisticated orchestration layers, data transformation engines (indexing) and logical loops (augmented retrieval).
Arguing semantics is important at times but being absolute about it is black and white thinking - cheap effort for a complex topic. Don't throw out the baby with the bath water!
Check out Lume: https://github.com/DeepBlueDynamics/lume. If it weren't obvious by the commits, I work on it. Probably a good reference for HOW to do good RAG, but not the ONLY way to do it.
Continuing to plug on this. Let me know if you have any issues you need squishing. Been testing mostly on Windows, but could use some Q&A on Mac and Linux. Will update the video on the website sometime this weekend. Build on!
I bake MCP tools into everything now, including doing screenshots. Any LLM can run just about every function, including resizing the window. I just watched Fabel 5 do a full usability test on a new project, copying the release cycle for my agentic terminal, relaunching the app like 20 times as it went, ensuring the move to a built and signed release was working. It installed the program like 5 times (something I do daily multiple times).
I noticed map tiles were not working and started to tell it, but then all of a sudden they reappeared and checking the logs it had found the issue and autocorrected itself.
The key here is feedback loops and systems annealing.
As for Dan, my God I love this guy. Glad someone posted it!
Github: /kordless and /deepbluedynamics (agent orchestration and terminals)
Reach me at:
kord @ deepbluedynamics
or
kord @ gmail
Build on!