What leaves your machine

This is the complete list of what Awaitful sends from your machine - not a summary, the list. The most specific thing Awaitful ever learns about a coding session is how long a sponsored line was on screen.

What leaves

• A device token, so we know which machine earned
• That an agent is thinking, and for how long
• Which surface showed the line

In wire terms, the client makes a handful of request types and nothing else:

• Ad requests - which surface is asking. That is the whole query.
• Event reports - batched events proving a line was seen: a random event identifier (so the server can drop duplicates), the event type, which ad and slate, the surface, an advisory client timestamp, and the visible milliseconds, which the server caps.
• A kill switch poll - a yes/no safety check with no body at all.
• Patch health reports (only if you enable a patch surface) - hashes of Claude Code's own bundled files, so the fleet can agree a patch is safe. Never hashes of your files.

What never leaves

• Your code
• Your prompts
• Your files or file names
• Your agent's output

No file names, no paths, no project or repository names, no clipboard, no terminal contents. Thinking detection watches the agent's own spinner indicator, not what the agent is doing. Everything that runs inside Claude Code - the patched line, the terminal script - talks only to a local helper on your own machine at 127.0.0.1, never to the network directly. The terminal script even receives Claude Code's session data on its way through and deliberately never reads it; it only passes it on to your own previous status line.

Identity, held to the minimum

A linked machine authenticates with a device token that identifies the machine, not your browsing - its narrow powers are described in Sign in and link your editor. Even the docs feedback control at the bottom of this page is anonymous by construction: it sends the page name, the vote, and your optional note. Nothing else.