pair-agent

Pair remote AI agents with a browser via HTTP and setup keys.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tyhuffman7/gstack-hermes --skill pair-agent-tyhuffman7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pair-agent
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-pair-agent
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill pair-agent-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pairs a remote AI agent with your browser to enable cross-agent browsing and collaboration. It creates a one-time setup flow so the remote agent can operate in a separate, controlled tab with isolated context.

Core Features & Use Cases

  • One-time setup key prints instructions that another agent can follow to connect your browser.
  • Isolates sessions per agent with scoped access to avoid cross-agent interference.
  • Works with common agents like OpenClaw, Hermes, Codex, Cursor, or any agent capable of making HTTP requests to browse on your behalf.

Quick Start

Print the setup key and paste it into the other agent to pair 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?

To pair a remote AI agent with your browser, you print a one-time setup key from the local server and paste those instructions into the other agent. This connects the remote agent to a controlled tab with isolated context.

What agents can I use for cross-agent browsing?

Cross-agent browsing works with OpenClaw, Hermes, Codex, Cursor, or any agent capable of making HTTP requests. The remote agent follows the printed setup instructions to connect to your local server.

How does session isolation work when pairing multiple AI agents?

Session isolation works by providing per-agent tabs with scoped, read-only access to avoid cross-agent interference. This ensures each remote AI agent operates in a separate, controlled tab with isolated context.

Do I need a local server to enable remote AI agent browsing?

Yes, you need an internal local HTTP server to enable remote AI agent browsing. The local server hosts the one-time setup key and manages the isolated, per-agent tabs that the remote agent connects to.

What is the setup process to connect Cursor or Codex to my browser?

The setup process to connect Cursor or Codex to your browser involves printing a one-time setup key and pasting it into the agent. The agent then uses this key to make HTTP requests to your local server.

Can I use any HTTP client to pair with my browser session?

Yes, you can use any HTTP client or agent capable of making HTTP requests to pair with your browser session. The system relies on standard HTTP communication with your local server to establish the connection.