GhostGet

Documentation · GhostGet 0.19.0

GhostGet documentation

Start with the tutorial if you’re new. Each how-to guide finishes one task, the explanation pages cover how GhostGet protects your accounts and how it compares with browser tools, and the reference lists every supported action. The pages follow the Diátaxis documentation model.

These pages describe GhostGet v0.19.0. Each one also serves Markdown at the same URL when a request asks for it.

Tutorials

The tutorial needs only a terminal and Bun.

How-to guides

Each guide finishes one task, with its requirements and limits beside the commands.

  • Capture URLs and archive media. Choose inspection, durable Markdown capture, or one verified finite-item media archive.
  • Connect Beeper. Bind the pinned official CLI and one Desktop target, then use its supported actions.
  • Export WhatsApp history. Use four read-only actions on local WhatsApp data and write one private bundle for TextButler.
  • Connect Gmail. Create a Google OAuth desktop client, sign in from your terminal, and keep the connection past Google’s seven-day test limit.
  • Author a provider plugin. Define one operation, prove what it sends and returns, then check, test, pack, trust, and install the exact bundle.

Explanation

These pages explain how GhostGet protects your accounts and how it compares with other ways agents reach the web.

  • Security model. How GhostGet ties each action to one account, encrypts cached reads, separates reads from writes, and stops actions when a service changes.
  • How agents reach the web. Six approaches, from browser tools to reader services and integration platforms, compared with GhostGet's named actions.

Reference

The reference lists what this release supports.

  • Provider capability reference. Every supported action in v0.19.0, grouped by service and access method.
  • GhostGet Skills. GhostGet workflows packaged as programs for Claude Code, Codex, and Devin, with no model calls and a record of each run you can replay offline.
  • llms.txt. A summary of this site for agents.

Source-level contracts that belong with the code live in the repository's docs/ directory: plugin protocol, messaging automation, publishing, and local development.