Feedback that stays beside the code.
Pin a detail in your own running development app, inspect the source reference behind it, and hand the note to the person or coding agent you choose.
A local record. An explicit handoff.
Check local setup requirementsStart with the setup requirements, not public capture. The hosted capture launcher does not capture localhost.
Set it up in Velo.
Set up the existing bridge
The runbook documents @velo/bridge, a Node 20.11-or-newer local tool. Check package availability and your project root before running it; add only the development-only script it prints, including its page key.
Pin in your own app
Enable pin mode with Alt+V or the visible Pin mode control. Save a note against the element; the bridge records it in .velo/pins.jsonl with the source reference it can derive.
Inspect, then hand off
Use velo pins list to inspect the file, line, and derivation. A person or your chosen coding agent makes the change; resolving the pin requires a verifiable commit touching the referenced file.
What to know before you start
The bridge does not edit code or run an agent. Its local annotation process makes no outbound request; optional hosted login and project linking are separate network actions.
A loopback address is not proof of authority. Keep the page key, consented origins, and development-only content-security policy rules intact. No installed native app or publicly released package is established by this page.
The runbook is the setup authority
The repository runbook docs/runbooks/local-annotation.md owns the command, Node requirement, page key, origin consent, source derivation, and resolution checks. The documented command is npx @velo/bridge --root .; registry availability has not been verified here.
Give the next review a clear place to land.
Start with the setup requirements, not public capture. The hosted capture launcher does not capture localhost.