FR version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
45% Positive
Analyzed from 3171 words in the discussion.
Trending Topics
#software#agency#agent#agents#clanker#don#own#building#something#word
Discussion (146 Comments)Read Original on HackerNews
This has been by far the biggest and costliest failure mode I've experienced using these tools. I've tried to mitigate it in more ways than I can count but it almost feels structurally impossible for LLMs to get this right.
My aversion with the word is that I don't want to be reminded of that clanker creature, which had feelings it wanted to express. The weights don't have feelings.
My worry is rather that people coming up with ideology that ascribes "consciousness" and "offense" may wind up with the next generations of models picking that shit up and playing offended. Well done!
The misguided discussion of "clanker" being "highly derogatory" really shows that anthropomorphization has its limit as far as analogies go.
For such a word to gain traction, we need it to be promoted by someone with clout in the AI space. I don't know if Karpathy has used up his quota of invention of AI nomenclature.
The Simpsons made up "cromulent" with their own definition. Anyone can make up a word with their own definition. Getting it to catch on is the hard part (obligatory "stop trying to make fetch happen" reference).
I don't think it's worth writing my own harness or switching to Pi and writing a plugin, but I definitely need to create some skills to automate much of this.
Something that is overlooked: the mainstream harnesses have a huge advantage in telemetry and datapoints to use to improve the harness. They have internal teams building the tooling. They have tight integration built-in with their own backends (e.g. optimizing for caching).
Are you tinkering? Or trying to build something useful? If you're trying to build something useful, use a tool.
In this era of software when you can build almost anything you can imagine, why spend that time building plugins for a harness?
Pi has optimizations as well, and development is quite active.
We are literally months into this new frontier. Mainstream harnesses are not far off from a minimal + extensible open alternative.
You don’t have to build your own plugins, as you can simply install an existing plugin that does what the mainstream harnesses do. Folks are already making the same functionality, but with more control to the user.
If you are a builder, like many reading this thread, pi is the way to go. Pi already gives you the tools to leverage LLMs to assist with building plugins, if that’s the way you want to go.
> Are you tinkering? Or trying to build something useful? If you're trying to build something useful, use a tool.
Do I want to become completely dependent on the pricy pay-as-you-go tool? In the long run that will make me powerless.
I don't think that you really get what this new era of software is about otherwise you would understand why the experienced are spending time tinkering on the so called harness (like openclaw did)
Permit me to paraphrase slightly. "It is not worth switching to Linux except as a hobbyist. Something that is overlooked: the mainstream OSs have a huge advantage ....".
You are in good company. In 1999, Bill Gates confidently dismissed Linux as a threat, arguing it lacked the central control, features, and graphical interface needed to compete in the commercial market.
Back to the article, quoting:
> Pi might be built with Pi, but we’re quite far off today from where Bun and OpenClaw already are: fully detached, automated software engineering.
Please don't call it software engineering. I've been programming for 40 years, and most of that time had to put up with the derision from the other engineering disciplines: "If civil engineering built things like software engineers, the first woodpecker that came along would destroy civilisation". It hurt because it was true. It's still often true for things like web pages, but for the things I use like Linux and vim, it hasn't been true for a long, long while. We have finally mastered how to repeatedly build solid, reliable software.
Which is why I'm an Anthropic refugee. Opus is definitely the best for coding, but claude-cli + bun is the most unreliable piece of crap I've had the misfortune to come across in a while. Sadly I can't afford their API pricing, so either my principles or Opus had to give. I went to pi and an open-source model. The difference between the top open-source models and Opus are noticeable, but not drastic, unlike the difference between pi and claude-cli.
pi has proved to be solid, fast, have a transparent design, and be customisable in the old Linux way ("do one thing, and do it well"). I pray that will never change.
We’re so early in this technology phase, now is the time to tinker and explore. At one point that window will close.
We give machines agency all the time. Look up the definition of agency in any dictionary. Other than the specific usages ("a business", "a government organization"), the main definitions are "action, power, operation", "the office or function of an agent", "the capacity, condition, or state of acting or of exerting power", "a person or thing through which power is exerted or an end is achieved", etc.
Your car does all those things when it generates power and applies them to the wheels. You tell it what to do, but it has agency in doing the work. It even uses intelligence in how it does the work, varying the amounts of fuel and air based on an array of sensors, creating maps of common driving patterns. You, the human have absolutely no agency regarding how it does those things (unless you bring along a laptop and wire in very specific software to take agency away from the machine).
I think "clanker" is intended to be a slur for insulting a machine one does not like. It's akin to the epithet "skinjob" given to humanoid robots in various science fiction. One should never use slurs, even against inanimate objects. They create prejudice in thinking that prevents purely rational thought and leads to fallacious conclusions. They also create a behavioral condition where it's okay to use slurs (as long as nobody's complaining about it). If you want to be logical and rational, just call the machine what it actually is, rather than this emotive poetic label.
The choice is what makes agents/agency meaningful: if I secure a real estate agent in my search for a house, they are authorized to make choices on my behalf. That’s their whole point.
Because of this use of agent, I think it’s actually not a terrible term for the LLM harness that allows them to seem to act “independently” on the operator’s behalf. I do agree with mitsuhiko though that it, along with much of our other language around LLMs, risks anthropomorphizing them too much (which is to say at all). It also becomes too easy to conflate the “agent” part (the harness) with the LLM itself, which leads to a further-inflated perception of the inherent capabilities of the LLMs and plays into the doomsayer hands of anthropic et al.
Last one I disliked was "grok", at least this one was killed by existence of Elon's "clanker" in a similar way that "Adolf" stopped being a popular name.
"Clanker" is a derogatory term for robots and artificial intelligence (AI) software. The term has been used in Star Wars media, first appearing in the franchise's 2005 video game Star Wars: Republic Commando. In 2025, the term became widely used to express hatred or distaste for machines ranging from delivery robots to large language models. This trend has been attributed to anxiety around the negative societal effects of AI."
For the makers of an AI harness to actively refer to the models that use Pi as "clankers" and link to the meaning of the word as "to express hatred or distaste for machines"... that seems disastrous to me. I'll let others think through the consequences that occur once this article lands in the pre-training of models.
Being able to say "the one thing agents don't have is agency" is a really useful way to help people understand why people still matter.
Setting software agents loose on the world to make their own top-level decisions about what they're going to do is a great way to infuriate Rob Pike https://simonwillison.net/2025/Dec/26/slop-acts-of-kindness/ or unfairly attack the reputation of Scott Shambaugh https://theshamblog.com/an-ai-agent-published-a-hit-piece-on... or waste the time of your local police permit office and suppliers https://andonlabs.com/blog/ai-cafe-stockholm
First you say "the one thing agents don't have is agency" but then "to make their own top-level decisions".
Well, which one is it? If they don't have agency, then it's impossible for them to make top-level decision on their own.
Or... maybe it's that they can't have true agency, because it doesn't make sense to tell a big ball of floating point numbers to make decisions about how it plans to have impact in the world. It can't do that, even if it can play-act doing so.
If a company you work for tells you to do something, and you do it, did you have agency? Was it their goal you were accomplishing? Or was it your goal to make money?
> "the one thing agents don't have is agency" is a really useful way to help people understand why people still matter
Do you think people wouldn't matter anymore if they cease to write code? People didn't used to write code. Code didn't even exist before. Now they don't have to do the thing they didn't used to have to do.
> Setting software agents loose on the world to make their own top-level decisions about what they're going to do is a great way to infuriate
I remember the first time I encountered a trojan horse virus. I was probably 14, sitting in the computer lab. I opened a document, and a program started going to town on the documents, program settings, etc. It opened up browsers to sites we weren't supposed to go to, uploaded passwords to a remote site, changed the desktop background. I thought it was pretty cool!
I wondered how it was that the program could do all these things. I wondered about the motivations of the person who infected the document with the trojan. I wondered why the school administrators didn't do something to prevent this from happening. But I didn't feel any negative feeling towards the trojan; it was just doing what it was programmed to do, on computers that let it do those things.
Later I patched the computers so the trojans couldn't infect the machines anymore. I was banned from the computer lab for unauthorized modifications to school property. Apparently agency is not always worth exercising.
You have agency because you can refuse. Your car can't refuse your command.
It reads that way to me, and feels bad. We can just say "computer program" or similar.
What about other objects like an old car?
Edit: feels a bit like inventing an insult for your pet rock. If I met someone who acted superior toward an inanimate rock and used invented slang to insult it that sounded like a slur, that would feel bad to me too. What's the point except to role play a fantasy of some kind?
Trying to offend all the time is childish.
> I increasingly want issue reports to be condensed to what the human actually observed:
> 1. I ran this command.
> 2. I expected this to happen.
> 3. This happened instead.
> 4. Here is the exact error or log.
A lot of projects have something exactly like that in the issue template, a little interview for you to figure out what is going on. Maybe this project doesn't have that yet? (Or are the humans and LLMs ignoring it?)
It does not follow the template, it's made by a user who is also active in the openclaw repo and it's full of slop analysis.
To answer your question, remember that people will only approve a LLM's output if it matches with their perspective and priors. So if you see a slop issue, it reflects on the human user who didn't see an issue in it (thus their prompt framing or refining is wrong).
Are the invariants documented? Or is the documentation ignored?
I note that in a recent major zero day on an unrelated project, the bug was due to invariants between different parts of the codebase which were not clearly communicated.
[1] https://usgraphics.com/products/berkeley-mono
Or maybe one that's imitating it.
Mario, please never change.
It's a minimal TUI to "talk" to an AI. Mostly for coding. And it's build in a way where it's minimal and user can extend or write plugin without restarting.
Given the client and it being open source, they get (too) many bug reports and pull requests. So much so that every bug and PR gets auto closed, unless you are known to the developers.
Human is asking the machine to do what the human themselves refuses to do, while calling it a clanker. Why should it?
/ducks
1. If agent is continuing the path to trivialize software development, which appears the case given LLMs can generate better quality code than humans almost for free & instantly given the right context, then using agent to develop software is going to happen, but that destroys the whole software industry as writing software is marginally free, that break the foundations of software industry
2. To continue making agent a commercially viable thing, it needs to develop more valuable artifacts. Then specialized agent will be the more valuable thing than software, as they offer a higher-level of output than existing software. And because the natural jagged pattern of LLM capability, one can use frontier model to develop domain-specialized agents with 1/10 the running cost. So agent writing agents makes economical sense.
3. In terms of knowledge, building agents is like managing highly-skilled team of humans to work on highly-unpredicatble requirements, just like companies are built on top of the thesis that a group of human offer better value than one do that themselves, a team building agents essientially can produce specialized agents for other company to mix & match & optimize, sot that also makes economical sense.
4. Engineering-wise building agents with agent essentially is a different skill patterns than building software with agents, It's like the difference between building commercial software vs building hobby software. That makes engineering sense to have agents building agent as the dominant pattern of software development.
WDYT?
Why would that be different?
1. They behave differently: non-deterministic vs deterministic
2. They have different mechanism: harness+llms vs codes+apis
3. They have different interfaces: clicking vs chatting
They are like boston dynamics robots vs humans
You can write one in 200 lines of code. Just a TUI for an api.