Authorization notice. Doma is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Remote script. Running npm install pulls third-party packages, so review the dependency list before running the install in a sensitive environment.
Who it is forA developer who wants a custom browser automation agent based on the open-source DomA core for their own internal use.
The problemA prebuilt extension does not fit a specific workflow, and the developer needs to change the agent's code.
The outcomeA locally built DomA extension that includes your changes, loaded into Chrome or Edge for testing.
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
- Install Node.js 20 or later.
- Run
git clone https://github.com/dom-actions/domaand thencd doma && npm install. - Run
npm run build, then load dist/desktop/open as an unpacked extension with Developer mode on. - Run
npm run devto work on the code while developing, and read CONTRIBUTING.md before you send changes. - Confirm your change works in the browser and review the PolyForm Shield License terms before distributing or offering a product.
Prompt for your agent
Clone the dom-actions/doma repo, install dependencies, and run the build so that the output is in dist/desktop/open. Expected output: a built extension folder and a short note of the build result. Verify that dist/desktop/open exists and loads as an unpacked extension in Chrome or Edge.
Caveat. The license forbids using this software or derivatives to provide a product or service that competes with DomA or its commercial edition, so a custom build must be used within those terms.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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