FAQ

#Does Wield see my passwords, cookies or results?

wield.run doesn't. Recipes run in your browser, and requests go from your browser to the site. Results go from the extension to wield-mcp to your AI app, on your computer. wield.run serves recipes; it never receives your sessions or what sites send back. In the site's tab, a recipe may read the one token it names (a CSRF or bearer token) to use in that site's own requests; the security model lists exactly which. The logs in ~/.wield/logs show every host that was contacted.

#Can the agent book or buy something without me?

No. Every recipe that changes data stops before the first such request and shows an Allow window in your browser, with what will be sent. Deny is the default, and no setting or policy can turn the window off.

#Which sites work?

The public recipes cover travel, marketplaces, appointments, food, shopping and housing, mostly in Germany, Austria and the US so far. More are added by request. Ask your agent to list_sites, or see wield.run. For anything else, use request_recipe, or record it on a Pro or Team plan.

#Which browsers and systems?

Chrome, Edge, Brave, Arc, Vivaldi, Opera and Chromium, on macOS, Windows and Linux. Firefox and Safari aren't supported: Wield needs Chromium's native messaging and extension APIs.

#Does my browser have to be open?

Yes. Recipes run in a tab of the site. The window can be in the background; Wield opens background tabs and reuses tabs you already have.

#How is this different from a browser agent that clicks through pages?

A browser agent reads screenshots and clicks, step by step. That takes minutes and costs model tokens for every page, and it fails when a layout changes. A Wield recipe makes the same requests the site's own page makes and returns data in about a second, with no screenshots. Agents still help with the parts recipes don't cover. The benchmark on wield.run compares both on the same tasks.

#Is it allowed?

Wield acts as you, in your browser, at a human pace: one task, a few requests. Public recipes are reviewed for each site's terms, and per-site pacing keeps traffic polite. You're responsible for how you use a site, as when you use it by hand.

#What does it cost?

The extension, wield-mcp and the public recipes are free. Running recipes costs nothing, because it happens on your computer. Plans add private recipes, the recipe builder and team features (pricing).

#What happens when a site changes?

Each recipe has a test plan. Health checks and (opt-in) outcome reports mark recipes that stop working, and Wield runs the last version that worked while the recipe is repaired. Versions are kept, and an agent can pin one.

#Can I use Wield without an AI app?

Yes. npx -y wield-mcp demo runs a few sites from the terminal. The MCP tools work with any MCP client, including your own scripts through an MCP SDK.

#How do I uninstall?

1. Remove the extension from your browser.
2. Remove wield from your AI apps; init made a backup of each config file.
3. Delete ~/.wield.
4. Delete the run.wield.bridge.json files listed by doctor. On Windows, also delete the run.wield.bridge registry keys under HKCU\Software\…\NativeMessagingHosts.