Recently, I've found my preferred way to interact with lots of products is getting Claude to use a CLI tool, and then just talking to it out loud about what I want to happen.
So I made a CLI tool for Ghost, to see what it would be like in our own product - it's called ghst and it essentially makes everything in the UI available by CLI (and MCP).
Mostly this was an exercise in doing it just to see if I could - but it turned out to be a lot more interesting than I expected.
We've spent 10+ years focusing on having a clean, well designed interface for Ghost. It's something we care a lot about, and spend a lot of time on.
But within about ~1hr of using Ghost via Claude/CLI, it was hard to imagine going back to caveman-clicking around a browser to get something done. Particularly for complex or compound tasks that might require visiting several different areas of the app.
Follow this publication
Copy this handle into a Wirepost reader:
@ten-minute-test.pages.dev
A name, not a hash — short enough to say out loud. Your reader
looks it up on this domain and then checks the identity below for itself, so the name is
a convenience and never the proof.
Or the full address, which also records where you started:
It records that you started here, at post 2. If the
address ever serves an older copy of this publication than the one you were given, your reader
will say so instead of quietly showing you less.
Underneath that address, this publication is one permanent identity:
feed://bagaaieraazuc4j5e3qu4pgijif275li67qz4q5nsinmj3y2bny3vw2kul7ca — a hash of its own first record, not a domain name.
It is what your reader checks every post against, and it does not change if this page moves to
a different address.
No Wirepost reader? Use
Atom or RSS in any feed
reader you already have. Those carry the posts, but not the signatures — an ordinary feed reader
has no way to check who wrote them.