How to Get Support for LoopX: Contact Channels, GitHub Issues, and Community Resources

LoopX provides multiple support channels ranging from informal WeChat chat to formal GitHub issues, all documented in key repository files.

If you're stuck with LoopX and need help, the project maintains several official pathways for assistance. Whether you prefer quick informal chat or structured bug tracking, the repository's README.md, COMMUNICATIONS.md, and documentation tree contain the exact contact points and procedures.

---

Quick Support Options at a Glance

LoopX organizes support into three tiers based on urgency and formality:

Method	Best For	Documentation Source
WeChat contact	Quick questions, community chat	README.md lines 521-524
Lark group	Ongoing collaboration, announcements	README.md adjacent to WeChat info
GitHub Issues	Bugs, feature requests, formal tickets	COMMUNICATIONS.md line 23

---

WeChat: Fast Informal Support

For immediate assistance or casual community discussion, LoopX maintains a public WeChat contact.

Finding the Contact Details

In README.md at lines 521-524, you'll find:

• WeChat ID: huangrt00
• QR code image: docs/assets/loopx-wechat-contact.png

The COMMUNICATIONS.md file at line 23 explicitly references this WeChat contact as an informal channel for project coordination.

Connecting via WeChat

# Locate the QR code asset for scanning or embedding

find . -name "loopx-wechat-contact.png" -path "*/docs/assets/*"

When sending a friend request, mention "LoopX" to help the maintainer identify your purpose.

---

Lark Group: Workspace Collaboration

LoopX also hosts a Lark group for more structured ongoing discussion. The Lark QR code and join link appear in README.md immediately following the WeChat information.

This channel suits:

• Longer technical discussions
• Coordination on upcoming features
• Real-time troubleshooting with multiple community members

---

GitHub Issues: Formal Support Tracking

For reproducible bugs, feature requests, or anything requiring permanent documentation, LoopX directs users to GitHub Issues.

Creating an Issue via Web Interface

Navigate to the repository's Issues tab and use the provided templates if available.

Creating an Issue via GitHub CLI

# Open a structured support request using the gh CLI

gh issue create \
  --title "LoopX: [Brief description]" \
  --body "## Environment

- LoopX version: 
- Runtime: 
- OS: 

## Problem Description

[Describe what you expected vs. what happened]

## Steps to Reproduce

1. 
2. 
3. 

## Additional Context

[Logs, screenshots, etc.]" \
  --label "support"

The COMMUNICATIONS.md notes that WeChat serves as a supplementary channel, but GitHub Issues remain the authoritative record for project decisions.

---

Private and Security-Sensitive Support

For matters requiring confidentiality—security vulnerabilities, private business inquiries, or sensitive data exposure—LoopX provides escalation paths.

Security Disclosures

Consult SECURITY.md for the official security contact channel. This file contains the designated email or private reporting mechanism for vulnerabilities.

General Private Contact

The GOVERNANCE.md file at line 75 contains policies regarding private maintainer contact. Rather than posting personal contact information publicly, the recommended approach is:

1. Open a brief public issue requesting private communication
2. A maintainer will provide a secure channel for the sensitive discussion

# Example: Requesting private contact for a sensitive matter

gh issue create \
  --title "Request: Private support channel needed" \
  --body "I have a sensitive matter to discuss that shouldn't be public. Please contact me privately." \
  --label "governance"

---

Self-Service Documentation

Before reaching out, LoopX encourages users to consult the documentation tree in docs/.

Key Documentation Locations

Path	Purpose
docs/guides/README.md	Central hub for how-to guides
docs/product/runtimes/codex-cli/README.md	Runtime-specific troubleshooting
docs/operations/	Deployment and operational guidance

Many guides include "Common Issues" or "Troubleshooting" sections with resolution steps.

Searching Documentation Programmatically

# Search for troubleshooting content across docs

grep -r "troubleshooting\|common issue\|support" docs/ --include="*.md"

# Find all README files in the product documentation

find docs/product -name "README.md" | head -10

---

Summary

• WeChat (huangrt00) and Lark provide fast, informal community support—check README.md lines 521-524 for QR codes and links
• GitHub Issues are the formal channel for bugs and feature requests, referenced in COMMUNICATIONS.md
• Security matters follow the private disclosure process in SECURITY.md
• Private escalation requires requesting a secure channel via public issue, per GOVERNANCE.md line 75
• Documentation-first approach: Search docs/guides/ and docs/product/ for self-service answers before contacting maintainers

---

Frequently Asked Questions

How do I find the LoopX WeChat contact?

Check [README.md](https://github.com/huangruiteng/loopx/blob/main/README.md) at lines 521-524. The WeChat ID huangrt00 and a scannable QR code are provided there. The COMMUNICATIONS.md file confirms this as the informal contact channel.

Can I open a GitHub issue for general questions?

Yes, though the project encourages using WeChat or Lark for quick questions. GitHub Issues are preferred for bugs, feature requests, or anything requiring permanent tracking. Use gh issue create or the web interface, and include environment details and reproduction steps.

What if I need to report a security vulnerability?

Do not use public channels. Follow the private disclosure process in [SECURITY.md](https://github.com/huangruiteng/loopx/blob/main/SECURITY.md). If you cannot locate the security email, open a generic issue requesting private contact and a maintainer will provide a secure channel.

Is there a community chat beyond WeChat and Lark?

Based on the repository structure, WeChat and Lark are the primary real-time channels documented in README.md and COMMUNICATIONS.md. No Slack, Discord, or Matrix references appear in the source analysis. Check the latest README.md for any additions since your version.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}