> For the complete documentation index, see [llms.txt](https://docs.lawnchair.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lawnchair.app/community/get-involved/community-channels.md).

# Community channels

If you need help using Lawnchair, want to discuss features with other users, or just stay up-to-date with the project, you can join our official community channels.

### Discussion and support

These platforms are the primary place for user-to-user support and general discussion.

Please be respectful and courteous to other members and follow the rules of each platform.

<a href="https://t.me/lccommunity" class="button secondary" data-icon="telegram">Telegram</a><a href="https://discord.gg/3x8qNWxgGZ" class="button secondary" data-icon="discord">Discord</a>

### Official announcements and community events

Follow these channels for official news, release announcements, contests, and community showcases.

These are generally not monitored for support questions; please use the discussion channels above for help.

<a href="https://mastodon.social/@lawnchairapp" class="button secondary" data-icon="mastodon">Mastodon</a><a href="https://x.com/lawnchairapp" class="button secondary" data-icon="x-twitter">X (formerly Twitter)</a><a href="https://reddit.com/r/lawnchairlauncher" class="button secondary" data-icon="reddit-alien">Reddit</a>

### Unmonitored channels

To save developer bandwidth and prevent ignored messages, please do not use the following channels for general support or bug reporting.

The core team does not monitor these spaces for technical assistance.

The channels here include:

* Our support email at `support@lawnchair.app`
* [GitHub discussions](https://github.com/LawnchairLauncher/lawnchair/discussions)
* [XDA thread](https://xdaforums.com/t/lawnchair-customizable-pixel-launcher.3627137/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lawnchair.app/community/get-involved/community-channels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.