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

How to let an agent work inside your own logged-in Chrome with Axuse

An agent uses your daily Chrome or Edge session through the extension bridge.

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

Credentials. The agent acts inside your logged-in sessions, so it can reach any account you are signed into; limit tasks to ones you have approved and review actions as they happen.

Who it is forA knowledge worker who needs an agent to act inside sites they are already logged into, without signing in again.

The problemA fresh browser has no logins, so agents cannot reach dashboards or accounts the user already uses.

The outcomeThe agent runs actions in the user's existing browser session after a one-time extension setup and a verified connection.

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

  1. git clone https://github.com/ctoldigital/axuse.git
  2. cd axuse
  3. node src/cli.js setup --browser chrome --harness codex
  4. Click Load unpacked once on the extensions page that opens, then run node src/cli.js bridge verify.
  5. Ask the agent to open the site with the extension backend and report what it sees on the logged-in page.

Prompt for your agent

Using the axuse MCP server with the extension backend, open <site URL> in the user's logged-in Chrome session and report the account name or main heading shown on the page. Confirm the bridge is connected with the bridge verify command before acting.

Caveat. The README says the extension bridge drives the user's real browser, so the agent sees and changes whatever that session is already logged into.

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