WeaveCrawl in plain terms.
Works in your own Chrome. Remembers each site it learns. Asks before it submits, uploads, buys or deletes.
In short
- It asks you before it submits, uploads, buys or deletes.
- It works in your own Chrome. It is in private testing.
What it does for you
- Let your agent do the web work you hate.
- Works in your own Chrome.
- Remembers each site it learns.
- A stopped job picks up where it stopped.
Who stays in control
- Submit, upload, payment and delete need a person's yes.
- Only you can loosen the rule. Your agent cannot.
- Robot checks (captchas, tests that ask a person to prove they are human) go to a person, and the click spot is outlined. It never solves them automatically.
What is stored and encrypted
- Your vault (the place where saved secrets are kept), cookies and login sessions are encrypted on the machine that runs it.
- The key sits on the same machine. That protects a stolen file, not someone using your account.
- Your data lives on your own devices and is synced between them. We keep no customer data on our servers.
- Usage data is collected only if you allow it. It is masked, off by default, and we ask at install.
- By default, WeaveCrawl listens only on your own computer. A connection from another machine has to prove who it is.
How it runs
- Three ways to run it: your Chrome, its own browser, or a desktop app.
- It is in private testing. Join the waitlist; we give testers access by hand.
What we do not promise yet
- We do not claim it gets past robot checks. It hands them to a person.
- A readable list of approvals is not built yet. Each run keeps a local technical log on your computer.
- You cannot yet delete or export what it remembers about one site.
- WeaveCrawl holds no security certification yet.
For your technical readers
Your agent connects to WeaveCrawl over MCP (a standard way for agents to use tools).
Join the waitlist; we give testers access by hand.