How it works
How it works
Nothing to install on the phone, nothing clever hidden anywhere. Three steps, each with a drawing, and then the details that matter.
-
Link your WhatsApp
Open the panel, go to the WhatsApp tab and scan the code with your phone (WhatsApp → Linked devices → Link a device). From WhatsApp's point of view uautsapp is now a linked device, like a laptop running WhatsApp Web. Your phone keeps working as it always did.
One phone per workspace. Unlink whenever you like, from the phone or from the panel.
-
Your conversations come into orbit
WhatsApp hands a new device the recent past — weeks, often months, of every conversation. uautsapp keeps it in a cache that belongs only to your workspace, encrypted with keys that exist nowhere else. From then on, new messages arrive as they happen. Media is not fetched until something asks for it.
Want the deeper past? Export a chat from the phone and import it. Nothing is ever doubled.
-
Connect Claude, then ask
In Claude, add uautsapp as a custom connector. Claude registers itself and sends you back to the panel to approve it — and that screen is where you choose: read only, or read and send. Then ask in your own words. "What did Ana say about the invoice?" "Who is waiting for an answer since Monday?" Claude picks the tools; you see every call in the activity log.
Step by step, for claude.ai, Claude Desktop and Claude Code.
What syncs, and what does not
Personal conversations and groups sync. Status updates and channels are ignored. Conversations you exclude in the settings are never cached — and if they had been, they are purged the next time the service starts.
A message deleted on the phone is deleted from the cache: the text is dropped and it falls out of the search index.
When Claude sends a message
Sending is off by default. A client or a token has to be created with sending allowed; a read-only one is refused by the tool itself, server-side, not talked out of it.
Even then there are limits you control: so many per minute, so many per day, and the same text cannot reach more than a handful of chats in an hour — the thing that stops the tool being turned into a bulk sender, whether by a confused model or a malicious prompt. Every send is written to the log with the recipient and a fingerprint of the text.
What the activity log shows
Every tool call, with which client made it, when, and from where. Every send. Every sign-in and every approval. And the rare occasion when someone from uautsapp opens your workspace for support — when, who, and why.
Unlinking
From the phone's Linked devices, or from the panel's WhatsApp tab. Syncing stops; the cache stays until you delete the workspace, so Claude can still search what was already there.
Ready when you are.
Two days free, from the moment Claude first connects.