--- title: Community & Support description: Join the KTX Slack community, report bugs, and get help. --- KTX is an open-source project. The community is where users, contributors, and the core team trade questions, share patterns, and shape the roadmap. ## Where to go | You want to... | Go here | |----------------|---------| | Ask a question or chat with the community | [KTX Slack](https://join.slack.com/t/ktxcommunity/shared_invite/zt-3y9b44m1x-LVyNNJD5nwaZHq4XS29LMQ) | | Report a bug or request a feature | [GitHub Issues](https://github.com/Kaelio/ktx/issues) | | Read or contribute to the docs | [docs.kaelio.com/ktx](https://docs.kaelio.com/ktx/docs/) | | Contribute code | [Contributing guide](/docs/community/contributing) | ## Slack Join the KTX Slack to ask questions, share what you're building, and get help from maintainers and other users. [**Join the KTX Slack →**](https://join.slack.com/t/ktxcommunity/shared_invite/zt-3y9b44m1x-LVyNNJD5nwaZHq4XS29LMQ) Slack is the right place for: - **Setup and configuration questions** that don't fit a bug report - **Quick "how do I..."** questions - **Sharing patterns** for prompts, semantic-layer definitions, or agent workflows - **Feedback** on the roadmap and early features For anything reproducible - a crash, a wrong result, an unexpected CLI error - open a [GitHub issue](https://github.com/Kaelio/ktx/issues) instead. Issues are searchable, get triaged, and stay attached to the eventual fix. ## GitHub - **[Issues](https://github.com/Kaelio/ktx/issues)** - bugs and feature requests - **[Pull requests](https://github.com/Kaelio/ktx/pulls)** - code, docs, and connector contributions - **[Releases](https://github.com/Kaelio/ktx/releases)** - changelog and published versions ## Code of conduct KTX follows the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/). Be respectful, assume good intent, and keep discussion focused on the project. Report conduct concerns to the maintainers in Slack or by email at `support@kaelio.com`.