Skip to the collection

agent-native · Agent Harnesses & Operator Surfaces · Verified 2026-09-20

peerd

Listed on The Agent-Native Index

peerd: the AI agent harness native to the browser

What it does

peerd is a browser extension that runs a full agent harness inside the browser you already use. The agent can drive your tabs and signed-in sessions, run sealed JS notebooks, compiled WASI tools, client-side apps, and WASM Linux VMs, and — on preview builds — talk to other peerd browsers over WebRTC.

The homepage thesis: native and cloud apps drive the browser from outside; peerd lives inside it. No background host process, no sidecar, no peerd cloud, no external tool broker. Model calls go to the provider you configured (or local Ollama / planned WebGPU). Current builds send no product telemetry to peerd.

Category honesty: this is a harness, not a remote browser-as-a-service. Browser & Web Execution in this catalog is for managed / remote browser sessions. peerd inverts that: the user’s browser is the runtime, hypervisor, and control plane.


Agent-facing interfaces

How agents onboard

Interaction pattern: Browser extension (load unpacked) — local harness, no peerd account

git clone https://github.com/NotASithLord/peerd.git

See the full onboarding section in the dossier.

Protocol surface

Interface Detail
Browser extension Load extension/ (Chromium) or packaged Firefox XPI
Homepage / thesis https://peerd.ai
Source / docs https://github.com/NotASithLord/peerd — CLAUDE.md, SECURITY.md, docs/
Preview A2A peerd-distributed WebRTC mesh (omitted from store builds)
MCP Not shipped
Hosted API None — “no backend”

Verification

Last verified 2026-09-20.

Sources: