Omagma documentation#
Start with installation and account setup, then choose the bar, terminal or agent guide. The bar is read-only; the experimental TUI and CLI can use an account grant for sending and mailbox/contact changes. The bar runs on Linux Omarchy; the TUI and CLI run on Linux and macOS.
These guides describe Omagma’s current features. Dated evidence reports retain the versions and revisions that were measured.
Get started#
- Install on Linux or macOS: choose Homebrew on Mac or a matching verified bundle, then install the requested interface.
- Connect accounts and permissions: Chrome profiles, read-only bar access, full TUI/CLI access, Google Console steps and per-account consent.
- Ask an agent to install it: a ready-to-use request and the included setup skill.
Everyday use#
The feature catalogue lists the main capabilities first, then smaller reading, composition, organization and agent workflow details.
| Guide | What you will find |
|---|---|
| macOS installation | Homebrew, native release bundles, Keychain and Chrome defaults |
| Bar dropdown | Account switching, mail links and refresh status |
| Terminal mail | Reading, search, compose/reply, contacts, attachments, labels and keyboard/mouse controls |
| Agent CLI | Structured commands, account selection, cache/server search, drafts, receipts and CLI/TUI coverage |
| Browser WebAssembly | Optional source build, local server, existing-account connection and supported browser workflows |
| Updates | Daily release notices, dismissal and installation-specific Omarchy/Homebrew/manual upgrade guidance |
| Bar background refresh | Configure periodic checking while the dropdown is closed |
| Terminal background cache | Optional five-minute cache fetching while the TUI is closed |
| Terminal cache | Startup, loading states, retention, cached search and clearing mail |
Privacy and distribution#
- Privacy and credentials: tokens, cached mail, browser routing and the separate bar/terminal grants.
- Memory: what the published measurements include, with dates, versions and workload limits.
- Distribution and Google registration: user-supplied OAuth registrations and the distinction between testing, publishing and verification.
- License notices: bundled third-party licenses.
Development and reference#
Developing Omagma is the entry point for source builds, local changes, tests and release qualification. These tasks are separate from normal installation and account onboarding.
| Reference | Purpose |
|---|---|
| Next priorities | UX audit, safety follow-ups and useful TUI/CLI parity proposals |
| Agent development rules | Compiler, ownership, privacy and local iteration rules |
| Backend transport / bar protocol | Backend and UI integration contracts |
| Terminal implementation | Module ownership and terminal runtime architecture |
| Terminal provider | Gmail/People operations and capability/credential design |
| Terminal UI | Rendering, input, composition and lifecycle design |
| Browser architecture | Shared TUI controller, platform/provider adapters, fixed budgets and browser capability boundaries |
| Bar verification / terminal verification | Developer correctness and resource checks |
| Release maintenance | Version-driven Linux/macOS bundles and publication |
| Zig wiki follow-up | Curator notes distinguishing compiler findings from application bugs |
Historical evidence#
These reports retain their actual versions, source revisions, platforms and failed/passed checks. They are reference material rather than installation steps or claims about a later development build.