Write directly in any textbox
Trigger AutoClaw inside Gmail, Notion, Slack, LinkedIn, and other browser workflows without leaving the page.
It opens directly in the active field, reads the current page only when you ask, optionally references other tabs, and uses a split memory model that keeps durable context in the cloud while leaving short-term thread state on-device.
Core Product Model
Cloud long-term memory
Per-user profile, preference, fact, and note memory retrieved before generation.
Local short-term thread
Recent interactions stay in the extension namespace for the current browser profile and account.
Explicit context
No hidden cross-tab scraping, no password or payment field reading, and no automatic form submit.
Why it exists
Trigger AutoClaw inside Gmail, Notion, Slack, LinkedIn, and other browser workflows without leaving the page.
AutoClaw only reads visible page context when the user explicitly invokes it, instead of running as a background listener.
Stable facts, company context, and writing preferences are stored per account and retrieved before generation.
Recent task context stays in the extension on the current browser profile and is not turned into a server-side memory vault.
Architecture
AutoClaw treats stable identity and current task state as different problems. Durable context belongs in an account-level cloud store. Recent task state belongs in the local extension runtime, where it stays close to the current browser session.
Use Cases
Privacy boundary
That model is what makes the product usable in real workflows without quietly becoming a surveillance layer in the browser.