01
OfficialDiscord
The official channel: talk, report, releases.
Engineers on rotation respond during working hours; paste logs for deployment issues, screenshots for usage ones.
Community
Talk to real users and real developers
Stuck on a deploy, proud of a workflow, chasing releases — Discord, GitHub, docs and email, each tuned to how fast you need an answer.
Four doors, four jobs
Discord is fastest, Issues last longest, docs go deepest, email is most formal — pick by the job.
Ordered by response speed: Discord fastest, issues most durable, email most formal.
Four doors, clear jobs: day-to-day in Discord, durable questions in Issues, systematic learning in the docs, formal partnerships over email — full coverage, no application needed to enter.
02
GitHub
The source repository and issue feedback.
Issues in English or Chinese both work; the raw error text and reproduction steps are the two most useful things.
03
Docs
Deployment and usage documentation.
04
Contact
Reach us by email.
Channels are entrances, not walls — from any of them you can reach the source, the docs, and the people who respond.
Logs, screenshots, scenarios — all at once.
Announcements live only in the four channels.
Ways to contribute
From a one-line report to a source commit, four roads in.
Every road starts with one small act:
Start with the docs: smooth the sentence that tripped you. Fastest merges, most treasured.
01
Report issues
Open a GitHub issue: your deployment shape, reproduction steps, expected result — and the raw error text.
02
Improve the docs
The docs are repository content; spot a gap or something stale, file it or propose the change.
03
Compare notes
Ask and share in the Discord deployment and usage channels; engineers on rotation respond.
04
Grow the ecosystem
Bring your MCP servers or custom catalog endpoints into the market, published against the registry API.
All contribution starts from the repository: change proposals, docs corrections, and issues share one entry.
Land a change; your name is in the log.
Contributing does not require being an expert first: one reproducible issue or one docs correction moves the project forward.
The roadmap, updated in public
Releases are announced on the blog and Discord; the single-server boundary, BYOK channels and explicit-failure discipline are long-term commitments with no silent changes.
The roadmap updates publicly and rolls quarterly: the single-server boundary, BYOK channels and explicit-failure discipline are long-term commitments, announced ahead in the official channels.
All three lines deepen inside the self-host boundary — no hosted plane, no tracking.
- The target model of enrolled machines beside cloud computers — more platform capabilities land through the docs
- The three-family market catalog keeps growing; the web-install payload surface extends as needed
- Voice, triggers, and five-dimension memory — all evolving inside the self-host boundary
The roadmap is not a wish list — every listed item anchors to a fact you can find in the docs or the repository.
Docs fix every release.
Support, on two tracks
The test for free support: if the answer is in the docs, it should never need a ticket.
Every support level has an exit: docs, community, inquiry. Questions never vanish.
Self-serve support
Docs and community first: 54 pages cover deployment, usage, and operations; Discord and GitHub issues are real response channels.
Open the docs →Enterprise support
For on-site delivery or dedicated support, use enterprise inquiry — forward-deployed service runs on a quote basis, detailed on the solutions page.
See solutions →Docs first, community next, enterprise when needed — three layers make sure every question finds an exit instead of disappearing into a form.
Post in general; we will point you right.
Deployment questions, usage notes, and release news — see you in the community.
If MagicFrog saved your team time, write it down — one real note beats ten tutorials.