- Home
- Skills
- Testing & Debugging
- Multi-account testing in one Chrome
Works with the AI Agents you already use
Multi-account testing in one Chrome
Test an app as several users at once: admin and customer side by side, hand-offs between roles, and whether user B can open user A's data. Each tab has its own login, all in your own Chrome. Free, via Qiksy Bridge.
Free
Multi-account testing in one Chrome
Example session with this skill installed
I'm signed in as the manager on staging. Open a second tab as the employee (test login is in .env.test), send a leave request from there, approve it as me, and check the employee sees it approved. Then check the employee cannot open my team report by its URL.
- Read your context and instructions
- Compiled the multi-account testing in
Two users, one browser
| Tab | User | How |
|---|---|---|
| 1 | manager (you) | your own tab, already signed in |
| 2 | employee | qa_open_isolated { session: "employee" }, signed in with the test login |
Hand-off: leave request
Employee tab: qa_fill_json filled the leave form (dates 10 to 14 Nov, reason "Family trip") and pressed Send. Status shows
Pending.
2.
Manager tab: reloaded Inbox. The request is there, from the right person, with the right dates. Pressed
Approve.
3. Employee tab: reloaded. Status changed to Approved and a notice says who approved it.
The hand-off works both ways.
Access across accounts
Copied the manager's report address /reports/team/412 into the employee tab.
GET /api/reports/team/412 200
The page rendered the full team report, salaries column included.
The employee can read the manager's report by its URL. The menu hides the link, but the server does not check the role.
Suggested fix
- Check the role on
GET /api/reports/team/:idand answer 403 to non-managers. - Add a test: employee session, same URL, expect 403.
Screenshots of both tabs are attached. Want me to retry after the fix?
Connects securely to your tools. The creator never sees your data.
About this skill
A lot of bugs need two people to show up. The manager approves what the employee sent. The seller answers the buyer. User B changes an id in the address and opens user A's order. To test that you usually juggle a second browser profile or an incognito window, and an agent cannot drive either.
This skill lets your agent open extra tabs in the Chrome you already use, each with its own private session: separate cookies, localStorage and IndexedDB. Every tab is a different signed in user, and your own login keeps working untouched.
What the agent checks
- Access across accounts: an address that belongs to user A, opened as user B, must answer "not found" or "forbidden".
- Role limits: buttons and pages the lower role must not have.
- Hand-offs: a request, message or approval goes from one user to the other, with the right sender and state.
- Sessions that do not leak: sign out in one tab, the other stays signed in.
- Live updates arriving in the other user's tab.
Each finding comes with what each user did, what the other one saw, the request with its status and the server's error body, and a screenshot of each side.
How
It uses Qiksy Bridge, a free MCP server for the Chrome you already have open (qa_open_isolated for the extra sessions). Setup is the Qiksy extension plus one npx qiksy-mcp line in your agent's config.
Price
Free. Prefer to do it by hand without an agent? Our free MultiLogin Tabs extension does the same for people: several accounts on one site, one tab each.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Chrome only, with the free Qiksy extension and its "Agent control" switch on. Isolation separates cookies, localStorage and IndexedDB per tab inside one browser; logins kept outside them (client certificates, the OS keychain) are shared. Custom dropdowns render only in the tab in front. 2FA prompts and captchas are left to the person.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 13 days ago
- Free with an Agensi account
- Software
- Qiksy Chrome extension (free)qiksy-mcp (npm)
Node.js 18+Google Chrome