How to Get Support for Meetily: Community Channels, PRO Help, and Debug Logging

You can get support for Meetily through community Discord servers, Reddit, GitHub Issues, and LinkedIn, while PRO subscribers receive priority email support, and technical issues require RUST_LOG=debug logs to diagnose.

Meetily is a privacy-first AI meeting assistant packaged as a single Tauri desktop application, with the entire product—the Next.js frontend and Rust backend—maintained in the Zackriya-Solutions/meetily repository. Because all layers of the application live in one codebase, knowing how to get support for Meetily depends on choosing the right channel and providing diagnostics tied to the correct subsystem.

Community Support Channels

The project maintains several public channels, all linked from the root README.md.

Discord Servers

Join the main Meetily community server at https://discord.gg/crRymMQBFH for real-time chat with developers and users. There is also a dedicated Privacy-First AI channel at https://discord.com/invite/vCFJvN4BwJ for broader discussions about privacy-focused tooling.

Reddit and LinkedIn

Browse community-driven Q&A and announcements on Reddit at https://www.reddit.com/r/meetily/, or follow professional updates and release notes on LinkedIn at https://www.linkedin.com/company/106363062/.

GitHub Issues

For structured bug reports or feature requests, open a new issue using the template at https://github.com/Zackriya-Solutions/meetily/issues/new/choose. Accelerate diagnosis by including your OS version, Meetily version (./clean_run.sh --version), and a debug log excerpt. Mention relevant source paths—such as frontend/src-tauri/src/audio/pipeline.rs for audio dropouts or frontend/src-tauri/src/whisper_engine/whisper_engine.rs for transcription errors—so maintainers can route the ticket quickly.

Website and Product Updates

Subscribe to official release notes and security advisories at https://www.zackriya.com/meetily-subscribe/.

PRO and Enterprise Support

If you are a Meetily PRO subscriber, you receive Priority Support (referenced at line 236 of the README). PRO users can contact the team directly through the email address provided in the purchase confirmation or through the private support portal in their account dashboard. This channel is intended for critical production issues, advanced configuration assistance such as custom AI endpoints, and early-access features like speaker diarization.

Collecting Diagnostic Logs

Many issues are resolved by reviewing runtime logs. Meetily uses the log crate, and debug output—including perf_debug! macro statements—can be toggled via the RUST_LOG environment variable.

# macOS / Linux

RUST_LOG=debug ./clean_run.sh

# Windows PowerShell

$env:RUST_LOG="debug"; .\clean_run_windows.bat

The output appears in the terminal where the app was launched. Copy this output into your GitHub Issue or Discord thread to give maintainers timestamped module traces.

Mapping Issues to the Repository Architecture

Understanding where a problem originates helps you tag it correctly. Meetily consists of three logical layers:

1. Frontend (Next.js + React) — All UI code lives under frontend/. Tag frontend UI bugs with the UI label.

2. Rust Backend — Core logic, audio capture, and LLM orchestration reside in frontend/src-tauri/src/.

   • frontend/src-tauri/src/lib.rs — Tauri command registration and event handling.
   • frontend/src-tauri/src/audio/pipeline.rs — Device discovery, capture, mixing, and VAD processing.
   • frontend/src-tauri/src/whisper_engine/whisper_engine.rs — Model loading and transcription orchestration.

3. Architecture Docs — The high-level system diagram is documented in docs/architecture.md. GPU-acceleration setup details are in docs/GPU_ACCELERATION.md.

Automating Bug Reports with the GitHub CLI

If you have the GitHub CLI installed, you can create an issue with logs pre-attached:

gh issue create \
  --title "Audio dropout on Windows 11 (v0.4.0)" \
  --body "$(cat <<EOF
**OS:** Windows 11  
**Meetily version:** 0.4.0  
**Steps to reproduce:**  
1. Start a meeting recording.  
2. After ~30 seconds the system audio stops.  

**Log excerpt:**  
$(RUST_LOG=debug ./clean_run.sh 2>&1 | head -n 20)
EOF
)"

This command attaches the first 20 lines of the debug log, helping maintainers reproduce the issue faster.

Summary

• Start with community channels—Discord, Reddit, GitHub Issues, or LinkedIn—for general help.
• Include your OS, Meetily version, and a RUST_LOG=debug log excerpt in every technical request.
• Reference relevant backend modules such as audio/pipeline.rs or whisper_engine/whisper_engine.rs to route the issue correctly.
• PRO subscribers should use the dedicated priority-support email or portal for critical or advanced issues.
• Consult docs/architecture.md and docs/GPU_ACCELERATION.md for system-level context before filing complex bugs.

Frequently Asked Questions

What is the fastest way to get help with Meetily?

For real-time troubleshooting, join the public Discord server at https://discord.gg/crRymMQBFH. If you have a reproducible bug, opening a GitHub Issue with your OS version and a debug log is the most direct path to a code-level fix because it reaches the maintainers of Zackriya-Solutions/meetily directly.

How do I collect debug logs for a Meetily support request?

Set the RUST_LOG environment variable to debug before launching the app. On macOS or Linux, run RUST_LOG=debug ./clean_run.sh; on Windows PowerShell, run $env:RUST_LOG="debug"; .\clean_run_windows.bat. Copy the terminal output—which includes perf_debug! traces from the Rust backend—into your support thread.

Where should I report a frontend UI bug versus an audio transcription issue?

Report UI bugs under the frontend/ directory or tag them with the UI label. For audio capture problems, reference frontend/src-tauri/src/audio/pipeline.rs. For transcription failures, reference frontend/src-tauri/src/whisper_engine/whisper_engine.rs. Checking docs/architecture.md first can help you identify the correct subsystem.

What support do Meetily PRO users receive?

According to the README at line 236, PRO subscribers receive Priority Support through a dedicated email or private portal. This channel is reserved for critical production issues, advanced configurations such as custom AI endpoints, and early-access features like speaker diarization.

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