The Mac app. The Windows and Linux app, with buttons on each row instead of swipes:
My turn,
Waiting,
Snoozed.
Install
- Mac (macOS 14 or later): Remora.dmg,
then drag Remora to Applications. It isn't notarized yet: the first time, right-click Remora → Open (on macOS 15:
System Settings → Privacy & Security → Open Anyway).
- Windows 10 or 11 (preview): Remora-Setup.exe,
a per-user install with no admin rights. It isn't signed yet: if SmartScreen warns, click More info → Run anyway.
- Linux (preview, community supported, x86_64): Remora-x86_64.AppImage,
which updates itself, or Remora-amd64.deb
for Ubuntu and Debian. It needs a keyring for the tokens, and lives in the tray (on GNOME, add the AppIndicator
extension, or it opens as a window); details.
Then connect a first tool: getting started.
Remora is one inbox in your Mac’s menu bar, or the system tray on Windows and Linux, for everything that needs you:
code reviews, your own merge requests, Slack mentions and DMs, Linear and Jira issues, Notion tasks, Outlook mail,
invitations and Teams chats, and your own reminders. It sorts them by what you have to do (To reply, To review, To fix, Ready to merge…), not by
where they came from, and shows no more than you can take in.
It is built for teams with strict data rules: nothing leaves the computer except to the tools you allow. There is
no Remora server, no account and no telemetry; sorting, ranking and advice run on the device. An assistant (Claude, or
an OpenAI-compatible model) can add a short brief, off by default and only where the organization allows it.
Inspired by gitbar (merge requests in the menu bar), Gestimer (drag down to set a reminder)
and Google Inbox (bundles, Done, Pin, Snooze). Same design system as Myna. Built with the
help of Claude (Claude Code, Anthropic's AI assistant).
| Part | What it is | Stack |
|---|
Remora for macOS macos/ | The menu bar app | Swift 6 (strict concurrency), SwiftUI and AppKit, NaturalLanguage |
Remora for Windows and Linux desktop/ | The same rules, sources and assistant in a tray app for Windows 10 and 11 and Linux, in preview: keyword sorting only, what differs | Rust, Tauri 2, Svelte |
Website site/ | Marketing pages in English and French, static on Cloudflare | HTML, CSS, a Python generator |
Docs docs/ | The user guide, IT and compliance, and developer docs, in English and French | VitePress |
Features
- My turn / Waiting: My turn holds what someone is waiting on you for (review requests, mentions, DMs, tasks,
due reminders, and your own merge requests once approved, blocked or failing). Waiting holds what you're waiting
on others for. Snoozed and Done are one click away.
- Verbs: To reply, To review, To fix, Ready to merge, To do, Reminders, To read (shown last, not
counted) and Waiting on others, whatever the source. Chat messages are sorted on your computer: keyword rules in
English and French first, then, on the Mac, Apple's on-device sentence embeddings. When unsure, To reply.
- Done hides an item until something changes on it (new commit, approval, comment…). Pin keeps it at the top.
- Priority: overdue and due today first, then the tool's priority (Linear Urgent, High…), the nearest due date,
recent activity. Low priority is shown, not counted. Long bundles show their top five and "Show N more".
- Menu bar (Mac): one count, or one per tool ordered by the most pressing verb. Click to open, drag down to
cast a reminder (a bubble shows when it comes back; further down is later), right-click for Refresh, New
reminder, Settings and Quit. Two-finger swipes: right for Done, left for Snooze.
- System tray (Windows and Linux): one count; Ctrl+Alt+R casts a reminder from anywhere, and Done and Snooze are buttons on
each row.
- Snooze with a reason: waiting for someone, no time now, needs focus, not urgent, not feeling it. Each reason
suggests a return time; waiting can come back "until there's news". Presets, or a scrubber: minutes, then
hours, then days. The Snoozed tab shows one insight at a time: loops, pile-ups, items on the same topic
(on-device word embeddings on the Mac, shared words on Windows), items gone quiet.
- Review prep and sessions: "~6 min · 4 files · tests ✓ · Auth" under each review request, from file paths
and line counts only. Start session goes through them one by one, quick wins first (⏎ open, D done,
S snooze, → skip).
- Links between tools: a pull request and a Linear issue with a similar title are shown together.
- Waiting assistant: suggested reviewers when there are none, a drafted nudge when they stay silent for a day.
Written locally from templates; you copy it, Remora never sends.
- Learns your habits on your computer: what you handle fast and what you push back breaks ties within a bundle,
and a small star says why.
Sources
| Plugin | What it shows | Credentials |
|---|
| GitHub (+ Enterprise) | Pull requests you opened, review requests, issues assigned to you | Fine-grained token, read-only Pull requests and Issues (or a classic token: repo, read:org) |
| GitLab (+ self-hosted) | Merge requests you opened or review, approvals, pipelines; other To-Dos (issues, mentions) | Token: read_api |
| Bitbucket (Cloud or Data Center) | Pull requests you opened or review, approvals, changes requested, build status | Cloud: API token (read:user, read:repository, read:pullrequest), e-mail and workspace; Data Center: HTTP access token |
| Azure DevOps (+ Server) | Pull requests you opened or still have to vote on, votes, policy checks; work items assigned to you | Personal access token: Code (Read), Work Items (Read) |
| Slack | Mentions, DMs and replies in your threads from the last N days; your questions still waiting; reactions (✅ moves an item to Done) | User token xoxp-…: search:read, channels:history, groups:history, reactions:read, emoji:read |
| Linear | Issues assigned to you (priority, due date), unread mentions and comments | Personal API key |
| Jira (Cloud or Data Center) | Issues assigned to you (priority, due date, status), and recent comments that mention you | Cloud: API token and e-mail; Data Center: personal access token |
| Microsoft 365 (preview) | Flagged mail and unread mail sent to you, invitations you haven’t answered, unread Teams chats | Sign in through the browser, with the app your organization registered in Microsoft Entra |
| Notion | Open tasks assigned to you in chosen databases | Personal access token, or an internal connection's secret |
| Claude Code | Brief, summaries, triage, on your Claude plan | Claude Code signed in on this computer |
| Claude API | Brief, summaries, triage | Anthropic API key |
| OpenAI-compatible | Brief, summaries, triage | API key and server (OpenAI, Azure, Mistral), or none on a local server |
Accounts can be named ("Work GitLab", "Client Slack"), several per tool. Setup: connecting your tools.
Privacy and compliance
- Declared destinations. Every plugin declares the hosts it may reach; a test fails if one doesn't.
- One gate. Plugins only get an HTTP client limited to their own hosts plus the account's host. Anything else
fails with "Blocked: … is not an allowed destination", look-alike domains included (tested).
- External AI off by default. Assistant plugins are refused until it is allowed, except a server on the
computer; then the AI features appear.
- Managed policy. IT can lock the allowed tools, external AI and avatars with an MDM configuration profile
(
fr.igitscor.remora: AllowedPlugins, AllowExternalAI, AllowRemoteImages); on Windows, under
HKLM\SOFTWARE\Policies\Remora; on Linux, in /etc/remora/policy.json.
- Local data. Tokens in one Keychain item; everything else in
~/Library/Application Support/Remora/. On
Windows, the Credential Manager and %LOCALAPPDATA%\fr.igitscor.remora; on Linux, the Secret Service and
~/.local/share/fr.igitscor.remora, readable by you only.
Settings → Privacy lists every data flow and erases local data. No telemetry, analytics or crash reporting.
Every flow, the MDM profile and deployment, for IT and compliance teams: the admin docs.
Engineering highlights
- Clean architecture, plugins for every integration. Domain and rules in
RemoraCore, sources and assistants
in RemoraPlugins, the app on top. A plugin is a manifest (fields, setup steps, egress) and a fetch.
- On-device ML first. Keyword rules, then Apple's NaturalLanguage sentence embeddings to sort messages; word
embeddings and a rare-token check for topic similarity; Naive Bayes for personal ranking and snooze advice.
Calibrated for precision: a missed group beats a wrong one.
- Compliance enforced at one point. A guarded HTTP client per plugin, a policy object readable from MDM, and
tests for look-alike domains.
- One spec, two apps. The Windows and Linux app ports the Swift rules and plugins to Rust with the same fixtures and tests;
native-tls uses the Windows certificate store, so corporate root certificates just work.
Quality
| Suite | Tests | What it covers |
|---|
| macOS (Swift Testing) | 485 | Verbs and classification in both languages, placement and counts, Done and snooze rules, snooze clock and advice, review prep, links, waiting assistant, ranking; every plugin against fixtures; the compliance gate, link and redirect checks, https-only hosts; the assistant's requests and the claude runner; the app layer (connect, saving, erase, disconnect, notifications, MDM policy, the Keychain vault) on a temporary folder |
Windows (cargo test) | 481 | The same rules, the six source plugins against the same fixtures, the guarded client, link and redirect checks, https-only hosts, the registry and Linux policy, storage, the inbox service, and what the tray shows |
CI runs each suite when its folder changes, and on demand.
Building it yourself
Requirements: macOS 14 or later and Xcode 16 (Swift 6 toolchain); Rust (rustup) for the Windows and Linux app.
cd macos
make test # unit tests
make run # build build/Remora.app and launch it
open build/Remora.app --args --demo # sample data in a window, nothing saved
cd desktop && cargo test --workspace # Windows and Linux core and plugins
Copy build/Remora.app to /Applications and turn on Open at login in Settings.
Working on Remora: CONTRIBUTING.md. From the repository root, make test runs every suite,
make check what CI runs, and make alone lists the rest (demos, translations, docs, website). Signing and sharing the app:
building and releasing.
Documentation
The documentation is at triage.iscor.me/docs, in English and French; its sources are in
docs/ (VitePress).
- Guide: getting started, connecting your tools,
the inbox, snooze and reminders, reviews,
the assistant, FAQ.
- For IT and compliance: overview, data flows,
MDM policy, deployment, code signing policy,
accessibility.
- Developers: architecture, writing a plugin,
building and releasing, Windows and Linux,
proposal: delegation.
Releasing
make release V=0.7.0 checks, then pushes one commit (version, changelog, site pages) and the tag v0.7.0: the
release workflow checks that the tag matches the source, tests and builds both apps (signed
as the code signing policy says), and publishes Remora.dmg, Remora-Setup.exe, the AppImage and the .deb with their SHA-256, SBOM
and signed build provenance in one GitHub release, only if every build succeeds. The download links above always point to the latest one.
Website
site/ holds the marketing pages and, built from docs/, the documentation, served by Cloudflare as static assets (no server code, a strict CSP, no
analytics). The copy lives in site/copy/ and the markup in site/templates/; site/build.py writes the English and French pages:
macos/scripts/screenshots.sh # the demo inbox, each tab, both languages and schemes
make og # social cards, after a change to site/og/card.*
make deploy # docs, then Cloudflare (the release workflow does it after each release)
Security
Please report vulnerabilities privately, as SECURITY.md explains. What changed in each release:
CHANGELOG.md.
License
GPL-3.0-or-later. Remora bundles the Outfit font (SIL Open Font License 1.1) and tool logos from Simple
Icons (CC0); see macos/Resources/LICENCES.txt.
