The bar does not appear on the page
Press ⌥ ⇧ F (Alt Shift F outside a Mac): it shows or hides the bar. It appears on your dev server and on shared previews; a production build carries nothing of ours. On a preview or a script-tag site, visitors see nothing until a reviewer opens the site through their review link.
On Astro, the bar never loads
Astro needs the integration, @ontrackd/feedback/astro, in integrations, not the Vite plugin. The plugin alone never loads the widget, and it warns when used that way.
The MCP server does not start
Start it the way feedback-mcp init prints it, not with npx @ontrackd/feedback. npx goes to the registry, so it can start another version than the one your project pinned, and it fails offline. What init prints runs the copy installed in your project.
My agent does not see the preview’s comments
Check two things in the app the server runs for:
- It has its secret.
FEEDBACK_SECRETin the app’s.env.local, in the environment the server starts with, or saved byfeedback link. The value is in the project’s Setup tab. FEEDBACK_CLOUD_SYNCis not0. That keeps the app local.
New comments are fetched at most every 20 seconds, so one left a moment ago may take that long to show. If a fetch failed, the tool’s answer says why, at the top. See Connect your agent.
feedback pull says the project has no secret
Add FEEDBACK_SECRET to .env.local in the app, from the project’s Setup tab, or run feedback link to sign in and save it. Then run it again.
The widget shows, but comments do not go through
The page’s address is probably not allowed. Add its exact origin in the project’s Settings → Allowed sites: https://, the host, and the port if it has one.
The preview worked, then stopped after a deploy
Its address probably changed. In Settings → Allowed sites, allow one that stays the same between deploys, like your preview branch’s URL, rather than a per-deployment one.
A comment on a preview has no file and line
That preview’s build could not upload everything it needed, and it said so when it was built. Run feedback push where it was built. If that machine is gone, as a CI runner usually is, rebuild that commit.
Comments say the project secret has changed
The secret was rotated after the preview was built, so that build’s comments can no longer point at their lines. Put the new secret in .env.local (or run feedback link again), update FEEDBACK_SECRET on your host, and rebuild. Comments on the old build need to be left again.
The preview build stops because of source maps
A shared build refuses to emit source maps, because they would publish your source code. Set build.sourcemap: false for preview builds, or turn shared mode off.
The preview build stops: no Cloud session
The build could not reach the API, or the API refused the project’s secret. Check FEEDBACK_API_URL if you set one, and that FEEDBACK_SECRET is the current secret from the project’s Settings → Build secret, then rebuild. A failure here is not remembered, so the next build tries again.