Authorization notice. Axuse is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA journalist or researcher who needs to check a claim on a specific web page before publishing or citing it.
The problemScreenshot-based agents guess pixel positions and often misclick or miss small text, so the answer is slow to get and hard to trust.
The outcomeThe agent returns the matching element text and its destination, based on the accessibility snapshot rather than an image guess.
What you need first
- Node.js 22 or newer
- A Chromium-family browser (Chrome, Edge, Chromium, or Chrome for Testing), or AXUSE_BROWSER set to its path
- git to clone the repository
- Codex or Claude Code installed as the MCP host
Steps
git clone https://github.com/ctoldigital/axuse.gitcd axusenode src/cli.js doctorcodex mcp add axuse -- node /abs/path/axuse/src/cli.js mcp- Ask the agent to open the target URL, find the link, and report where it goes.
Prompt for your agent
Using the axuse MCP server from the repo at <repo path>, open <target URL>, find the link labeled <link text>, and report its destination. Check that the reported destination matches the link target shown in the accessibility snapshot before answering.
Caveat. Axuse needs a local Node.js 22 install and a clone of the repo, so it is not a copy-and-paste setup for non-developers; use the non-developer onboarding guide in the repo for that path.
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