#Forms & multi-step flows

Hand Arachne a sign-up, a submission, or a multi-page process, and it carries the whole thing through — pausing for your approval exactly where you ask.

#Overview

Plenty of work on the web is not a single click — it is a sequence. You fill in a field, move to the next page, confirm a choice, review a summary, and submit. Arachne handles these flows end to end. You describe the outcome you want, supply the details the flow needs, and Arachne moves through the pages the way a person would: reading each step, entering the right information, and continuing until the process is complete.

This is where Arachne's carry-through and its permission levels matter most. A multi-step flow often includes a moment of real consequence — a submission, a confirmation, a final "send." You decide in advance how much freedom Arachne has at those moments. It can carry the whole flow on its own, or it can stop and wait for your word before each change, so nothing irreversible happens without you. Every step is verified before it is reported done, so a "completed" from Arachne means the flow actually went through.

#What you can do

  • Complete sign-ups and registrations — create an account or register for something by providing the details once and letting Arachne enter them across the form.
  • Submit forms — fill in and submit single-page or multi-field forms, from short contact forms to longer applications.
  • Move through multi-page processes — follow a flow that spans several screens, carrying your information forward from page to page and finishing the process at the end.
  • Sign in where you have connected an account — let Arachne operate services you have authorized, so a flow that requires being signed in can proceed.
  • Review before the point of no return — have Arachne pause at the submission or confirmation step so you can check what it is about to do.
  • Set how much freedom each flow gets — keep yourself in the loop for every change, let Arachne work freely inside your workspace, or let it run the whole flow automatically.
  • Watch the flow happen live — see each page and each entry as Arachne works, so you can steer the first run.
  • Keep the result — the outcome of a flow is saved as an artifact you can find again, reopen, and reuse.

#How to use it

  1. Describe the outcome. Say what you want done — "sign me up for this," "submit this form," "complete this application" — and point Arachne at the page or process if you already have a link.
  2. Give the details the flow needs. Provide the information up front: the name, contact details, choices, or text the form will ask for. The more complete you are, the fewer interruptions later.
  3. Choose a permission level. Decide how much freedom Arachne has for this flow:
    • Plan first when you want to see the approach before anything is entered.
    • Ask before acting when you want to approve each change as it happens — ideal for the submission step.
    • Work in your workspace when the flow stays inside a project you are working in.
    • Act automatically when you trust the flow and want it run start to finish.
  4. Watch the first run. Keep the live view open so you can see each page and each field. This is the best moment to catch a wrong choice and steer.
  5. Approve the consequential steps. Where you set Arachne to ask, it pauses before each change — most importantly at the final submit or confirm — and waits for your go-ahead.
  6. Confirm the result. When the flow finishes, Arachne reports back with the verified outcome, saved as an artifact you can reopen.
Important

Stopping always works immediately, at any permission level. If a flow is heading somewhere you did not intend, stop it — nothing is locked in while you are still in control.

Tip

For anything that submits, sends, or registers, start at Ask before acting so Arachne pauses before the irreversible step. Once you have watched a flow run cleanly, you can give it more freedom next time.

#Examples

What you ask:

text
Sign me up for this newsletter with my work email, then stop before you confirm so I can check it.

What you see: Arachne opens the page, enters your work email, moves through the sign-up steps, and pauses at the confirmation. You review, give the go-ahead, and Arachne completes the registration and reports it done.

What you ask:

text
Fill out this three-page application with the details I gave you and submit it.

What you see: Arachne works through each page in the live view — entering your details, carrying them forward, and reaching the final summary. After the submit step is verified, it confirms the application went through and saves the result as an artifact.

What you ask:

text
Go through this checkout flow but ask me before the final purchase.

What you see: Arachne moves through the multi-step flow up to the last step, then stops and asks for your permission. You approve, and it completes the final step — or you decline, and nothing is submitted.

#Tips

  • Front-load the details. Give Arachne everything the form will ask for in your first request, so it can move through the pages without stopping to ask you for each field.
  • Reserve approval for what matters. Use Ask before acting so the pauses land on the consequential steps — submissions, payments, confirmations — rather than every keystroke.
  • Watch the first run of any new flow. Seeing each page live lets you correct a wrong choice early, before it carries forward.
  • Turn a recurring flow into a saved skill. If you complete the same kind of flow often, save it as a reusable skill so you can run it later by name without re-explaining each step. See Saved skills.