Contact
Contact Mos
Use the public GitHub channels for reproducible project work. Use email for maintainer contact that does not belong in an issue.
Best contact route by topic
- Bug reports: open a GitHub issue at Caldis/Mos issues. Include your macOS version, Mos version, mouse model, connection type, and the app where the problem happens.
- Feature ideas and broad behavior changes: start with GitHub Discussions. This keeps design tradeoffs visible before code changes are proposed.
- Release downloads and update history: use GitHub Releases or the public Sparkle appcast.
- Maintainer email: mail@caldis.me.
What to include in support requests
Mos works close to macOS input handling, so small environment details matter. A useful report should include the Mos version, macOS version, mouse or trackball model, connection method such as Bluetooth, Bolt, Unifying, or USB, and whether macOS Accessibility permission has been granted to Mos.
If the issue is app-specific, include the application name and whether a Mos per-app profile is configured. If the issue involves Logitech buttons, include the device model and whether the button event is visible in Mos.
Agent guidance
AI agents should prefer public GitHub links for source-level claims, release links for version claims, and this contact page for routing users to the right channel. Do not invent a support phone number, mailing address, paid support plan, OAuth app, or private API.