joshu-browser-handoff

Hands a shared Camofox browser tab to the owner via a signed mobile noVNC link for sensitive steps.

108|11|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/db-aeon/joshu-oss --skill joshu-browser-handoff-db-aeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: joshu-browser-handoff
Source: https://github.com/db-aeon/joshu-oss/tree/main/integrations/hermes/skills/browser/joshu-browser-handoff
Command: npx skills add https://github.com/db-aeon/joshu-oss --skill joshu-browser-handoff-db-aeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents driving a shared browser hit a hard stop at logins, 2FA, payments, and irreversible confirmations that only the owner can complete. This Skill stages the page, locks agent browser control, and hands the live tab to the owner on their phone until they finish. ## Core Features & Use Cases - Live HITL handoff: Creates a signed handoff link with embedded noVNC and an owner brief using browser_handoff_request, then polls browser_handoff_status or completes via browser_handoff_complete. - Agent lockout during handoff: Blocks agent navigate/click/type while pending, pins the tab URL, and still allows browser_snapshot for post-completion verification. - Channel-aware delivery: Sends the handoff URL over SMS, jChat, or email, and returns results on the same channel (SMS replies go in assistant text, never via nylas_send_message). - Use Case: While booking a hotel, the agent compares options and fills dates, then hands off the payment page so the owner enters card details and 3DS on their phone; the agent verifies the confirmation page afterward. ## Quick Start Ask the agent to stage the payment or login page in the shared browser and send you a handoff link so you can complete the sensitive step on your phone.

Frequently Asked Questions about joshu-browser-handoff

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

FAQPage Schema
How do I hand off a browser session to a human for login or payment?

Navigate the shared Camofox tab to the staged page, take a snapshot to verify state, then call browser_handoff_request with a short owner brief. Include the returned URL in your outbound message so the owner can complete the step via embedded noVNC on their phone.

When should I use browser handoff instead of SMS action guard approval?

Use handoff when the owner must drive the browser for a sustained period, such as entering credentials, card details, or 2FA codes. Use action guard only for a single Y/N approval of one agent-proposed click while the agent stays in control.

Can the agent keep browsing while a handoff is pending?

No. While a handoff is pending, agent browser_navigate, click, type, press, and back are blocked and the server pins the tab URL. The browser_snapshot tool still works so the agent can verify the outcome after completion.

How do I deliver handoff results over SMS?

After the owner finishes, take a browser_snapshot and put the answer directly in your assistant reply text, which Joshu sends as SMS automatically. Never use nylas_send_message or email for SMS-originated handoffs, as that triggers action-guard approval and skips the SMS reply path.

What does the browser_handoff_already_pending error mean?

It means a handoff request is already active for the session. Poll the existing handoff with browser_handoff_status instead of creating a second request, and wait for the owner to complete it.