LoopX Community

中文

Use this page to choose the public channel that matches what you want to do. Chat is useful for exploration, but reproducible bugs, decisions, and durable evidence should return to GitHub.

Discuss And Connect

• Pinned GitHub Discussion: current technical directions, known limitations, and community discussion.
• Discord: informal onboarding, workflow comparison, and show-and-tell conversation.
• Lark developer group: scan the QR code to join directly.
• WeChat contact: add huangrt00 and mention LoopX in the friend request.

For channel ownership, support boundaries, and official publication sources, see Support.

Report, Request, Or Contribute

Choose the narrowest issue form for your public-safe report:

• Bug report for reproducible incorrect or unexpected behavior.
• Feature request for a concrete product or documentation improvement.
• First-run feedback for optional feedback after installing and running LoopX once.
• Show and Tell / Adoption for a public-safe workflow, result, integration, or adoption story.
• Usage story for a public report from a LoopX run lasting hours, days, or longer.
• Contributor task to claim, propose, or discuss repository-safe work.

Before opening a contribution, read Contributing and the public/private boundary. Never publish credentials, private project context, raw agent sessions, internal links, or local runtime state.

Share A Showcase

Start with the Showcase catalog, then use one of these prompts:

• Show and Tell / Adoption: describe what really ran, how LoopX was used, the observed outcome and public evidence, remaining limitations, and reproducible artifacts when available.
• Usage story: record the run duration, capabilities exercised, public-safe recovery story, and the outcome LoopX helped complete.

Showcase entries keep evidence boundaries explicit. A report may be useful before it is independently reproduced, but its status must say what remains user-reported, assisted, experimental, or unverified.

Explore The Ecosystem

• Ecosystem adoption and derivatives catalog: maintainer-curated public evidence about integrations, mechanism reuse, proposals, learning resources, and derivatives.
• ADOPTERS: voluntary, self-attested adoption entries from projects and users.

These are different evidence surfaces. A catalog entry records observable public evidence; it does not imply endorsement or production deployment.