DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to fill repetitive web forms with DomA in your browser with Doma

Let DomA fill and submit repeated web forms in Chrome or Edge using your own LLM key.

Authorization notice. Doma is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Do not give DomA login passwords or payment details unless you have reviewed what it will send to your LLM provider.

Who it is forAn office worker or operations staff member who must enter the same details into many web forms and wants the browser to do the typing.

The problemEntering the same data into many web forms by hand is slow and error-prone.

The outcomeThe forms you point DomA at are filled and clicked through, and you review the results before any final submission.

What you need first

  • Chrome or Edge browser
  • Your own LLM API key from an OpenAI-compatible provider
  • Node.js 20+ only if you build from source

Steps

  1. Download the latest package from Releases at https://github.com/dom-actions/doma/releases and unzip it.
  2. Open chrome://extensions or edge://extensions, turn on Developer mode, and drag the unzipped folder onto the page.
  3. Add your own LLM API key in the extension settings.
  4. Open the target form page and give DomA the task of filling it with your data.
  5. Check every field before you let DomA submit.

Prompt for your agent

Use the open-source repo dom-actions/doma as a browser agent to fill the web form at <target form URL> with the values in <data file>. Expected output: a report listing each field filled and any field left empty. Verify that the form shows the intended values before submission.

Caveat. The README says you must supply your own LLM API key, and it does not describe how the key is configured inside the extension, so check the project documentation for that step.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page