Live data from Hacker News

Show HN: My LLM CLI tool can run tools now, from Python code or plugins

simonwillison.net

171–178 of 178 posts

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#171

Earlier quoted context omitted.

But why can we not hold humans responsible in the case of LLM? You do have to go out of your way to do all of these things with an LLM. And it is the human that does it. It is the humans that give it the permission to act on their behalf. We can definitely hold humans responsible. The question is: are we going to?

I think intent matters. Let's say you are making an AI-controlled radiation therapy machine. You prompt and train and eval the system very carefully, and you are quite sure it won't overdose any patients. Well, that's not really good enough, it can still screw up. But did you do anything wrong? Not really, you followed best practices and didn't make any mistakes. The LLM just sometimes kills people. You didn't intend…

> But did you do anything wrong?

Yes, you had a deontological blindspot that prevented you from asking, "What are some of the high-risk consequences, and what responsibility do I have to these consequences of my actions?"

Deontology's failure case is this ethically naive version that doesn't include a maxim that covers the "Sometimes peoples' reliance on good intentions relieves them of exerting the mental energy of considering the consequences which ultimately cause those consequences to exist"-situation.

One of the assumptions that bears arguing against is that the choice is framed as happening once before the system is deployed. However, this oversimplification has an unfortunate side effect - that we can't know all of the consequences upfront, so sometimes we're surprised by unforeseen results and that we shouldn't hold people to the standard of needing to accurately predict the future.

In real life, though, the choices are rarely final. Even this one, deploying the genocide-promoting LLM is reversible. If you didn't predict that the LLM promotes genocide, and then you find out it does in fact promote genocide, you don't throw up your hands and says, "I hadn't thought of this, but my decision is final." No, armed with the information, you feel a sense of duty to minimize the consequences by shutting it down and fixing it before deploying it again.

Further more, you take a systems level approach and ask, "How could we prevent this type of error in the future?" Which ends with "We will consider the consequences of our actions to a greater degree in the future," or perhaps even, "We don't have enough foresight to be making these decisions and we will stop making medical devices."

The point is that distilling the essence of the situation down to "good intentions absolve responsibility," or "one drop of involvement implies total responsibility," isn't really how people think about these things in real life. It's the spherical cow of ethics - it says more about spheres than it does about cows.

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#172
post #27

Earlier quoted context omitted.

No, I'm using uv tool just like in that issue. I'll keep an eye on it, at least I know it's not just me.

I'm also using uv tools and fixed it by doing something like this to upgrade: uv tool install llm --upgrade --upgrade --with llm-openrouter --with llm-cmd ...

Same, but put that in a llm-upgrade.sh because the list was getting quite long :)

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#173
@simonw, how much have you used Claude code? I'm wondering if it makes sense to use Claude code as the main driver, but have crafted specialized "llm" based tools for Claude to use.

I would love to only have to use llm, but with the amount of functionality that Claude code provides, it seems unlikely that llm would ever support all of its features. Also, I have realized that llm is narrower in scoop, which is something I like about the tool.

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#174

@simonw, how much have you used Claude code? I'm wondering if it makes sense to use Claude code as the main driver, but have crafted specialized "llm" based tools for Claude to use. I would love to only have to use llm, but with the amount of functionality that Claude code provides, it seems unlikely that llm would ever support all of its features. Also, I have realized that llm is narrower in scoop, which is somethi…

I use Claude Code a few times a week but honestly I'm a little intimidated by how quickly it chews through tokens!

I think it's not impossible that LLM might one day be able to handle the same kind of processes with the right collection of tool plugins and a really sophisticated system prompt but it's not something I'm shooting for right now - Claude Code is a very complicated system!

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#175

Earlier quoted context omitted.

I built a similar one to this one: https://github.com/CGamesPlay/llm-cmd-comp Looks from the demo like mine's a little less automatic and more iterative that yours.

Interesting! I like it! The conversational context is nice. The ongoing command building is convenient and the # syntax carryover makes a lot of sense! My next step is recursion and composability. I want to be able to do things contextualized. Stuff like this: $ echo PUBLIC_KEY=(( get the users public key pertaining to the private key for this repo )) >> .env or some other contextually complex thing that is actually…

https://github.com/day50-dev/ono

It's happening

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#176
post #61

Ok this is great and perfect timing -- I've been playing around with Warp (the terminal) and while I love the idea of their terminal-based "agent" (eg tool loop), I don't love the whole Cursor-esque model of "trust us we'll make a good prompt and LLM calls for you" (and charge you for it), so I was hoping for a simple CLI-based terminal agent just to solve for my lack of shell-fu. I am keenly aware this is a major fo…

> I don't love the whole Cursor-esque model of "trust us we'll make a good prompt and LLM calls for you" (and charge you for it

Huh, I've been wondering why a terminal was advertising everywhere and sponsoring random projects. I didn't realize it's not a completely free thing.

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#177

Earlier quoted context omitted.

But why can we not hold humans responsible in the case of LLM? You do have to go out of your way to do all of these things with an LLM. And it is the human that does it. It is the humans that give it the permission to act on their behalf. We can definitely hold humans responsible. The question is: are we going to?

I think intent matters. Let's say you are making an AI-controlled radiation therapy machine. You prompt and train and eval the system very carefully, and you are quite sure it won't overdose any patients. Well, that's not really good enough, it can still screw up. But did you do anything wrong? Not really, you followed best practices and didn't make any mistakes. The LLM just sometimes kills people. You didn't intend…

> But did you do anything wrong? Not really, you followed best practices and didn't make any mistakes. The LLM just sometimes kills people. You didn't intend that at all.

Whoever made and/or (mis)use the LLMs should be liable for it, regardless of intent.

If I shot someone which I did not intend to, do I get away with it? No, I would not get away with it.

Re: Show HN: My LLM CLI tool can run tools now, from Python code or plugins

#178

Earlier quoted context omitted.

I think intent matters. Let's say you are making an AI-controlled radiation therapy machine. You prompt and train and eval the system very carefully, and you are quite sure it won't overdose any patients. Well, that's not really good enough, it can still screw up. But did you do anything wrong? Not really, you followed best practices and didn't make any mistakes. The LLM just sometimes kills people. You didn't intend…

> But did you do anything wrong? Yes, you had a deontological blindspot that prevented you from asking, "What are some of the high-risk consequences, and what responsibility do I have to these consequences of my actions?" Deontology's failure case is this ethically naive version that doesn't include a maxim that covers the "Sometimes peoples' reliance on good intentions relieves them of exerting the mental energy of…

> "good intentions absolve responsibility"

Yeah, I call it bullshit. I accidentally shot someone yet I did not intend to. I am still being liable for it.

Post reply on HN