# OpenWork Community Support: Channels, Templates, and Triage Workflow > Discover OpenWork community support options. Utilize GitHub Issues with templates, a clear triage workflow, and debug logging for effective problem-solving and feature requests. - Repository: [Different AI/openwork](https://github.com/different-ai/openwork) - Tags: how-to-guide - Published: 2026-08-07 --- **OpenWork provides a structured community support system centered on GitHub Issues with dedicated templates for bugs, features, and questions, complemented by a triage workflow defined in [`TRIAGE.md`](https://github.com/different-ai/openwork/blob/main/TRIAGE.md) and debug logging capabilities within the application.** The different-ai/openwork repository maintains a comprehensive support architecture that routes user inquiries through standardized channels. Whether you are reporting a crash, requesting a feature, or troubleshooting configuration, the project provides specific entry points and documentation to ensure maintainers can respond efficiently. ## GitHub Issues as the Primary Support Channel The main avenue for **OpenWork community support** is GitHub Issues. The repository uses structured templates located in `.github/ISSUE_TEMPLATE/` to categorize requests and ensure maintainers receive reproducible information. ### Bug Reports For crashes or unexpected behavior, use the **Bug Report template** at [`.github/ISSUE_TEMPLATE/bug_report.md`](https://github.com/different-ai/openwork/blob/main/.github/ISSUE_TEMPLATE/bug_report.md). This template enforces required fields such as environment details, reproduction steps, and expected versus actual behavior. Issues created through this template automatically receive the `bug` label and are prioritized according to the rubric in [`TRIAGE.md`](https://github.com/different-ai/openwork/blob/main/TRIAGE.md). Create a bug report using the GitHub CLI: ```bash gh issue create \ --title "Crash when opening Settings on macOS 14" \ --template "bug_report.md" \ --label "bug" ``` ### Feature Requests To propose enhancements, use the **Feature Request template** at [`.github/ISSUE_TEMPLATE/feature_request.md`](https://github.com/different-ai/openwork/blob/main/.github/ISSUE_TEMPLATE/feature_request.md). This template captures motivation, use-case, and potential impact. Submissions receive the `feature` label and are evaluated by maintainers for roadmap inclusion. ### General Questions For usage inquiries and configuration help, open a standard GitHub Issue and apply the `question` label. The [`SUPPORT.md`](https://github.com/different-ai/openwork/blob/main/SUPPORT.md) file serves as the central guide directing users to this channel for general help. Create a question issue via CLI: ```bash gh issue create \ --title "How do I configure a custom MCP endpoint?" \ --body "I'm trying to point the OpenWork MCP to a self-hosted server..." \ --label "question" ``` ## In-Application Debug Support For **desktop, worker, or session-specific bugs**, OpenWork provides built-in diagnostic tools. Before opening an issue, export debug logs directly from the application to provide maintainers with exact state information. 1. Open OpenWork → **Settings** → **Debug**. 2. Click **Export Runtime Report** and **Export Log**. 3. Attach the generated files ([`runtime-report.json`](https://github.com/different-ai/openwork/blob/main/runtime-report.json) and [`dev-log.txt`](https://github.com/different-ai/openwork/blob/main/dev-log.txt)) to your GitHub issue. These logs give maintainers the precise runtime state needed for reproducibility, reducing back-and-forth clarification requests. ## Security Reporting via SECURITY.md Vulnerabilities must not be disclosed publicly. The repository's [`SECURITY.md`](https://github.com/different-ai/openwork/blob/main/SECURITY.md) defines a private reporting process using a security contact link. Security issues are handled off-public-record with coordinated disclosure, separate from the standard public issue workflow. ## The Triage Workflow All incoming issues are processed according to [`TRIAGE.md`](https://github.com/different-ai/openwork/blob/main/TRIAGE.md), which defines the labeling and routing logic. The triage system assigns labels such as `bug`, `question`, `feature`, and `security`, then routes issues to appropriate maintainers based on priority and component. This structured approach ensures queries receive prompt attention while keeping the project maintainable. ## Code of Conduct and Contributing Community interactions are governed by [`CODE_OF_CONDUCT.md`](https://github.com/different-ai/openwork/blob/main/CODE_OF_CONDUCT.md), which establishes standards for respectful engagement. Contributors should also consult [`CONTRIBUTING.md`](https://github.com/different-ai/openwork/blob/main/CONTRIBUTING.md) for guidelines on pull requests and development workflows, ensuring that support requests and contributions align with project standards. ## Summary - **Primary support channel**: GitHub Issues with structured templates in `.github/ISSUE_TEMPLATE/`. - **Bug reports**: Use [`.github/ISSUE_TEMPLATE/bug_report.md`](https://github.com/different-ai/openwork/blob/main/.github/ISSUE_TEMPLATE/bug_report.md) for crashes and errors. - **Feature requests**: Use [`.github/ISSUE_TEMPLATE/feature_request.md`](https://github.com/different-ai/openwork/blob/main/.github/ISSUE_TEMPLATE/feature_request.md) for enhancements. - **Debug data**: Export runtime reports and logs from Settings → Debug for desktop issues. - **Security issues**: Report privately via [`SECURITY.md`](https://github.com/different-ai/openwork/blob/main/SECURITY.md), never through public issues. - **Triage process**: [`TRIAGE.md`](https://github.com/different-ai/openwork/blob/main/TRIAGE.md) governs label assignment (`bug`, `feature`, `question`, `security`) and maintainer routing. ## Frequently Asked Questions ### How do I report a bug in OpenWork? Use the bug report template located at [`.github/ISSUE_TEMPLATE/bug_report.md`](https://github.com/different-ai/openwork/blob/main/.github/ISSUE_TEMPLATE/bug_report.md) when creating a GitHub Issue. Include your environment details, reproduction steps, and attach debug logs from Settings → Debug if reporting a desktop app issue. ### Where can I ask general usage questions about OpenWork? Open a GitHub Issue and label it as `question`. The [`SUPPORT.md`](https://github.com/different-ai/openwork/blob/main/SUPPORT.md) file provides guidance on what information to include. This channel is intended for configuration help and usage inquiries that are not bug reports or feature requests. ### How do I report a security vulnerability? Follow the process outlined in [`SECURITY.md`](https://github.com/different-ai/openwork/blob/main/SECURITY.md) and submit your report through the private security contact link. Do not open a public issue for security matters, as the project uses coordinated disclosure to protect users. ### What information should I include when reporting a desktop app issue? Include the **runtime debug report** and **developer log export** generated from OpenWork's Settings → Debug menu. Attach both [`runtime-report.json`](https://github.com/different-ai/openwork/blob/main/runtime-report.json) and [`dev-log.txt`](https://github.com/different-ai/openwork/blob/main/dev-log.txt) to your GitHub issue to provide maintainers with the exact application state needed for diagnosis.