Blog

The Apps WriteAmp Refuses to Read

There is one kind of field where WriteAmp will never, ever offer a suggestion, and I want to tell you about it, because it is the feature I am most sure about and the one that is easiest to miss.

When you type into a password field, WriteAmp goes silent. Not quietly silent, like it is thinking. Deliberately, structurally silent, the way a good guest does not open the drawer marked private. No ghost text. No suggestion. No clever guess at what your master password might be, because a clever guess at a password is not a feature, it is a leak.

The line I will not cross

Here is the thing about autocomplete. To suggest the next few words, the app has to read the words before the cursor. That is the whole deal, and it is fine, because the words before the cursor are the sentence you are writing. But a password field is different. The text in front of the cursor is not a sentence. It is a secret, and reading it, even to complete it, is the one thing I decided WriteAmp should never do.

So WriteAmp checks for secure fields before it does anything else. If the field you are typing in is marked as secure, or is a password field, or belongs to a password manager, the app suppresses itself. It does not suggest. It does not peek. It does not try to be helpful. It leaves the field completely alone, including the Tab key, so nothing you type into a password field can ever be completed, stored, or learned from.

The category, not just the field

This is broader than the password box on a login page. Password managers, the apps that hold your actual secrets, are treated the same way. If WriteAmp detects it is looking at a password manager context, it does the same thing: suppresses itself entirely. The apps whose whole job is keeping secrets are the apps where an autocomplete has no business being.

And there is a subtler layer too. WriteAmp watches for field names and contexts that signal a secret, things like fields labeled for a passcode, a passphrase, or a secret key. The idea is not to catch every possible secret, because you cannot. It is to be conservative in the right direction, to assume that if a field looks like it is keeping a secret, WriteAmp should treat it as one and stay out.

Why I built it this way

Here is the honest reason, and it is not just good citizenship. If WriteAmp suggested completions in password fields, it would be a security hole, and a security hole in a tool that asks for Accessibility permissions is how you destroy trust in an afternoon. The whole product is built on the claim that your writing stays on your Mac and is never mishandled. The moment WriteAmp read a password, that claim would be a lie, and the people who noticed would be right to delete the app.

I think about it as the difference between a tool that watches your typing and a tool that watches over your typing. A tool that needs to read your sentences to help you is fine, as long as it is clear about what it reads and never crosses the line into what it should not. The secure-field exclusion is the line, drawn in code, not in a privacy policy.

This is the same instinct as the rest of the privacy story, and it is why I publish the network ledger and show you exactly what the app learns. I would rather build the boring, trustworthy thing than the clever thing that makes people nervous.

What it means for you

Practically, this means you do not have to think about it. WriteAmp will never ask you to disable the secure-field protection, because you cannot, and you should not want to. Your passwords stay exactly as safe as they were before you installed the app, because the app treats them as if they do not exist.

The privacy page has the full written version of the permissions and protections. The download is free for 30 days if you want to see the boundary for yourself. Type into a password field and watch nothing happen. That nothing is the feature.

---

On macOS 26+ Macs, Apple Intelligence mode stays free even after the trial ends — you always keep a working path to suggestions.

Written by Amit Ashwini, who builds WriteAmp and runs its marketing. More: why the Tab key beats the chat box · mini, midi, and max compared · benchmark methodology.