←back to thread

Building a Mac app with Claude code

(www.indragie.com)
165 points gdudeman | 2 comments | 06 Jul 25 14:55 UTC | HN request time: 0.5s | source
Show context
flenserboy ◴[06 Jul 25 17:22 UTC] No.44482473[source]▶
Has anyone tried this for command line applications? This could be a great way to develop some very specific/corner-case tools.
replies(1): >>44482615 #
simonw ◴[06 Jul 25 17:40 UTC] No.44482615[source]▶
I write CLI tools with LLMs all the time. I even have a custom Claude Project that teaches the LLM to use inline script dependencies with uv so I can "uv run script.py" without first having to install anything else: https://simonwillison.net/2024/Dec/19/one-shot-python-tools/

I have a collection of tools I've built in this way here: https://tools.simonwillison.net/python/

replies(2): >>44482806 #>>44483052 #
kiitos ◴[06 Jul 25 18:48 UTC] No.44483052[source]▶
A CLI tool is a native binary that I can run directly via e.g. `/path/to/binary`. If I need to use `uv run ...` to execute something, then that thing isn't really a CLI tool, it's an interpreted script, which relies on an interpreter that needs to be available as a pre-requisite, and all of the numerous complications that follow from that...
replies(1): >>44483583 #
1. simonw ◴[06 Jul 25 20:03 UTC] No.44483583[source]▶
Use this as your shebang line:

  #!/usr/bin/env -S uv run --script
https://treyhunner.com/2024/12/lazy-self-installing-python-s...

I don't think requiring all CLI tools to be "native binaries" makes sense. Plenty of popular CLI tools are not compiled binaries. The Python and Node.js ecosystems run on those.

replies(1): >>44504717 #
2. kiitos ◴[08 Jul 25 22:46 UTC] No.44504717[source]▶
You're describing scripts, which require interpreters like I guess uv or Node or Python. A CLI tool is a native binary.