pair-agent

Pair a remote AI agent with your browser via a setup-key workflow.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/tony30552001/Genpic-master --skill pair-agent-tony30552001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pair-agent
Source: https://github.com/tony30552001/Genpic-master/tree/main/.agents/skills/gstack/pair-agent
Command: npx skills add https://github.com/tony30552001/Genpic-master --skill pair-agent-tony30552001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pair a remote AI agent with your browser to enable secure, collaborative control and delegated browsing work.

Core Features & Use Cases

  • Pair a remote agent to generate a setup key and print instructions the other agent can follow to connect.
  • Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests; remote agent gets its own tab with scoped access (read+write by default, admin on request).
  • Supports triggers like pair with agent, connect remote agent, share my browser, or remote browser access to enable cross-agent workflows.

Quick Start

Use the pairing flow to generate a setup key and connect a remote agent to your browser.

Frequently Asked Questions about pair-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pair a remote AI agent with my browser for collaborative control?

To pair a remote AI agent with your browser, you generate a setup key and follow the printed instructions to establish a secure connection. This enables delegated browsing tasks and session sharing across agents.

Can I connect OpenClaw, Hermes, Codex, or Cursor to my browser session?

Yes, you can connect OpenClaw, Hermes, Codex, Cursor, or any HTTP-enabled agent to your browser session. The remote agent receives its own tab with scoped access, defaulting to read and write permissions.

What access permissions does a remote agent get when sharing my browser?

When sharing your browser, a remote agent gets scoped access with read and write permissions by default. You can request admin access per session to enable elevated controls for specific cross-agent workflows.

Does connecting a remote agent to my browser require HTTP requests?

Yes, connecting a remote agent requires an integration path that supports HTTP requests and per-session access control. The setup-key workflow manages the secure pairing and delegates browsing tasks to the remote agent.

What are the limitations of pairing remote agents for browser access?

Pairing remote agents for browser access is limited to HTTP-enabled agents and requires a setup-key workflow. Access is scoped per session, defaulting to read and write, with admin access only available upon explicit request.