The story
The hard part of a reply is the first sentence
You open your inbox and most of what is there needs two lines back. None of it is difficult. Somebody wants a date confirmed, somebody wants to know if you saw the file, somebody is following up politely on a thing you have already decided.
What is expensive is starting. The cursor sits in an empty box. You type a greeting and stop, because the next sentence needs the shape of the whole reply and you have not built it yet. So the message goes back to the pile, and you answer it tomorrow with an apology at the top.
henna exists for that gap and nothing else. It reads the message you highlighted and writes the obvious version of the reply — the greeting, the acknowledgement, the structure, the sign-off. Not because those parts are clever, but because they are the parts that stop you.
Then it stops and hands the draft to you. henna does not fill your composer and it does not press Send. It puts the draft on your clipboard, and you paste it in yourself.
That step is the whole design. An assistant that types straight into your composer is one distracted moment away from sending something you did not read. Copying is a small friction that guarantees a person saw the words — and it is why henna can be useful without needing to be trusted.
The same discipline runs through the draft itself. Where a reply would need a
fact henna cannot know — a date, a price, an amount — it writes
[date] rather than something plausible. A confident wrong number
in an email you send is worse than an empty box, and a tool that produces one
has cost you more than it saved.