In short:
ak-chrome-profilelets your agent work inside the Chrome profile you use every day, with the Google account and cookies you are signed in with. It opens the URL with thechrome-profilecommand, then attaches the agent to the exact tab it just opened through Chrome DevTools MCP. If you do not need a real signed-in state, do not use it:ak-agent-browserorak-web-testingfit better.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when the agent needs the exact account, cookies or workspace you are signed in to in Chrome, for example to read an internal dashboard. You do not need it for ordinary browser testing: use ak-agent-browser, ak-web-testing or the project's existing Playwright tests instead.
flowchart LR
A["Task needs a browser"] --> B{"Need a real Chrome profile?"}
B -->|"No"| C["ak-agent-browser or ak-web-testing"]
B -->|"Yes"| D["ak-chrome-profile"]
D --> E["Tab in the right profile, agent can read and act"]
D --> F["Setup missing: stop, guide step by step"]It rests on 3 things:
| Concept | Question | Example |
|---|---|---|
| Profile key | Which profile does the agent open the page in? | Key work points to the company email, key side-project points to the profile whose display name contains "Side Project" |
| Browser bridge | Can the agent read the tab it just opened? | Chrome DevTools MCP in auto-connect mode. The first time, Chrome asks for remote control permission, you allow it, the agent calls once more |
| Tab anchor | Among all tabs of all profiles, which one was just opened? | The URL gets a #cdp-profile=work&cdp-open=6d4f8b0a9c1e2d33 suffix. The agent picks the tab with that exact cdp-open code, then checks cdp-profile |
The CLI only reads profile descriptions, never cookies or passwords, and the agent asks you before using a profile you have not configured. The trade-off: the skill only supports Google Chrome stable.
Sample prompt (reading a page behind sign-in):
/ak-chrome-profile Open <internal dashboard URL> with the work profile.
Read the metrics table at the top of the page and summarize it for me.
Constraint: read only, do not click any button or submit any form.| Flag | What it is for | Since ak |
|---|---|---|
--profile | Takes a profile name; declared only, behavior not described | 2.15.0 |
--tab | Takes a tab title or URL; declared only, behavior not described | 2.15.0 |
Below is the detailed version: the run flow, 5 situations with prompts, each flag explained, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-chrome-profile: let your agent work in your real Chrome" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-chrome-profile". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-chrome-profile
