For developers shipping agentic products

Give your agents a visible, trustworthy way to operate software.

This runtime connects models to real interfaces with overlays, relay-backed sessions, MCP tools, browser runtime support, and desktop accessibility hooks so agents can point, narrate, act, and verify.

  • Open source Apache 2.0
  • Rust runtime with TypeScript and Python SDKs
  • Browser overlays plus real macOS accessibility support

Why this exists

Most agent demos hide the hardest part: earning user trust while acting.

Show your work

Highlight, annotate, and move a visible agent cursor so users see what the system is about to do before it does it.

Connect real runtimes

Use a relay, SDKs, and MCP tools instead of ad hoc glue code every time you want an agent to touch a live interface.

Operate beyond the DOM

Pair browser overlays with native accessibility access for desktop workflows that can’t be reduced to webpage automation alone.

The stack

Built like infrastructure, presented like a product developers can actually adopt.

Agent surfaces

MCP client, TypeScript SDK, Python SDK, CLI, custom WebSocket clients

Runtime core

Relay, tool dispatch, verification, playbook orchestration, session routing

Execution surfaces

Browser overlay, extension replay runtime, macOS accessibility backend

Protocol-first

Structured wire types, session-aware routing, and explicit tool semantics.

Human-legible

Overlays, narration, and verification make agent behavior inspectable.

Composable

Use one layer or the full stack: SDK, overlay, extension, MCP, or playbook engine.

Explore

Turn the landing page into a full story for evaluation, adoption, and proof.

Pilots

Start with a real workflow

For teams that want a managed Browserbase-style path to visible agent sessions before self-hosting.

Request a pilot
Architecture

How the runtime is put together

The relay, tools, overlay, extension, and accessibility path explained in one technical view.

Open architecture page
Use cases

Where visible agent interaction wins

Support flows, onboarding, QA, and internal tools where showing intent matters as much as acting.

Open use cases page
Quickstart

Get a truthful developer path

The shortest path from repo clone to a running relay, overlay, and SDK-driven interaction loop.

Open quickstart page
Brand system

Keep naming abstract until launch

Shared content tokens make the future product name, tagline, and CTA language easy to swap.

Open marketing README

Proof points

There’s enough real product here already to market honestly.

Implemented surfaces

The relay, MCP server, playbook engine, browser overlay, extension, TypeScript SDK, Python SDK, and macOS accessibility backend are all present in-repo.

Trust-oriented mechanics

Visual highlighting, narration, replay, verification, and structured tool errors create a better operator experience than blind background automation.

Clear current limitation

Desktop accessibility is strongest on macOS today; Linux and Windows are promising but not yet the production-default path.

Visual assets

Build concrete proof, not just copy.

System diagram

Reusable runtime diagram for docs, marketing pages, and decks.

Diagram showing agent surfaces flowing through runtime core into overlay, extension, and accessibility surfaces.

Social preview

Starter open-graph style panel for social sharing and repo previews.

Social preview graphic for the marketing workspace.

Developer feel

Show the path in code, not just diagrams.

import { CoPilotClient } from "@ghostrider/sdk";

const client = new CoPilotClient("ws://127.0.0.1:4201/ws/agent");
await client.connect();

await client.highlight("#submit-btn", { label: "Review this action" });
await client.annotate("#submit-btn", "Submitting after validation");
await client.clear();

Start here

Use this workspace as the outward-facing home for the product story.

Keep the technical docs focused on implementation truth, and let this area become the polished front door for developers evaluating the project.