Web actions for agents
Install the CLI or tell your agent to. It reads a page, archives one media item, or acts in an account you connected, and returns the result instead of a browser to steer.
Free and MIT licensed · macOS and Linux with Bun 1.3.14 · Release v0.18.45
$ ghostget read https://example.com
---
title: "Example Domain"
source: "https://example.com/"
clipped: "2026-09-05"
platform: "generic"
capture_status: "complete"
capture_method: "http"
capture_scope: "page"
---
# Example Domain
This domain is for use in documentation examples without needing permission. Avoid use in operations.
[Learn more](https://iana.org/domains/example)ghostget read for a public page: a short record of what was captured and how, then the page as Markdown. Nothing was saved.
Public-page read recorded on September 5, 2026; command updated for Ghostget.
How it works
Your agent asks for a supported action, such as reading an inbox or saving a video. Ghostget checks the inputs and the account, makes the request, and returns a structured result. Sign-in details stay inside Ghostget.
The agent asks for an outcome, such as reading an inbox or preserving one video.
Ghostget finds one installed, supported action. There is no general browser or request tool to fall back on.
Ghostget checks the exact service, account, and risk level, then makes one exchange. Your sign-in can reach only the service that action needs.
Your agent gets a structured result, a note of anything incomplete, or a saved record that the outcome is not yet known.
No browser to steer
Browser-using agents stream the live page into the model and let it choose each click. With Ghostget, the agent asks for an outcome and only the result comes back.
Page state and screenshots never enter the agent’s context. It never sees a cookie or token, and there are no selectors for it to guess. If a service changes how it responds, the affected action stops instead of improvising a click path.
Some pages need a real browser to render. For those, Ghostget runs its own browser internally, at most two at a time, and the agent can’t steer it. The agent-browser comparison shows how that works.
Measured
Your model provider charges for everything the agent reads. On September 22, 2026, ghostget read returned these bytes for each URL, compared with the raw HTML the URL serves. Every row was one HTTP capture with no browser and capture_status: "complete".
| Page read | ghostget returns | Raw HTML | Smaller by |
|---|---|---|---|
| Wikipedia article | 15,021 bytes | 145,617 bytes | 9.7× |
| GitHub repository page | 79,955 bytes | 647,690 bytes | 8.1× |
| This site’s security guide | 7,220 bytes | 41,295 bytes | 5.7× |
| Hacker News front page | 7,311 bytes | 34,791 bytes | 4.8× |
| example.com | 345 bytes | 559 bytes | 1.6× |
At roughly four bytes per token, that Wikipedia read costs about 3,800 tokens where the raw page carries about 36,000. The table counts bytes because tokenizers differ.
Browser-driving agents pay again on every step, because the page comes back into context each time. A July 2026 comparison matrix cites Microsoft’s reported figure of about 114,000 tokens for a typical Playwright MCP task, against about 27,000 for its disk-first CLI. Treat any single figure as an estimate.
What it does
Providers
Each entry shows how Ghostget connects to that service and links to its supported actions in this release.
32 supported actions
Accounts · Bridges · Contacts · Conversations · Messages · Presence · Reactions
Local app
26 actions run through a pinned version of Beeper's official CLI, and 6 are fixed reads from Beeper Desktop. Writes need a preview first, and Ghostget never resends a write whose outcome is unknown.
8 supported actions
Comments · Content · Feeds · Media · Posts · Profiles
Public web, no sign-in + Signed-in web session
1 supported action
Listings
Public web, no sign-in
1 supported action
Feeds
Signed-in web session
1 supported action
Feeds
Signed-in web session
2 supported actions
Feeds · Listings
Signed-in web session
2 supported actions
Organizations · Profiles
Public web, no sign-in
3 supported actions
Contacts · Messages
Official API
3 supported actions
Comments · Feeds · Posts
Signed-in web session
8 supported actions
Comments · Contacts · Content · Feeds · Media · Messages · Posts · Profiles
Signed-in web session
5 supported actions
Conversations · Messages
Local app
13 supported actions
Articles · Comments · Contacts · Feeds · Organizations · Posts · Profiles · Reactions · Replies
Official API + Signed-in web session
11 supported actions
Comments · Content · Feeds · Flair · Media · Messages · Posts · Profiles
Signed-in web session
13 supported actions
Articles · Comments · Content · Feeds · Media · Messages · Organizations · Posts · Profiles · Subscribers
Signed-in web session
4 supported actions
Feeds · Media · Posts · Profiles
Signed-in web session
3 supported actions
Comments · Feeds · Profiles
Signed-in web session
1 supported action
Profiles
Signed-in web session
3 supported actions
Registry sites · Registry tools
Public web, no sign-in
4 supported actions
Contacts · Media · Messages
Linked device
16 supported actions
Articles · Comments · Content · Feeds · Likes · Messages · Posts · Profiles · Replies · Threads
Official API + Signed-in web session
5 supported actions
Comments · Feeds · Media · Posts · Profiles
Signed-in web session
The bundled webmcp adapter reads tool schemas
from the public WebMCP Registry
for 1,802 listed sites covering
15,282 published tools, and calls the
1,509 declared read-only,
with no account needed. How WebMCP works with your agent ·
Use WebMCP sites
Provider names identify compatible services and do not imply endorsement. Counts are for release v0.18.45. Browse every supported action
Get started
Any agent that can run terminal commands can install Ghostget for you. To do it yourself, install Bun 1.3.14 on macOS or Linux, then install the @hraness/ghostget canonical release archive. Your first public-page read needs no account, API key, or vault.
bun add --global https://github.com/hraness/ghostget/releases/download/v0.18.45/hraness-ghostget-0.18.45.tgz
ghostget read https://example.comOptional: add the Agent Skill
npx skills add hraness/ghostget#v0.18.45
Teach your agent the Ghostget commands after installing the CLI. With Bun, run bunx skills add hraness/ghostget#v0.18.45 instead. View the Ghostget Agent Skill on skills.sh.
Success prints Example Domain as Markdown without saving it. Next, save a page or connect one service. Provider setup starts with ghostget adapter sync-bundled --json.
Interfaces
Ghostget runs on your machine. It has no hosted API or MCP server, so your agent can do the same things from a skill, a terminal, or typed code.
Add the release-matched capture, archive, provider, and publishing guide to an agent that can run commands.
npx skills add hraness/ghostget#v0.18.45Use stable human output or JSON from a terminal, a script, or an agent tool call.
ghostget capabilities --jsonImport validators and types without starting the CLI or reading anything on your machine.
import { isProviderPluginId } from "@hraness/ghostget"Menu bar and terminal
Review connected accounts, permissions, pending approvals, and recent activity in your menu bar or terminal. The menu also opens recent output files. Your agent keeps using the same CLI and SDK.
Run ghostget menubar for the menu companion, and ghostget menubar install to start it at login. The downloaded companion is unsigned; ghostget menubar doctor explains platform setup.
Prefer the keyboard? Stop the menu with ghostget menubar stop, then run ghostget tui. Tab moves between six sections, Enter opens actions, and ? shows help. Only one control client runs at a time; public-page reads need neither.
Safety and limits
Account state and saved results stay on your machine. Requested work contacts the source service, and your agent receives the results you give it.
ghostget vault import-x accepts a 1Password field reference instead of a pasted secret; Ghostget verifies the X user and stores the token privately on your machine. It is a token importer for one provider, not a general password manager.Compare
Most “browser use” tools give the model a browser to drive, on your machine or in the cloud. With Ghostget, the agent asks for a reviewed outcome and gets back one result. Compare the approaches in detail.
| Approach | Best fit | How Ghostget differs |
|---|---|---|
| browser-use | Open-ended, multi-step browsing where the model observes the page and decides each step | The model chooses no steps. Each call runs one reviewed action or stops with an error. |
| Playwright MCP | Giving an existing agent live browser controls, with the accessibility tree streamed into context per step | One result per call. No page state goes back into the agent’s context. |
| agent-browser | Shell-level browser steering an agent composes itself: open, click, type, snapshot | Ghostget runs agent-browser internally for pages that need rendering, and the agent can’t steer it. |
| Browserbase + Stagehand | Managed cloud browser sessions at scale, with proxies, stealth, and session replay | Runs on your machine with no remote browser, and never falls back to a browser when an action is missing or has changed. |
| Pipedream Connect | Hosted integration breadth and managed end-user authentication across thousands of APIs and prebuilt tools | A smaller local set whose provider actions and implementations are reviewed before they run. |
| Apify MCP | Discovering and running eligible Apify Store Actors through a hosted MCP service, with access to results and storage | Each provider action and implementation must be named and reviewed before it can run. |
| Ghostget | Repeated account and page work where you want to know exactly what the agent can do | Encrypted local copies of reads, a preview and a record for every write, and actions that stop when a service changes. |
Questions
Any agent that can run commands: Claude Code, Codex, Cursor, Gemini CLI, or your own. The optional Agent Skill teaches it the Ghostget commands and their limits in one step.
No. Install the CLI and read a public page. You connect a service only when you want its actions, and each connection is stored on your machine. Hraness Accounts sign-in is optional and is not needed for page reads or provider setup.
It uses a sign-in you already have for a service, on this machine, and keeps it out of your agent’s hands. Each sign-in is bound to one account and one service, in a locked local store the agent cannot read. Ghostget’s normal outputs do not include cookies or tokens. The calling agent keeps the separate tools and permissions you give it.
Nothing. Ghostget is free and MIT licensed, with no hosted tier and no paid plan. You pay your model provider and any service subscriptions you already have.
No. The CLI and SDK send no analytics to ghostget.com; they make only the network requests the action you chose requires. This website counts page views with cookieless analytics and honors Do Not Track. The privacy page explains both.
macOS and Linux with Bun 1.3.14. Actions that read iMessage or Apple Photos need macOS. Beeper actions need Beeper Desktop on the same machine, and WhatsApp reads need a linked device.
No. Ghostget supplies a CLI, an SDK, and a macOS menu-bar companion. Your agent brings the model and the plan; Ghostget manages account permissions, approvals, and the records of its actions.
Yes, in two cases. When a page can’t be read without rendering it, Ghostget runs its own browser, at most two at once; page reads try a single HTTP request first. Some signed-in provider actions, such as certain LinkedIn and Instagram reads, also run inside a contained browser session. In both cases the browser accepts no selectors, coordinates, or scripts from the caller.
If a request left the machine and its response was lost, the effect may already exist. Ghostget keeps that uncertainty visible and settles it from separately obtained evidence instead of sending the request again.
Page capture, media archives, encrypted reads, and 139 supported actions across 21 services. ghostget capabilities shows what is installed and available on your machine, and the provider list names every action in this release.
Documentation
Each guide covers the current release, the commands to use, and the limits that apply.
Install the CLI, read a public page, then choose saving, account setup, or local controls.
Choose between an inspection, durable Markdown capture, or one verified finite-item media archive.
See every provider action available in the current release and the access method it uses.
How Ghostget keeps sign-ins on your machine, ties each action to one account, and handles a write whose outcome is unknown.
Define one operation, prove what it sends and returns, then check, test, pack, trust, and install the exact code.
Every guide organized by job: tutorial, how-to, explanation, and reference.
Essays
How named actions differ from browser control, virtual machines, device policy, and the other ways people try to limit what an agent can do.
Why Ghostget exposes named operations instead of falling back to general browser control.
Why a failed inbound identity check does not establish a safe outbound operation.
Why a virtual machine around an agent does not define a safe web operation.
How WebMCP sites publish tools, what the public registry adds, and the three commands Ghostget runs against it.
browser-use, Playwright MCP, agent-browser, and hosted browsers compared side by side with Ghostget’s named actions.
PayPal crashed on GrapheneOS after a root-detection check. Device-policy attestation is not a named web operation.
A rumour of a bug can be enough for agentic search. A search direction is not a named web operation.
Omarchy’s default desktop let any user process escalate to root. A host privilege grant is not a named web operation.
Made by
Ghostget is built by Hraness, a software studio in Puerto Rico. We build tools that give AI agents memory, context, web access, and a record of their work, and we make apps and sourced archives for people.
Related
Start with one public page and no account or API key. Connect a service when you need its actions.
