Every flaw, in plain sight.
Users report it. Your Claude fixes it. StareGlare catches every bug report and every error your apps throw, puts them in one calm inbox, and lets Claude fix the code and tell the people who asked.
- Report pages & widget
- Mac & Godot
- Error capture
- Duplicates
- Two-way email
- MCP for Claude
Every app here sends its bugs straight to it.
Mac apps, browser games and web tools that send their bug reports, ideas and questions through StareGlare.
Five steps. One workspace.
From the first report to the reply that says it’s fixed, for every app and game you make. Claude can work in each step over MCP.
- 01 Listen Everything users run into
- Report pages & widget
- Mac app & Godot addon
- 17 languages
- A page to follow it
- 02 Catch The errors nobody reports
- Errors & crashes
- Grouped per version
- One email an hour
- Reopens if it returns
- 03 Triage One calm inbox
- Priorities & labels
- Duplicates merged
- Saved replies
- Keyboard & ⌘K
- 04 Fix Claude does the fixing
- MCP server & skill
- Knows each repo
- Notes with the commit
- GitHub & Linear issues
- 05 Notify People hear back
- Two-way email
- One reply for duplicates
- Slack & Discord
- Webhooks
Hear about every bug, even the unreported ones.
A report page people will bother to use, a widget for the web, a menu item for Mac apps and a key for Godot games. Errors and crashes come in on their own. All of it lands in one calm inbox.
Report a bug17 languages
The widget, the report page, the tracking page and the confirmation email follow the visitor’s language, from English to Macedonian and Japanese.
Duplicates, merged
Reports of the same problem fold into one. Reply once and everyone who reported it hears back.
Errors before anyone writes
Errors and crashes captured on their own, grouped and counted, with versions affected and one email an hour, not one per error. Error tracking guide
Logs you can read
Tail of every log inline, errors highlighted, filter as you type. Console errors from the web and crash logs from Mac apps and Godot games.
Looks like your app
Per-app colour, icon, chat-style or classic popup, intro and thank-you text. A live configurator shows it before you paste it.
A page they come back to
Every reporter gets a private link to follow their report and add details, without signing up.
Where your team already is
New reports and replies to Slack, Discord or a webhook. Turn a report into a GitHub or Linear issue per app.
Private by default
Per-workspace access rules, private file storage, rate limits, 90-day retention, and reporters untick anything before it’s sent.
“Fix these reports and tell the users.”
That’s the whole workflow. StareGlare ships an MCP server and a Claude skill, so Claude can read each report with its logs, open the right repository, fix and test the code, and leave you a note with the commit. Then it writes to each reporter in plain words.
- Knows where every app’s code lives
- Never emails anyone unless you say “notify”
- Internal notes with root cause and commit
- Per-workspace tokens you can revoke anytime
claude mcp add --transport http stareglare \ https://stareglare.com/api/mcp \ --header "Authorization: Bearer snag_sk_…"Then just ask
Fast enough to live in.
One dashboard for every app, built to be used with the keyboard and kept quiet until something needs you.
⌘K for everything
Jump to any app, report, page or action. ⌘\ folds the sidebar to icons.
Keyboard-first inbox
j / k to move, x to select, e to close, / to search. Peek a report without leaving the list.
Focus mode
Hide everything but the report in front of you. “Since you were last here” sums up what changed.
Real two-way email
Reply from StareGlare, reporters answer from their inbox. Internal notes stay internal.
Saved replies
Type / in a reply for canned answers. “Fixed in the next update” shouldn’t need typing twice.
Team and activity
Invite people to the workspace. Owners keep the connections, and an activity log shows who did what.
Near-live
New reports and closes show up without a reload. The tab title tells you when something’s unread.
Light and dark
A calm dashboard either way, with each app tinted in its own colour.
One line for the web. Five for Mac. One call in Godot.
<script src="https://stareglare.com/widget.js" data-app="gridburg" data-color="#30a46c" async></script>
A floating “Report a bug” button in the page’s language. Captures the page, browser and recent console errors. Website guide
let snag = SnagReporter(appSlug: "hourslip", publicKey: "snag_pk_…", baseURL: URL(string: "https://stareglare.com")!) NSApp.helpMenu?.addItem(snag.menuItem(logFiles: { [logURL] }))
Adds “Report an Issue…” with the StareGlare icon to your Help menu. Uploads the tail of your logs, system info and a window snapshot, then opens the report page. After a crash, the crash log comes too. macOS guide
# Project Settings: stareglare/app_slug and stareglare/public_key # F9 opens a report, or call it from your pause menu: StareGlare.report()
Captures a screenshot, the end of the log and system info, then opens the report page. Notices when the last session ended unexpectedly. Godot guide · Download the addon
How I keep track of bugs and suggestions for six apps.
Why I built StareGlare, how the reports get in, and the HourSlip report that went from "this annoys me" to a release in an hour and a half.
Read the postQuestions about StareGlare.
What is StareGlare?
StareGlare collects bug reports, feedback and questions from your apps and games, and the errors they capture on their own. Each app gets a branded report page, a one-line web widget, a Swift helper for Mac apps or a Godot addon for games. Everything lands in one inbox, and your Claude fixes the bugs and replies to the people who reported them.
How does Claude fix the bugs?
StareGlare includes an MCP server and a Claude skill. Claude lists your open reports, reads each one with its logs, opens the repository for that app, fixes and tests the code, and leaves an internal note with the root cause and commit. It only emails reporters when you ask it to.
Does StareGlare email anyone on its own?
No. Claude drafts replies and waits for “notify”. Reporters get a confirmation that their report arrived, and you get notifications, but every reply is sent by you or by Claude when you ask.
Do I need Claude to use StareGlare?
No. The report pages, the inbox, error capture, labels, saved replies and two-way email all work on their own. Claude is there when you want it to do the fixing and the replying for you.
What gets collected?
What the reporter types and attaches, plus app version, OS and device info. From Mac apps and Godot games, logs and a screenshot come along, and after a crash the crash log too. The reporter sees what is attached and can untick it before sending.
Which platforms?
Anything with a browser link. A one-line widget for web games and sites, a tiny Swift package for Mac apps, and an addon for Godot 4 games on Windows, macOS and Linux. Report pages speak 17 languages.
How is StareGlare different from Sentry or Instabug?
Sentry and Instabug focus on crash reporting, monitoring and SDK-level telemetry. StareGlare collects what your users choose to tell you, keeps it in one small inbox, and lets you or Claude reply. It can also capture errors and crashes on its own, grouped and counted, but it is not a monitoring suite: no performance tracing, source maps or session replay. It works well alongside one. See the full comparisons.
How do I get started?
Email hello@stareglare.com with a line about your apps or games, and we'll set up a workspace for you.
Look closer. Nothing hides.
Hear it, fix it, tell them. Tell us about your apps or games, and we’ll set up a workspace for you.