Website feedback your coding agent can act on.
Right-click any part of your UI. Leave a comment. Claude Code, Codex, or any file-reading agent can see it and make the change.
Right-click what you want changed and leave the note where it belongs. Fidibaku keeps the comment attached to that element.
The comments are ordinary files in your project. Claude Code, Codex, or another coding agent can read them, map them to the code, and start implementing.
Your agent changes the real code. Refresh the page, review the result, and leave another comment if it needs one more pass.
For a running local website:
npx -y fidibaku review http://localhost:3000For a static HTML page:
npx -y fidibaku review ./page.htmlRight-click anywhere and type your feedback. Fidibaku saves it as *.comments.md and *.comments.json beside your project.
No account. No browser extension. No hosted service.
Tell Claude Code, Codex, or your agent of choice:
Read the open Fidibaku comments, fix the UI, and mark each one resolved.
Each comment keeps the exact UI element, label, and context. Your agent gets actionable feedback instead of a paragraph describing where to look.
Landing pages, product interfaces, visual QA, HTML prototypes, generated reports, and design polish all use the same loop:
Right-click → comment → agent acts.
Single-file decks and single-page apps work too: each comment stays on the slide, route or hash it was made on. See views.
How it works · Security · Contributing
MIT



