OmaDigest

OmaDigest is a native Omarchy attention layer and background agent. Built around a custom harness using Pi, it observes the existing notification service, applies deterministic privacy policy before persistence, gathers bounded context from enabled integrations, and lets a tightly scoped attention agent hold, alert on, or brief you from permitted evidence. When you need to focus, OmaDigest handles the feed without taking over the rest of your computer.

It does not replace the notification daemon or put a general-purpose agent inside the shell.

Status: Beta. The release demo exercises notification intake, privacy, DND re-entry, digest generation, source controls, template suggestions and authoring, and default-agent integration authoring. Dictation, scheduling, and read-aloud remain optional beta surfaces.

Highlights

• Briefings, not another inbox — answer “what needs me?” instead of replaying every popup.
• Privacy before persistence — protected apps such as Signal start at Ignore; unknown apps start at Count only, with content erased.
• Citations by construction — every factual digest entry must cite a supplied notification or connector source ID.
• Source jump-backs — expand a digest entry's sources to open its retained HTTPS page or focus the originating application, with an explicit unavailable state when an app notification has expired.
• Deterministic templates — TypeScript, not the model, chooses the governing briefing skill.
• Attention intelligence — conservative subject grouping plus a bounded attention agent can recall prior episodes, watch an evolving subject, create the right digest, or surface a time-sensitive alert without granting notification text execution authority.
• Conversation-aware calm — known chat notifications wait for a per-thread quiet window, collate into one conversation group, and refresh a recent matching digest instead of producing one digest per message.
• Outcome-first compression — conversations and correlated feeds become the smallest useful set of requests, decisions, blockers, and changes while raw provenance stays behind Sources.
• Progressive memory — a provenance-preserving temporal memory keeps recent episodes detailed, compresses older context into rebuildable summaries, and lets the agent search or zoom before deciding.
• Attention timeline — inspect received evidence, holds, digests, alerts, handoffs, and feedback as subject threads, then switch to a time-decayed memory view and open compressed spans back toward their source moments.
• Recurring research — keep a question warm on an hourly, daily, or weekly cadence; choose focused, broad, or deep web research plus a change window, then receive a compact cited brief only when current evidence supports a meaningful change.
• Cross-source correlation — stable PR, issue, repository, URL, and CVE entities join related notifications, CI results, connector evidence, and agent activity without relying on matching app names.
• Timely event prep — approaching meetings and deadlines can schedule a bounded pre-event checkback, recall related history, and produce a focused briefing.
• Attention rules — describe what should interrupt, wait, become a digest, or stay quiet; a scoped compiler previews current matches and priority conflicts before the deterministic rule is saved.
• Outcome learning and explanations — useful/not-useful feedback, reads, handoffs, and cancelled watches become visible bounded calibration signals, while Why this? links the evidence, correlation, matching policy, and subject timeline.
• Templates stay yours — edit instructions and routing JSON directly, or ask the constrained in-panel agent for a validated revision; editing a packaged default creates a resettable user overlay.
• Right-sized authoring — a scoped session drafts readable templates in-panel; integration requests open the default coding agent with a dedicated skill and a validated, disabled-by-default install path.
• Sandboxed connector boundary — integrations are disabled by default, permission-declared, removable, time-bounded, and run outside Quickshell.
• Useful sources out of the box — native Omarchy notifications and focus state, live-tested GitHub metadata, local crash and update state, system telemetry, and Herdr agent activity.
• Category-level control — keep a source enabled while turning off noisy streams such as completed tasks, network transitions, or account activity.
• Explicit action handoff — send one cited digest item to the default Omarchy agent, or continue broader authoring work in Herdr.
• Background attention loop — react after notification quiet windows, enabled-source polling, native events, DND re-entry, a daily schedule, or bounded watch leases that wake on related evidence, source changes, or a deadline; + always requests a fresh digest.
• Voice both ways — dictate authoring requests with Voxtype and optionally read completed digests aloud.
• Inspectable configuration — privacy, templates, integrations, permissions, setup, and enablement are file-backed and hot-reloadable.
• Theme-native UI — the Quickshell panel, spacing, typography, and monochrome mark follow the active Omarchy theme.

Demo

https://github.com/user-attachments/assets/1bfaaf85-1480-4b9f-a62c-b098f96d96a1

Music: “Study and Relax” by Kevin MacLeod, from the FreePD archive, dedicated to the public domain under CC0 1.0. See Third-party materials for all preview and demo-media credits.

Install

Requirements

• Omarchy Quattro with shell plugin support
• Node.js 22 or newer available as node
• Bubblewrap available as bwrap for the connector sandbox (included with Omarchy)
• an AI account connected in OmaDigest: Codex/ChatGPT, OpenAI, or Grok/xAI

Optional features:

• Voxtype for dictation
• secret-tool for integration and TTS secrets
• mpv for read-aloud playback
• herdr for explicit extended authoring handoff
• gh for the bundled, read-only GitHub notification integration

The complete lockfile-derived dependency license inventory and demo-media credits are documented in Third-party materials.

Add the plugin

omarchy plugin add https://github.com/jacob-vincent-mink/omadigest.git --enable

OmaDigest is a bar widget and defaults to the right section. If needed, place it explicitly:

omarchy bar put io.github.jacob-vincent-mink.omadigest --section right

Normal installation uses the checked-in broker bundle. It does not run npm, install hooks, invoke a package manager, or request privileges.

First run

1. Click the quill in the Omarchy bar.
2. Open Settings → Connections and connect the model account OmaDigest should use.
3. Review Settings → Privacy before allowing notification content into digests.
4. Let attention items accumulate, then press + to generate the first digest.
5. Optionally configure sources and their categories, draft a custom template, or set the widget's daily schedule in Omarchy's bar settings.

Read the usage guide for the complete workflow.

Update or remove

omarchy plugin update io.github.jacob-vincent-mink.omadigest --yes
omarchy plugin remove io.github.jacob-vincent-mink.omadigest --yes

Removing the plugin removes its executable plugin folder but deliberately leaves user-owned configuration and digest state in place. To erase those too:

rm -rf "${XDG_CONFIG_HOME:-$HOME/.config}/omadigest" \
       "${XDG_STATE_HOME:-$HOME/.local/state}/omadigest"

Review the paths before running the removal command. Secret Service credentials may be removed separately with your desktop's credential manager.

How it works

Omarchy notifications ─┐
Enabled integrations ──┼─► privacy filter ─► bounded attention store
                       │                           │
Quickshell panel ◄─────┘                           ▼
       │ NDJSON                         bounded attention proposal
       ▼                                  │ hold / digest / alert
TypeScript broker ◄───────────────────────┘
       ├─ searchable episodic memory + temporal summary tree
       ├─ bounded conditional-watch ledger
       ├─ scheduled cited research + claim ledger
       ├─ scoped digest Pi session ─────► validated cited digest
       ├─ Secret Service
       ├─ Voxtype
       └─ TTS provider + mpv

The QML plugin is presentation-only. A bundled TypeScript broker owns policy, persistence, routing, scoped model sessions, connector execution, authentication, voice, and explicit handoffs.

Security and privacy

OmaDigest gives each model session only the structured submission tool needed for its task:

These Pi sessions receive no bash, filesystem mutation, browser automation, or device tools. Research is the narrow exception for network evidence: its broker-owned tools expose a user-selected focused (4 searches/12 pages), broad (10/30), or deep (20/60) budget, bounded again by total source text and automatic daily work. Requests carry no credentials and cannot reach private addresses or source-defined actions. Integration authoring is deliberately different: OmaDigest opens the default coding agent with its authoring skill, which builds in a temporary directory and must pass the standalone package validator before an atomic, disabled install. Broader work starts only after Build in default agent, Open in default agent, Send to agent, or Continue in Herdr is clicked.

Generated integrations are schema-validated, syntax-checked, tested in the connector sandbox, probed with mocked inputs, installed atomically, and remain disabled until separately configured and enabled. Connectors use Node's permission model, a minimal environment, bounded I/O, and timeouts. Omarchy plugins themselves share the user's long-running shell process and are not an OS security boundary; review plugin code before installing it.

See Security policy and the detailed security model.

Templates and integrations

A template keeps human-readable instructions beside broker-validated eligibility and output policy:

templates/<id>/
├── SKILL.md
└── template.compiled.json

An integration is one removable package:

integrations/<integration-id>/
├── manifest.json
├── connector.mjs
├── connector.test.mjs
└── README.md

The bundled GitHub integration uses fixed read-only broker calls through the user's authenticated gh session and is exercised end to end in the demo; its connector receives neither a token nor process/network authority. Broker-native Omarchy sources cover bounded crash metadata, update availability, system telemetry, and Herdr agent transitions. Every source exposes category controls and a non-mutating status check; all start disabled except the existing Notifications and Focus/DND inputs. Calendar, chat, task, and social applications still participate through native notifications and per-app privacy rules. See the integration guide for the verified release scope and deliberately unbundled connectors.

Documentation

Why OmaDigest

I am a believer in the agentic OS: a malleable computer where much of an application can be a focused interface backed by an agent with the right context and narrowly chosen tools. OmaDigest is an experiment in that shape. The Quickshell frontend stays small; the custom harness does the bounded collection, correlation, routing, and summarization behind it.

The notification stream is a useful place to start because it already contains cross-application context, but usually presents it as isolated interruptions. An agent can collate related events, surface just-in-time information, and reduce context switching without becoming the main thing the user does with the computer.

Future plans

• More live-tested integrations with ordinary-user authentication.
• Repeatable connector instances for sources such as multiple RSS feeds or calendars.
• A way for integrations to ship independently, potentially by building on Omarchy's existing plugin system.
• Optional local semantic retrieval when it materially improves on the current inspectable entity and text search.

Development

The MVP was built in one day on August 20, 2026 using Codex with GPT-5.6 Sol and Herdr.

git clone git@github.com:jacob-vincent-mink/omadigest.git
cd omadigest
npm ci
npm run check
npm audit
node --test integrations/*/connector.test.mjs
qmllint -I "$OMARCHY_PATH/shell" BarWidget.qml Panel.qml components/*.qml

node_modules contains symlinks that the Omarchy plugin validator intentionally rejects. Validate a clean checkout or temporarily keep node_modules outside the repository:

omarchy plugin validate "$PWD"

See Contributing, Development, and AGENTS.md.

License and third-party materials

MIT © 2026 Jacob Mink. See Third-party materials for dependency licenses and demo-media credits.