The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Feedbacks listing page.
Free, Apache-2.0 visual feedback, session replay and debugging context.
Show the problem with a screenshot, exact text suggestion or video + session recording. Keep the discussion, event timeline, browser diagnostics and approved project context together. Your team and coding agent can investigate the evidence, make the agreed change and record verification. The complete product is free to self-host; you provide the infrastructure and any AI tools you use.
Set up a team server first. The order is: server → install and connect the Chrome extension → project context, optional GitHub App and members → each developer's personal MCP setup. One installation serves your team; the extension does not host a server. Follow the complete setup flow, or the separate DevOps installation guide.
Website · Why Feedbacks · Self-hosting · Extension · Coding assistants & plugins · API & MCP · Roadmap · Contributing
Recording guide · Debug bundles · Text suggestions · More review workflows
Feedbacks is an early 0.x release. Each application deployment serves one organization. Public registration, billing, SSO and shared-database customer tenancy are not implemented. See architecture and deployment boundaries.
Requirements: Node.js 22 or 24, npm, and Docker Compose for PostgreSQL.
Before bootstrap, add BOOTSTRAP_EMAIL, BOOTSTRAP_NAME and a unique BOOTSTRAP_PASSWORD to your local .env. Bootstrap creates the first owner once. Remove the bootstrap password afterward. Open localhost:3000. The example database password is for the loopback-only development database.
For live client edits, run npm run dev:web in another terminal and set APP_ORIGIN=http://localhost:5173 in .env before restarting the server. Use that origin in the browser. For the standalone public website, use npm run dev:site.
Production requires HTTPS, PostgreSQL and private S3-compatible storage. Follow the deployment guide for configuration, first-owner setup and recovery.
For a registry deployment, use the public Docker Hub image and registry Compose. The illustrated storage guide maps the five prerequisites to their environment fields. Developers can install the bundled Claude Code and Codex plugins in two commands, then connect their own scoped key.
Build with npm run build:extension. Load the dist/extension/unpacked/ directory from Chrome's Load unpacked, or use the ZIP in dist/extension/. Enter your own Feedbacks server address and approve pairing in the web application. Website-wide permission is a separate optional action. Existing saved server connections remain available.
| Path | Responsibility |
|---|---|
src/server/ | Authentication, project access, business operations, persistence and transports |
src/shared/ | Typed operation inputs, outputs and descriptions |
src/web/ | Authenticated React application |
src/cli/ | Bootstrap, JSON CLI and stdio MCP adapter |
plugins/ | Codex and Claude Code plugin packages and review skills; MCP bundles generated at build |
extension/ | Chrome Manifest V3 capture and review extension |
site/ | Independently deployable public website |
tests/ | Isolated authorization, transport and database tests |
ops/ | Generic deployment configuration |
docs/ | Public contributor and operator documentation |
Start with AGENTS.md and the documentation map. Claude Code and Gemini CLI have thin adapters to the same instructions. See supported skills and client setup. For an isolated app with synthetic data and no deployment credentials:
The command builds the app and prints its loopback URL and private local access-file path. Each run has a disposable database and independent port.
check runs formatting, architecture/docs checks, type checking, tests, all builds, an isolated app smoke check and release-content checks. CI also runs the native PostgreSQL tests, dependency audit and secret scanning. A passing build is not evidence of production deployment or capacity.
The application, extension and website source are Apache-2.0 licensed. Dependencies retain their licenses. Read contribution guidelines, community standards, security reporting and trademark guidance.