Chat modes & autonomy

Blocked, on request, or autonomous — set the dial per chat.

You are always in control of how active KKHS Assist is. There are two layers to it: one overall setting that decides how forward it is allowed to be in general, and per-chat exceptions on top of that for the chats you want handled differently.

Your self-chat sits outside these modes. It is your private workspace and always works unless you block it with WhatsApp's built-in Chat Lock.

The overall setting

Set this once on the Permissions page in your dashboard. It answers a single question: when may your assistant act in a chat that is not your self-chat?

Strict — it only ever acts when you summon it with /kk. No replies of its own, no watching, no following up. The most locked-down option.
Default — it steps in where you have given it a job. If you have asked it to handle a thread or coordinate something, it stays on that thread and follows up there. It never engages a chat you have not invited it into. This is where most people should sit.
Permissive — it may also step into chats you have not invited it into, but only when one of your written rules literally covers the situation. You write those rules; without them, nothing happens.

Moving to Permissive does nothing on its own — it is the rules that do the work, and you write them. Keep each one concrete and narrow: "Reply to delivery OTP requests in the Family group" is a rule; "be helpful" is not.

Per-chat exceptions

Whatever your overall setting, individual chats can be handled differently. Just tell your assistant, from inside the chat or from your self-chat:

"Handle this thread — keep following up until it's sorted." Now it is watching this chat and acting on its own here, for the purpose you gave it.
"Stop watching this chat." Back to only acting when summoned.
"Never read this chat." Blocked entirely — see below.

You will find both lists on the Permissions page:

Watching now — every chat your assistant is currently active in, what it is doing there, when that expires, and whether you granted it or it was picked up by a rule. Autonomy in a chat is normally time-limited, not permanent, so these expire on their own unless you asked for otherwise.
Blocked chats — the chats it must leave alone, which apply in every mode, including Strict.

Blocking a chat properly

There is a real difference between "don't bother me about this chat" and "never read this chat." Only the second one is a privacy control. Say "never read <chat>" — or add it to the blocked list on the Permissions page — and your assistant cannot read, search, summarize, quote, or reply in that chat at all. A label, a note, or a mention in passing will not do it. If you ask for something in a blocked chat, it tells you it is blocked and asks whether to unblock, rather than quietly doing it.

Draft-first by default

Whenever KKHS Assist is about to send a message to someone else on your behalf, it shows you the draft in your self-chat and waits for your OK first. Approve it by replying "send" or reacting 👍 to the draft. The exceptions are when you use /kk directly in a chat — you are already standing in it, so it acts there — or when you have handed that chat over for it to handle. And the first time it messages a new contact for you, it confirms the name and the number before anything goes out.

Whose voice it speaks in

When KKHS Assist sends something for you in another chat, it goes out as you, with no assistant header — that is the default, and nobody needs to know how the message got written. When you summon it with /kk, it answers as the assistant, clearly labelled.

If you would rather it be openly the assistant in a particular chat — a work group where people should know they are talking to your EA — just say so: "act as my assistant in this group," and every message there is labelled until you flip it back.

For what your assistant can reach in the first place, see Permissions & access.