Loading...
FEEDCHAT pins feedback on real web pages, then moves it through AI triage, Slack, Jira, and GitHub.
</body><script src="https://feedchat-web-81776548145.asia-northeast3.run.app/feedchat-widget.js" defer></script>The CTA copy does not make the next step clear.
Anchor feedback to the exact place on the real screen.
Preserve element labels, nearby text, and screenshots.
AI suggests priority, category, and possible owner.
Move next actions into Slack, Jira, and GitHub.
The widget captures the element label, nearest heading, and page title so vague comments become concrete targets.
Start with a URL. Use proxy mode with no code changes, or install one script tag for the most reliable live review flow.
Add the site URL you want to review. Staging, dev, and production all work.
New project →Use proxy mode for zero code changes, or install one <script> tag.
Share the `/live` URL. Reviewers can pin, comment, and sync in real time.
Proxy mode routes the target site through FEEDCHAT and injects the widget automatically. You do not need to touch the target site code.
Slack, chat, and verbal notes make it hard to know who meant what.
After deploys, comment locations drift and the original screen is forgotten.
Teams forget who decided what, and why, once the review is over.
The current product captures feedback on live screens. The next step is connecting the entire review session deeper into the product delivery system.
Threads, comments, and cursor events already sync in real time.
Replay page movement, pins, and decisions by session without relying on meeting notes.
Owner-gated sensitive settings are in place.
Separate workspace admin, project editor, and guest reviewer roles.
AI grounds vague feedback with element labels and nearby context.
Connect Figma and Storybook so a button maps to its real component.
FEEDCHAT combines proxy mode, element-level AI grounding, and Slack/Jira/GitHub delivery so feedback can move from a live screen to an actionable fix.
No. Proxy mode works with zero code changes. For authenticated screens or real production sessions, install the one-line widget embed.
Yes. Public projects allow anonymous reviewers with a link. Invite-only projects require Google sign-in and membership.
Use invite-only mode. Only members with the host's invite link can access the project after Google sign-in.
Start with a URL. Reviewers can join, pin, and comment immediately.
Create a projectWho said what, where, and why stays attached to the thread even after the next deploy.
<!-- index.html --> <script src="https://feedchat.app/feedchat-widget.js" defer> </script>
With a bot token, FEEDCHAT can look up the suggested owner and send a precise Slack ping.
Keep setup cost low: one script tag, or proxy mode with no site changes.
One thread maps to one ticket, preventing duplicates and preserving deep links.
Approve an actionable card and AI can draft the code change, commit, and PR body.
SSE keeps pins, comments, reactions, and status changes in sync.
Organize open, new, and decided items into a sprint-ready pipeline.
No. Classification results are stored in your FEEDCHAT database and are not used for external model training.
This POC is currently provided as an internal collaboration tool. External SaaS pricing can be defined later.