Talk to other people building with Pearl.
Discord for fast questions, GitHub Discussions for longer threads, and direct channels to the team when those don't fit.
Pick the channel that fits the question.
Discord
Real-time chat with other Pearl users and the team. Good for quick questions,
workflow ideas, and watching what other people are trying.
Request an invite →
GitHub Discussions
Longer-form Q&A, design discussions, and feature proposals. Searchable history,
so the answer outlives the question.
Open PearlGit →
Bug reports & feature requests
File at /feedback. Goes directly to the engineering team's queue — not a separate ticket system. Include the Pearl version and OS for fastest triage.
Security disclosures
Private. Email security@pearlfibers.com. Don't post in public channels until we've shipped the fix.
How to help.
What we accept from the community
- Bug reports with reproductions. Half the work is identifying the bug; if you've done that, file it and we'll fix it.
- Feature requests grounded in a real workflow. "I wish Pearl did X when I'm doing Y" beats "feature parity with [editor]."
- Documentation improvements. If a docs page is unclear, file feedback with the specific paragraph and what threw you off.
- Tutorial suggestions. If you'd write the same tutorial we should publish, tell us — we usually do.
What we don't accept (yet)
- External PRs to Pearl IDE. The core editor isn't open to community PRs right now — we're still moving fast and external contributions add coordination cost we can't absorb.
- Theme submissions. Use the VS Code extension you already love — the extension host runs it unchanged. No need for a Pearl-specific theme system.
- Plugin marketplace listings. Same story — the VS Code extension marketplace works inside Pearl. We don't run our own.
Code of conduct
Be respectful in all channels. We moderate hard against personal attacks, harassment, and bad-faith arguments. Sharp disagreement about technical decisions is welcome — disrespecting the person behind a decision is not.
Discord and GitHub Discussions are public; behave accordingly. Repeat violations are logged and lead to channel bans without warning.