Heardex for Claude
Ask Claude what users think, then let it find the fix.
Connect Heardex to Claude once and Claude can read your product's feedback and issues. Ask questions in plain words, or send an issue to Claude to look for the cause in your code.
Heardex as it is today, in our own workspace that tracks Starlink.
Ask in plain words
“What are the top complaints this week?” “Summarize the bug reports and where they come from.” “Which platforms talk about us the most?” Claude answers from your real data, with links to the posts.
Investigate in your code
“Investigate with Claude” on an issue gives Claude the issue, every report and its priority. In Claude Code it can then search your repository for the cause and suggest a fix. It asks before changing anything.
Read-only and revocable
Claude sees only the workspace you approve and can't change anything in Heardex. You can see every connected Claude account and revoke access at once.
Works where you use Claude
Claude on the web, the desktop app and Claude Code, on your own Claude plan. It uses the open Model Context Protocol (MCP), so other MCP clients that support remote servers can connect too.
How it works
- In Heardex, open Settings → Claude and click Connect.
- Approve access for your workspace.
- Ask Claude about your feedback, or click “Investigate with Claude” on an issue.
PDF export crashes on long notes
39 reports · 6 days · Reddit, App Store, GitHub
“Crashes every time my note is longer than 40 pages.”
“Lost an hour of work when export froze.”
“Falls over on big docs.”
- ›Investigating “PDF export crashes on long notes” (39 reports)
- ·Read 39 reports through the Heardex connector
- ·Searched src/export for the PDF writer
- ·src/export/pdf.ts:212 builds every page in memory before writing
- ·Crash reproduces above ~38 pages (heap limit on iOS)
- ✓Proposed fix: stream pages to disk in batches of 10
On which plans
- Included on every plan, Free included.
Good to know
- Claude usage counts toward your own Claude plan, not Heardex's.