Web AI × local development

Turn Web AI into a long-lived development partner for your machine.

Keep ChatGPT and other Web AI as the main reasoning surface. MCP gives them safe local tools, Herdr keeps workspaces, terminals, services, and agents alive, and the optional browser extension can carry local changes back into the Web conversation.

Let my agent install it Overview

Web AIChatGPT and other Web conversations remain the primary planner.

MCP→

Herdr-MCPWorkspaces, PTYs, servers, and agents survive individual turns.

WorkspacePTYGit / FilesAgent

↖Browser continuity (optional)Local events, recovery, and handoff can return to the Web conversation.

One path down, an optional path back

MCP is the core execution path; the browser extension is an optional continuity return path.

1Web AI

ChatGPT and other Web conversations remain the primary planner.

2MCP

Read, search, patch, Git, and execute only what the task needs.

3Herdr worksite

Workspaces, PTYs, servers, and agents survive individual turns.

↺Browser continuity (optional)

Local events, recovery, and handoff can return to the Web conversation.

Built for long-running development

↗

Reuse Web AI reasoning

Keep using the Web AI subscription and interface you already know instead of binding local execution to another model entry point.

□

Persistent worksite

A conversation can end while workspaces, terminals, services, isolated working copies, and agents keep running.

⇉

Direct tools + any agent

Use deterministic tools for small operations and delegate complex work to replaceable local agents in parallel.

↻

Optional two-way loop

Install the browser extension only when unattended jobs, page recovery, or cross-conversation handoff need a return path.

03 · Agent-assisted install (recommended)

Fastest path: let your coding agent install it

Give this prompt to your local coding agent. It should read the complete install protocol first, then automate everything that does not require you personally.

Install and configure Herdr and herdr-mcp for me. First read and follow this guide end to end: https://raw.githubusercontent.com/whshang/herdr-mcp/main/docs/i18n/en/agent-install.md . Install the local herdr-mcp runtime from GitHub Releases, not from a git clone. Pause only when I personally need to sign in/create a Cloudflare API Token, or when I need to add the herdr Connector/app in ChatGPT. Automate and verify everything else.

Read the complete quick agent install protocol

You take over only twice

1. Cloudflare sign-in / token

The agent takes you to the right page; sign in or create the required token, then hand control back.

2. ChatGPT Connector

Add the herdr Connector in ChatGPT and complete OAuth; the agent continues configuration and verification.

Choose your path

Agent-assisted install (recommended)

Copy the prompt above and let your coding agent follow the full protocol.

Manual install

Use the human install reference when you want to control every step yourself.

Browser extension (optional)

Install from the Chrome Web Store for conversation continuity, the status HUD, and Browser Control Center. In a bound ChatGPT Project, a fresh manual conversation can simply say “continue”; Herdr searches durable continuity and asks for confirmation when identity is ambiguous.

06 · Landscape

Why another project?

Coding MCP runtimes, persistent runtimes, remote workers, and Codex-first bridges are all valid. Herdr-MCP focuses on the Web-first + persistent-worksite combination.

Read the ecosystem and architecture comparison →