How to record a site and turn it into a Wield recipe
To record a site, ask your agent to record a task, do the task once in your browser, review what would be sent, and click Send. Wield sanitizes the recording on your device before you review it. A recipe builder then drafts a recipe from the sanitized recording, and your own browser tests the draft. Recording and the builder are paid-plan features, for individuals on Pro and for Team plans. Use it when no recipe exists for a site or an internal tool.
What you need
- A Chromium browser (Chrome, Edge, Brave, Arc, Vivaldi, Opera) with the Wield extension.
- A Pro or Team plan. See pricing for current plans.
- An AI app connected to Wield, or the extension's popup.
Start the recording
From your agent, ask in plain words, 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 in record mode.
From the extension, click Record a task in the Wield popup. The recording stays on your computer until you send it.
Do the task, review, send
- Your browser opens the site. It shows that Wield is recording and asks you to click Done when finished. The first time, Chrome asks for the debugger permission and shows its own bar while recording.
- Do the task once, the way you normally would, then click Done.
- Review the page. It lists exactly what would be sent: each request, with every value you typed replaced by a placeholder and every token replaced. Click Send, or Discard to stop. Nothing leaves 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 parameters. Only your browser can reach your account, so the test runs there.
- The recipe is saved privately to your organization as
<org>:<site>/<task>. 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 stays on your computer as ~/.wield/recordings/<rec_id>.json. Your agent can retry later with that rec_id.
What leaves your computer
The extension sanitizes the recording before you review it:
| In your session | In the recording |
|---|---|
| Values you typed, such as search terms, names and numbers | A placeholder with the field's label and length |
Cookies, Set-Cookie, Authorization and other auth headers | Removed |
| Tokens, session IDs and anything secret-looking | A redaction marker, the length, and a one-way fingerprint so the builder can see that a value is reused without seeing it |
| Emails, phone numbers, IBANs, card numbers, names, addresses and messages | A personal-data marker |
| Responses | Their structure only: 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 runs its own scan and rejects anything that is not sanitized.
What the builder cannot do
The builder never sees a typed value, so a few recipes need help:
- Specific constants, such as an API version string or a client ID that is not a fixed list, are asked for, or filled in at the test run.
- Write recipes, such as bookings or messages, are drafted but not tested automatically, because a test would send real data. Run one under supervision first. The Allow window still protects every write.
- Flows with several pages of setup, or a CAPTCHA on every run, may not be recordable. Ask for them with
request_recipeinstead.
Troubleshooting
- The review page refuses to send. A value or header survived sanitization. Discard the recording, and check whether the task put a secret in a field you did not expect.
- The builder is unavailable. Your recording is kept on your computer. Ask your agent to retry with the
rec_id. - The draft fails its test. Read the failing check in the result. A check that expects a fixed value may need a parameter instead.
FAQ
Can I record without a paid plan?
Recording and the builder need a Pro or Team plan. Without a plan, you can still request a recipe with request_recipe, and the most-requested sites are built first.
Who can see my recording?
The recording stays on your computer until you click Send. What you send is the sanitized version you reviewed. Recipes you build are saved privately to your organization, and admins can share them with members only.
Is the recorded recipe public?
No. A recipe built from your recording is private to your organization. A public recipe goes through a review and live verification first, as described in the contributing guide.