Contact.
Which channel fits which question — and what happens after you send it.
Bugs and feature requests
Open an issue on GitHub. Include the OMA version, the provider you ran against, and the smallest snippet that reproduces the behaviour — that is usually the difference between a fix and a thread of clarifying questions.
Triage happens in the open, and the queue is public, so you can see what sits ahead of your report instead of guessing. There is no support SLA on the open-source project.
Questions about using it
Ask in GitHub Discussions rather than by email — answers there stay searchable for the next person with the same question.
Most of it is already written down: Introduction for the model, Quick start for the first run, CLI reference for the oma binary, and Examples for working recipes.
Security reports
If you think you have found a vulnerability in the runtime, email [email protected] with security in the subject line instead of opening a public issue, so a fix can ship before the details are public.
Commercial delivery and support
Paid implementation, integration, and support are handled by 元定义科技 (YuanASI), a separate commercial entity — see yuanasi.com, email [email protected], or message WhatsApp. The framework stays MIT-licensed and free to use either way.
Everything else
Press, talks, and anything that fits none of the above: [email protected]. There is no ticketing portal — GitHub, that address, and WhatsApp for commercial enquiries are the whole surface.
Last updated: