Distribution and OAuth registration#

This page explains the distribution model and Google registration policy, not a developer qualification workflow. Installation uses matching Linux x86_64/arm64 binaries or complete bundles; setup is the canonical account/permission guide. No compiler or test harness is needed for a bundle.

Project source is MIT-licensed, with third-party notices included in releases. Omagma does not ship a shared Google OAuth registration or a service receiving Gmail data. Each user creates a Google OAuth registration and authorizes accounts locally. Read-only bar access and broader terminal access use separate registration client IDs in the same Google project.

A shared public registration would need maintained identity/support/privacy information and Google's applicable verification. Google classifies gmail.readonly and gmail.modify as restricted, and gmail.send as sensitive. Gmail scope classifications. Contacts creation uses the sensitive contacts permission; narrower read access uses contacts.readonly, and Google displays requested scope classifications in the project's Data access page. People scopes, sensitive-scope guidance.

Publishing source or selecting Production does not establish verification. Personal-use and internal-organization exceptions have specific limits; internal registrations serve only their owning Workspace/Cloud Identity organization. Google's exceptions.

Refresh tokens issued by External Testing registrations expire after seven days for Omagma's requested mail scopes, including both bar and terminal grants. Production removes that Testing-specific expiry; other expiration/revocation rules remain. This is registration policy, not a requirement to enroll in Omagma's developer tests. Google's token rules.

Published v0.2.3 includes the Omarchy plugin and experimental terminal/agent clients. Complete bundles contain the static backend and notices; terminal-only installation can use the matching raw binary with LICENSES.txt. Later local source features are labeled in the feature catalogue, with no change to published assets. The bar uses read-only consent; broader terminal access uses a separate client/grant. Keep private credentials/configuration, raw receipts and real-mail captures out of releases. Privacy, release maintenance.