Guides
Record a site
Show Wield a task once in your browser and get a tested, private recipe for your organization.
When no recipe exists for what you need (an internal tool, a back office, a site nobody has covered yet), you can show Wield the task once. The recipe builder turns the recording into a recipe, and your own browser tests it.
- On Free you get 3 builds a month. A working recipe is submitted to Wield's public registry, and once a reviewer approves it, it works for everyone, usually within a day.
- On Pro and Team it's saved privately to your organization and works right away. You can still share it with everyone from the dashboard (pricing).
From your agent
Ask your agent, for example: "Record how I check an order's status on shop.example.com and make it a Wield recipe." The agent calls request_recipe with mode: "record". Then:
- Your browser opens the site and shows "Recording on shop.example.com: do the task, then click Done". The first time, Chrome asks for the debugger permission and shows its own "Wield started debugging this browser" bar while recording.
- Do the task once, the way you normally would, then click Done.
- Review. A page lists exactly what would be sent: the requests, with every value you typed and every token replaced by a placeholder. Click Send, or Discard to stop. Nothing has left your computer before this click.
- The builder drafts a recipe from the sanitized recording. This takes about a minute.
- Your browser tests the draft with the draft's example params. Only your browser can reach your account, so the test has to happen there.
- It's saved privately to your organization as
<org>:<site>/<task>, and your agent can run it right away.
If the builder is unavailable or your plan's builds for the month are used up, the recording is kept on your computer (~/.wield/recordings/<rec_id>.json), and the agent can retry later with that rec_id.
From the extension
Click Record a task in the Wield popup, do the task, click Done, review and Send. The recording is saved on your computer. Then ask your agent to build it: "Build a Wield recipe from my recording rec_…".
What leaves your computer
The extension sanitizes the recording on your computer before you review it:
| In your session | In the recording |
|---|---|
| Values you typed (search terms, names, numbers) | A placeholder with the field's label and length |
Cookies, Set-Cookie, Authorization and other auth headers | Removed |
| Tokens, session ids, anything secret-looking | {"redacted": "token", "len": 36} plus a one-way fingerprint, so the builder can see that a value from response 2 is reused in request 4 without seeing the value |
| Emails, phone numbers, IBANs, card numbers, names, addresses, messages | {"redacted": "personal"} |
| Responses | Their structure: JSON shapes, and for HTML the tags, ids and classes without text |
| Images, fonts, analytics and ad requests | Dropped |
The review page runs a final check and refuses to send if a typed value or an auth header survived. The builder on wield.run runs its own scan and rejects anything unsanitized.
What the builder can't do
The builder never sees a value, so a few recipes need help:
- Specific constants (an API version string or a client id that isn't an enum) are asked for, or filled in at the test run.
- Write recipes (booking, sending) are drafted but not tested automatically, because testing would send real data. Run one supervised first. The Allow window still protects every write.
- Flows that need several pages of setup, or a CAPTCHA every time, may not be recordable. Ask for them with
request_recipeinstead.
Without a plan
request_recipe with the default mode adds the site and task to the public request list. The most-requested sites are built first, and you can see the list on wield.run. You can also write a recipe yourself (contributing).