# Community

**Faya Labs** is the community around Fayz: where you ask questions, report problems and follow what's being built. Fayz is the product; Faya Labs is the team that maintains it and the people building with it.

## Where to get help

- **Support / questions.** Start with the docs — [Troubleshooting](/en/docs/resources/troubleshooting) and the [FAQ](/en/docs/resources/faq) cover most early stumbles. The community support channel will be announced here soon.
- **Reporting bugs.** Found something broken, or behavior the docs don't explain? The official channel for filing issues (the bug tracker) will be announced on this page as soon as it's live. In the meantime, start putting the report together: what you expected, what happened and how to reproduce it (command, package version, `fayz doctor` output). The more concrete it is, the faster you'll hear back.
- **Ideas and feedback.** Missing a capability, a plugin, a piece of documentation? Send it our way — the SDK's priority list is shaped by the people actually building.

{% callout type="tip" %}
When reporting a problem, include the output of `fayz doctor` and the package version (`npm ls @fayz-ai/cli`). That cuts half the back-and-forth.
{% /callout %}

## How feedback becomes SDK

Fayz is built from the inside out: Faya Labs uses its own SDK to run real apps. Friction that shows up in a client app becomes a backlog item, and that item becomes an improvement in the core, in a plugin or in the docs. When something meaningful lands in a release, it shows up in the [Changelog](/en/docs/resources/changelog).

In other words: what you report doesn't vanish into a suggestion box — it competes in the same queue as the problems the team hits itself.