AgentsEye support
A useful report.
No prompts or credentials.
Start with the checks below. If the problem remains, send a short description and a diagnostics export so it can be investigated without sharing prompts, responses, or credentials.
AgentsEye crashes after enabling Prompts
AgentsEye 0.17.15 could repeatedly quit on launch after prompt history was enabled. Download the current version from the download page, quit AgentsEye completely, and replace the copy in Applications. Your provider settings and local usage history remain on this Mac.
iPhone companion
For beta access, QR pairing, notifications, widgets, and disconnecting, see the iPhone companion setup guide. If you need an invitation, contact support below; public beta installation is not yet available.
Try these first
- Open AgentsEye → Settings → Updates and install any available update.
- Use Refresh, then wait for the provider reading to finish.
- Open Providers and check the message shown for the affected provider. If it asks you to reconnect or approve access, follow that provider-specific action.
- Confirm the provider’s own app or command-line tool is signed in and can show current usage.
Create a privacy-safe diagnostic report
In AgentsEye, open Settings → Support and choose Export…. Save the JSON file somewhere you can review before attaching it.
The export contains app and macOS versions, privacy-safe settings, provider health, freshness, and connection errors. It is allow-listed and excludes prompts, responses, credentials, webhook URLs, token counts, workspace names, session labels, identifiers, and raw source paths. AgentsEye never uploads the report automatically.
Contact support
Contact @andrewdex on X and say that you need AgentsEye support. Include:
- The affected provider and the message AgentsEye shows.
- What you expected and what happened instead.
- When the reading last worked, including your time zone.
- Whether you have a diagnostics JSON ready to share privately.
Do not post the diagnostics report or sensitive details publicly. Share the report only after support confirms a private destination. For a suspected security issue, ask for a private security contact without describing the issue publicly. Never attach credentials, tokens, webhooks, or other secrets.
Keep private material out of support messages
Do not send prompts, responses, API keys, authentication tokens, Discord webhook URLs, billing details, or private source code. If a secret was exposed, revoke or rotate it with the provider before contacting support. Read the Privacy Policy for the complete data-handling explanation.