Support

RefKit is built and maintained by one person. Reports get read, and issues that break the core loop get fixed first.

Report a problem

Message @pavlutsky89 on Telegram. That is the whole of it — no ticket queue, no form, and the person who reads it is the person who writes the code.

Describe the page you were capturing if it is public, what you expected, and what happened instead. A capture JSON from the side panel is the single most useful attachment — it is what the engine sees.

Common situations

“This page cannot be inspected”

Chrome blocks extensions on its own pages — chrome:// URLs, the Web Store and the extensions gallery. This is a browser restriction with no workaround. Open an ordinary site and capture there.

Capture is refused on an ordinary site

By default Chrome gives RefKit one tab at a time — from the click on its toolbar icon until that tab goes somewhere else. The side panel outlives that, because it stays open while you browse. So a refusal on an ordinary site does not mean the page cannot be read; it means the grant has expired.

Click the RefKit toolbar icon again: the panel and draft stay open and the blocked capture resumes. Under Options → Site access, you may separately allow only the exact current origin and remove only that origin. If Chrome does not expose the URL, RefKit never substitutes an all-sites request.

Interaction states come back empty

Hover and focus styles are read from the page’s stylesheets. A stylesheet served from another origin without CORS cannot be read by any extension, so those rules are invisible. RefKit records that they were not captured rather than claiming the page has none.

The bridge will not connect

The server only listens when you start your agent with REFKIT_BRIDGE=1. Check the port and token it printed, and remember that copying the capture or DESIGN.md by hand always works as a fallback.

A colour role looks wrong

Roles are inferred from how a colour was used across the page, so an unusual layout can surprise the heuristics. That is worth reporting with the capture attached: the derivation is pure and deterministic, which means your capture reproduces the exact result on any machine.

Privacy questions

The privacy policy describes exactly what is read and stored. RefKit runs no servers and holds no data, so there is nothing to request or delete on our side — but questions about the policy are welcome.