> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genieforge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Signals and in-app feedback

> Signals capture real usage friction so you know what to build next, including app vs platform tags.

# Signals and in-app feedback

**Signals** capture what real usage reveals: bugs, friction, missing features, confusion, or data problems. They help you decide what to build next. Look for Signals and Feedback under the selected project.

The AI inside your app may also record a signal when it has to decline a missing capability or when something is clearly broken. On the Signals **Roadmap** tab, related reports are grouped and ranked. Each group is tagged as **app** (something you can fix in this app) or **platform** (a GenieForge capability gap).

When a signal looks platform-related, GenieForge also files **Platform Feedback** automatically. Both entries stay visible: you can still act on the signal in Signals, and see the same topic under Platform Feedback. Closing one does not close the other, so a mistaken platform tag still surfaces for you to dismiss or ignore. Account or billing issues still go to [support@genieforge.ai](mailto:support@genieforge.ai).