Beta package
GhostWriter — browser extension
The packaged extension, built for Chromium and Firefox. This is the real build the product ships, not a mock: load it unpacked and it runs on the profiles you open.
It reads what a prospect has published and rewrites your draft to match their register, under a Brand Voice Lock for teams. The rewrite calls a model over your own API key or the hosted API, so the extension is not useful by itself unless that is configured — the install notes below say where.
A beta package is unfinished software. Read the beta terms before you install it: they say what a beta is, what it is not, and where the limits of each of these products are.
Download
The two builds
Chromium covers Chrome, Edge, Brave, Opera and Vivaldi. Firefox needs its own package because the manifest differs.
- Chromium build — ghostwriter-1.0.0-chromium.zip (123 KB)
- Firefox build — ghostwriter-1.0.0-firefox.zip (123 KB)
- The privacy policy the extension ships with — privacy-policy.md, because it describes what leaves your machine.
Verify what you downloaded
These are the SHA-256 hashes of the two files as they sit on this server. Check yours before you load it:
0dcbc149e0c44b6670fb54cddddb41158f6dcd1fd9217c70991a776839979fd903d6397d3306bfc84491751d68118c111cb2ab5808dd471c3517d0f30c4a94f4# on Windows
Get-FileHash .\ghostwriter-1.0.0-chromium.zip -Algorithm SHA256
# on macOS or Linux
shasum -a 256 ghostwriter-1.0.0-chromium.zipInstall
Load it unpacked
# 1. make a folder and unpack the archive into it
mkdir ghostwriter-beta
Expand-Archive .\ghostwriter-1.0.0-chromium.zip -DestinationPath .\ghostwriter-beta
# 2. open the extensions page in your browser
chrome://extensions (or edge://extensions, brave://extensions, about:debugging#/runtime/this-firefox)
# 3. turn on Developer mode, then choose "Load unpacked"
# and select the folder you just createdThe extension is not in any store yet, which is why this is the only way to install it and why your browser will keep telling you it is running in developer mode. That warning is accurate.
Status
What is finished, and what is not
- The extension is built, packaged and verified for both browsers, and the release check re-runs the packages and their hashes rather than trusting a previous run.
- The companion web app and the product page are live. The payment backend is implemented and its unit tests pass; the integration suite that exercises the database and the billing path needs a reachable Postgres, so it has not run here.
- The send path is exercised end to end against a test mail server, not against a real inbox.
- What a beta tester cannot do yet: install it from a store, use it without configuring a model, or rely on the personalisation score as anything other than the product's own estimate.
Tell us what broke
A beta is only useful if the people testing it say what failed. What browser and version, what you clicked, and what you expected instead.