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

RefKit is in closed alpha, so reports come back directly to the maintainer. 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.

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 — check the Interaction states line in the panel.

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, confirm you granted the loopback permission during pairing, 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.