Wield

Your AI agent uses websites in about a second, with a fraction of the tokens, through your own browser and logins.

Wield makes your AI agent fast and cheap on websites. Claude, Cursor, Codex or any MCP client gets the answer from the site's own requests in about a second, instead of a browser agent clicking through pages for a minute. Your agent reads only the result, so it uses a fraction of the tokens. WHY WIELD - Fast: on 24 real tasks in our tests, Wield answered in 0.9 seconds at the median. A browser agent took 78 seconds. - Fewer tokens: the browser agent read about 43,000 tokens per task. With Wield your agent gets just the answer. - Not blocked: sites that refuse cloud browsers still work, because the requests come from your own browser. - Private: Wield uses the login already in your browser. Your passwords and cookies stay on your computer, and your tasks never run on our servers. WHAT IT CAN DO Search trains, flights, homes, products, jobs, events and restaurants on the sites you already use. The current list is at https://wield.run/sites. Missing a site? Ask for it from your agent, or record it once and turn it into a recipe with the recipe builder at wield.run (Pro and Team plans). HOW IT WORKS 1. Your agent calls Wield through a small local program, the Wield MCP server and bridge. Set it up once with one command from wield.run/install. 2. Wield picks a recipe from the public registry at wield.run. A recipe describes the requests a site's own pages send for one task. Recipes are data, not code, and every one is signed. 3. This extension runs the recipe in a tab of that site, with your login. 4. The result goes back to your agent on the same computer. YOU STAY IN CONTROL - The popup lists every request Wield sent: site, path, status and time. - Nothing changes on a site until you click Allow. For bookings, messages and orders you see exactly what will be sent, and no answer in two minutes counts as no. - New sites ask you first, and then Chrome asks too. - Requests go only to the site a recipe names. Recipes can't set cookies or run code. - Pause any site in the popup. Companies can restrict Wield with Chrome Enterprise policy. WHAT WIELD DOESN'T DO - It doesn't store, read or send your passwords. - It doesn't send your browsing or results to us. Only when you build a recipe does a sanitized recording go to wield.run, after you review it. - No tracking and no ads. Public recipes need no account. REQUIREMENTS The Wield MCP server and bridge on the same computer (macOS, Windows or Linux, with Node.js 20 or newer). Setup: https://wield.run/install. Without them the popup shows "Bridge offline". SITES Wield can open a tab of a site from its public recipe registry without asking first. Every other site asks you, then Chrome asks you too. OPEN SOURCE We intend to publish the extension, bridge, MCP server and recipe format as open source (MIT). Every recipe is already public at wield.run. Privacy policy: https://wield.run/privacy