sylin-org/ghostlight

Give your agent a visible place in the browser you already use.
A launch brief moves from empty form to ready for review, in full view.
Install Ghostlight | See where it fits | Installation guide | Trust Center
Your agent needs a page you are signed in to. The usual answer is a second, empty browser that
knows none of your sessions, driven by a model that has to learn Chrome internals to get anything
done.
Ghostlight gives it a tab group inside the Chromium you already have open. The work happens in
front of you: watch it, pause it, take the wheel, or end the session. The model says what it wants,
and Ghostlight does the browser part.
Ask an agent to read a page, complete a form, handle a file, follow a popup, or investigate a
failed web workflow. Ghostlight carries the task across tabs and browser changes while keeping the
browser work and its controls on your machine.
> A light left burning, so the halls stay safe.
Where it stands today
The published release is 1.3.14. It is available as the GitHub release
v1.3.14, the npm package
ghostlight@1.3.14, the Chrome Web Store adapter v1.3.12, and the MCP Registry record
org.sylin/ghostlight 1.3.14, all observed on 2026-10-02 and recorded in
docs/public-status.json and the
release custody record.
What you get
- **24 catalog tools**: 23 browser tools covering tabs, navigation, reading a page, screenshots,
semantic clicks and hovers, form input, file upload, scripts, waits, short flows, dialogs,
diagnostics, and workspace switching, plus one policy tool that explains the authority in
force. One call carries the intent; Ghostlight performs the browser steps behind it.
- **One truthful answer per call**: what happened, what changed in the browser, what is ready, and
whether running it again is safe. Ghostlight writes that answer, never the page, and adds at most
two recovery steps of its own. When an effect is uncertain it says so rather than guessing, and
never proposes a replay that could submit a form twice.
- **A desktop workbench** in the tray that shows work as it happens.
- **Your machine, and only your machine.** Ghostlight runs as you, reaches your browser over local
IPC, and keeps a payload-free local record. No account, no telemetry, no activation service, no
update ping, no hosted control plane, and no second hidden browser. The only network traffic is
the browsing you asked for.
Your first five minutes
You need Chrome, Edge, Brave, or Chromium 125+, an MCP client, and Node.js for the installer. The
service you run afterward is native Rust.
1. Install Ghostlight and register the MCP clients it finds:
2. Add
Ghostlight in Browser
from the Chrome Web Store.
3. Restart an MCP client if it does not hot-reload tools.
4. Give it one small, read-only task:
> Open https://example.com/ in a new Ghostlight tab, summarize the page, and tell me which tab
> you used. Do not click, type, submit, or change the page.
A sky-blue Ghostlight group should appear in your browser. The agent opens the page, reads it, and
names the exact tab it used. That one prompt proves the whole connection without authorizing a
click or write. Next time, it reuses that group and the nearest tab it already owns on that site,
so repeated work stops littering your tab strip.
If a step needs attention, run:
doctor checks the client entry, local service, browser connection, and extension, then names the
next action. The installation guide covers targeted clients, source
builds, updates, uninstall, and symptom-led recovery.
From one page to a whole workflow
Ghostlight is at its best when browser work has a thread to follow:
- **Pick up where you are signed in.** Open an application in the Chromium profile you chose and
work with the session already there. Credentials stay with the browser.
- **Finish the interaction.** Navigate, fill forms, upload files, resolve dialogs, wait for page