Start from Now
Now is the front page: a short list of work from the five modes. Choose an item here, then finish it in its own mode. Now has no separate Done action. It shows at most ten things, in four sections that never change order:
- People: whose turn it is with you, from Messages. Never the people you are waiting on.
- Due soon: To do’s Now band, overdue first, then by act-by date.
- Updates: one card for the latest digest (cut at 08:00 and 16:30): its headline, up to three lines that need a look or changed, and how much routine waits behind them.
- For tonight: from 17:00, one issue to read, from the newsletter you read most.
Each section shows at most three items, then “and 11 more in Messages”. A
long list of people becomes one line: “14 people waiting on you: 7 you write
with, 7 others. Start with the three below.” “You write with” are people
you have written to; “others” are people who wrote to you and you have not
answered, whether it is their first message or not. The headline, that line,
“and 11 more in Messages”, Messages’ Your turn and the Messages count in the
rail all count the same rows (a person once, a group thread once), so the
numbers add up. A section with nothing in it disappears. When all four are
empty, Now says “Clear” until another item surfaces. The caps live in the
daemon, so the web app, the TUI and mxr now show the same ten things.
Open Archive when you need a filed receipt, booking or reference. Records remain available there without adding work to Now.
In the web app, expand the Since … arrived line to see where mail went,
answer sorting questions, and inspect the sorting track record. Those details
stay collapsed while you work through the main rows.
Open Now
Section titled “Open Now”The web app and the TUI open on Now. Press g h to come back to it from
anywhere. From the command line:
mxr now --format tableSaturday morning. 14 people waiting on you, 1 thing to act on.
PEOPLE (and 11 more in Messages) 14 people waiting on you: 7 you write with, 7 others. Start with the three below. Samir Patel Contract renewal details your turn since Friday Leo Park Research notes: terminal workflows your turn since Friday Ari Stone Flight options for the Portland demo day your turn since yesterday
DUE SOON Fix payment for Spotify £11.99 act now
UPDATES 16:30 digest (+11 more, 149 routine) 8 need a look, 6 changed. 149 routine from 5 sources. GitHub acme/api Run failed: CI - main (9f8e7d6) Google Security alert: New sign-in from Chrome on Windows (already in To do) Stripe Payout of R 4,210.00 failed: bank declined (already in To do)
Not now: Reading 5 this weekThat is the demo mailbox on a Saturday morning. Every row says which mode it
came from and why. mxr now prints JSON by default, with the same sections,
caps and lines.
See where everything that arrived went
Section titled “See where everything that arrived went”Under the headline, the web app shows an arrival count and how many emails need a sorting decision. Expand that line to see where mail went, answer sorting questions, and check the weekly track record. The details account for every email that arrived since you last opened Now (at most 24 hours back):
Since 08:12: 50 arrived. 8 Messages · 10 Updates · 31 Reading · 1 spam. Also 2 in To do.The counts sum to the total: each email is counted once, in the mode it is in now, and Spam and screened-out senders are counted too. To do and Archive are “also”, never added, because an email there is still in its own mode. A count of zero is left out. Each count opens exactly those emails, newest first, so checking that nothing went missing is one click from the claim. When Now has nothing waiting, the line becomes the end state:
Clear. All 50 emails since 08:12 are accounted for.“Accounted for” means every email went somewhere; it never claims you read them. Where an email went is recorded when it arrives, so mail you archive later still counts where it went. From the command line, without moving the line’s window:
mxr arrivalsmxr arrivals list --mode readingYour sorting choices win. Otherwise this email’s list and automation evidence
decides its destination, even from someone you’ve written to. Uncertain personal
mail stays accessible without automatically becoming Your turn. Press ? on the
line for the sorting policy, or read Messages.
Arrivals read the same stored assessment as the modes and Inbox chips. Cached
mail, sender history, aliases and teaching changes refresh that assessment.
The original arrival destination and first-seen time stay unchanged.
The stored-assessment details require changes made after
v0.6.158; that release does not include them.
Unknown purpose still has a home marked Not sure: Messages for possible
personal mail, Updates for machine mail. Expand the arrivals line for provisional-placement counts. Run
mxr classify report --format json for bounded clusters of observed facts. The report reads
stored answers only and names missing or stale assessments while reconciliation is pending.
Move an email to where it belongs
Section titled “Move an email to where it belongs”X moves the email under the cursor to another mode, on any row in Now,
Messages, Updates, Reading and Inbox, and in the reader. Pick the mode with
one key:
| Key | Moves it to |
|---|---|
m |
Messages |
x |
To do (adds a to-do from it) |
u |
Updates |
r |
Reading |
e |
Archive (files the email’s evidence as a record) |
The move takes effect at once in every client, and the toast asks once:
“Moved to Reading. Always for this sender? (P)”. P sends everything from
that sender to the mode from now on; u or Undo puts the email back. In
the picker, a capital M, U or R moves the sender straight away. To do
and Archive keep their own X (not a to-do, not a record).
A sender’s mode always wins over a move made before it, and a move made after it wins for that one email. Inbox rows name the mode each email went to, with the reason on hover or focus: “→ Updates · automated sender”.
mxr reclassify MESSAGE_ID reading --dry-runmxr reclassify MESSAGE_ID readingmxr reclassify MESSAGE_ID updates --sendermxr corrections # every move, newest firstmxr corrections undo 12Answer what mxr wasn’t sure about
Section titled “Answer what mxr wasn’t sure about”When two rules disagree, Now asks instead of guessing, at most three times a day. In the web app, expand the arrivals line to answer. This includes mail from someone you’ve written to that only copied you:
2 emails I wasn't sure about. Where should these go?Sam Okafor copied you on "Boiler service at the flat". Updates for now.X answers it: m, x, u, r or e sends it to that mode, and Enter
keeps it where it is, which counts as an answer too. After the answer Now asks once, “Always for this sender?”.
Once you have moved mail, Now shows how sorting is going, counted from your own moves: “Last week mxr sorted 310 emails; you moved 2.” It counts the emails you moved; mail you never opened isn’t checked.
Act on a row in its own mode
Section titled “Act on a row in its own mode”| Key | What it does |
|---|---|
j / k |
Next and previous row |
Enter |
Open the row in its own mode, on that row: a person in Messages, a to-do in To do, the card’s first line in Updates, the pick in Reading’s reader |
e |
Done here, in the row’s mode |
r |
Reply to a person |
a |
Reply all to a person |
f |
Forward a person’s email |
o |
Open the email |
E |
Let go of the Updates card, after a preview |
X |
Move this email to another mode |
P |
Move everything from this sender to a mode |
u |
Undo |
? |
What Now is for, then its keys |
r, a and f work on a person’s row, where the conversation is. A to-do,
the Updates card and the reading pick are not conversations: o opens the
email first, and the reader’s r, a and f work there.
Done here takes the conversation out of that one mode until a new message arrives. Other modes keep it, and the email is archived in your mail provider only when no mode holds it any more. The toast says which happened every time:
Done in Messages. Still in To do (due Mon).Done. Archived in Gmail.u or the toast’s Undo puts it back. To keep mail in the inbox even when
the last mode lets go, set modes.archive_on_last_done = false. The desk’s
own Done at /desk follows the same rule: it never archives an email To do
still holds.
In To do, e ticks off that one to-do. Another to-do on the same email stays
open, and the email stays in the inbox until the last one is ticked off. In
Updates, e lets go of one source in the digest.
On the web To do page, press e to tick off the lit row. When the left
checkbox has focus, Space ticks it off or reopens it. When another button or
link has focus, Space activates that control. Otherwise, press Space to see
the lit row’s explanation, arrival time and field evidence. You can also choose
details on the row.
mxr modes done THREAD_ID --mode todo --todo TODO_ID --dry-runmxr modes done --mode updates --sender notifications@github.com --account ACCOUNT_ID --dry-runE on the Updates card previews what letting go of the digest does (“Let go
of 11 updates from 4 sources; 1 also in To do stays there.”) and lets go of
exactly that set when you confirm. See
Updates.
See which other modes hold an email
Section titled “See which other modes hold an email”One email can be in several modes: the landlord who asks “are you around Thursday?” and sends a lease to sign by Monday is in Messages and To do. On Now and in Messages, a row shows a small glyph for each other mode that holds it (the same glyph the sidebar uses for that mode), and hovering a glyph says why: “In To do: Sign the document from Sam Okafor, act by Mon 5 Oct”. The reader and the person’s page keep the sentence, in that mode’s words:
Also in To do: Sign the document from Sam Okafor, act by Mon 5 Oct g xThe g key opens that mode. From the command line:
mxr modes why MESSAGE_ID # or --thread THREAD_IDAnswer a new sender’s one question
Section titled “Answer a new sender’s one question”When a person writes to you for the first time, their row carries a new
mark. Put the lamp on it (j, or a click) and the row’s actions give way to
four glyph buttons, one per answer; hover a glyph for its name. On the
keyboard, X opens the move picker, where M Messages, U Updates,
R Reading and D Block answer for the sender (P opens just those four).
The status bar spells it out while the row is lit: “New sender: X then
M Messages · U Updates · R Reading · D Block”. Answering moves the sender for
their future mail too, and undo puts it back. The digits 1 to 4 that used
to answer say where answering went until 0.6.197. Automated senders are never asked: their mail goes to Updates or
Reading, and the row’s why line names the rule. The
Screener page, under More, has a queue of the new
senders its badge counts and a tab of every sender you have decided on.
The rail
Section titled “The rail”The sidebar lists Now, the five modes and Inbox, with their keys:
| Entry | Key | Opens |
|---|---|---|
| Now | g h |
The front page; its badge counts people whose turn it is and things to act on |
| Messages | g m |
People and groups, with their conversations inside. The count is the people waiting on you, the same as Now |
| To do | g x |
Things email asked you to do, by when to act |
| Updates | g u |
Notifications as a briefing by source, twice a day |
| Reading | g r |
Newsletters as an edition, with a Later shelf. No count: nothing in it is owed |
| Archive | g e |
Filed receipts, orders, bookings, bills and documents |
| Inbox | g i |
Everything, newest first |
Screener, Waiting on, Subscriptions, Snoozed and Reply later are in the rail’s
Views and Mail groups. Subscriptions no longer has a g key; g u opens
Updates.
mxr modes rail prints the same list with counts.
On a phone the web app shows five tabs instead: Now, Messages, To do, Reading and More. More opens a sheet with Updates, Archive, Inbox and every other page. Updates also opens from the card on Now.
The desk’s lanes, and Messages
Section titled “The desk’s lanes, and Messages”Messages is now its own mode: people as rows with their topics inside. See
Messages. The desk still exists (mxr desk, /desk)
and shares Messages’ rule for whose turn it is:
- You owe: an unanswered directed request from someone you have written to, or an explicit reply-later reminder that returned.
- Due: a promise you made is coming due, by a date from the email’s words or one you typed. A date a model wrote does not count (unverified dates).
- Waiting on: you wrote last and they have not answered.
- New from people: a directed request from a possible person you have not written to before.
A thread you were only copied on, or one sent to more than 10 people, that you never wrote in is nobody’s turn: it is in Updates. A turn nobody took goes quiet after three times your usual interval with that person, at least a week. The exact lane rules are in the reference.
Person mail still in your inbox that no lane holds stays in Messages as quiet, so it never vanishes from every mode, and ticking off a to-do on it never archives it.
Open the desk
Section titled “Open the desk”In the web app, /desk shows the desk’s lanes. From the command line:
mxr desk14 replies owed, waiting on 4 threads, 7 new messages from people.
You owe 14 Jon Bell Research notes: terminal workflows · wrote to you 22h · usually 47m Samir Patel Contract renewal details · 2 messages since you last wrote 16h · usually 47m Samir Patel Action required: unusual sign-in attempt · wrote to you 10h · usually 47m and 11 more (--limit to see them)
Waiting on 4 Samir Patel Launch checklist for Project Aurora · no reply to your la… 1d Ari Stone Urgent password reset notice · no reply to your last mess… 1d Leo Park Weekly local-first reading list · no reply to your last m… 19h and 1 more (--limit to see them)
New from people 7 Cal Brooks Contract renewal details · wrote to you 4h Account Verification Build failed on release branch · wrote to you 8h Cal Brooks Spring upgrade offer for your workspace · wrote to you 11h and 4 more (--limit to see them)
Everything else: Reading 6 · Paper trail 3 · Deliveries 2 · Screener 27That output is from mxr desk --limit 3 against the demo mailbox. Each row
shows the counterparty, the subject, the reason, how long it has been, and
“usually” when mxr knows how fast replies go between you (the median of at
least two past replies). A row that is past its usual time is flagged
overdue; the web app colours its age.
The Everything else line counts what arrived this week in Reading and Paper trail, active deliveries, open invites and new senders in the screener. None of those are unread counts.
In the web app, the greeting counts the work (“Saturday morning. 3 replies,
2 promises.”) and each count links to its lane. A lane shows five rows;
Show all opens the rest. mxr desk --account NAME limits the CLI to one
account.
See what each row asks
Section titled “See what each row asks”With a language model configured, each row from a person says in one line what the conversation is about, and on You owe and New from people the reason becomes what they ask of you (“Asks: confirm who owns the rollout check”). The inbox, label queues, the reply queue and owed replies show the same line in place of the snippet, and so does the TUI.
Lines come from the cache at once. Missing ones are written in the background for the rows on screen first and appear as each is ready; the desk keeps a line’s space under every row, so nothing moves. Pointing at a line names the model that wrote it. Newsletters and mailing lists never go to the model, and automated mail only on Updates. With no model the rows look as they always did.
A local model writes a line every few seconds (about 3 s each with gemma4 on
Ollama), so a screen of rows fills in over a minute or so the first time,
then comes from the cache until someone writes again.
llm.gist_concurrency lets a hosted model write several at once.
mxr desk --gists # cached lines only, never waitsmxr briefing gists THREAD_ID --generate # queue the missing onesDeal with a row
Section titled “Deal with a row”Open the conversation, then do what it asks:
- Reply. The reply field sits at the bottom of the conversation. To answer everyone you owe in one sitting, use Focus & reply.
- Snooze. Snoozing takes the conversation off the desk until it wakes.
Type the time in words, such as
fri 3orin 2d(time phrases). - Keep a promise. Due rows are promises from mail you sent: ones mxr found, and ones you asked to be reminded about. Do the thing, then use Done. See promises on send.
When you reply, the row leaves You owe on its own. When they reply, a Waiting on row leaves on its own.
Come back to it later
Section titled “Come back to it later”Reply later takes a time. Press b on a row, type when you want it back,
such as tue 9, tomorrow or in 2d, and check the exact time shown under
the field before you press Enter. The toast names that time. What happens
depends on who wrote last:
- They did (You owe, New from people): reply later. The conversation leaves the desk and your reply queue, and comes back to both at that time under You owe, with the reason “back from reply later”. Your inbox is not touched.
- You did (Waiting on): bring it back if nobody replies. The conversation leaves Waiting on. If nobody has replied by then, it comes back with the reason “no reply by the time you set” and joins your reply queue so you can follow up. If they reply first, it lands in You owe as usual and the time is dropped.
It comes back on its own, once, even if mxr was not running at the time.
Press Enter with no time for the plain reply later: the reply queue, now.
On Waiting on a time is required. u, or the toast’s Undo, puts back
whatever was set before, for about a minute.
From the command line, preview with --dry-run, then set it. --at takes
the same time phrases:
mxr desk later 7f5a428a-90b3-5f5f-a276-bfc82dd82874 309ae832-4d84-5d78-a3ef-76a7eda21496 --at "tue 9" --dry-runWould set 2 conversations for Tuesday 6 October, 09:00 (in 6 days). 7f5a428a-90b3-5f5f-a276-bfc82dd82874 reply later: back in You owe and the reply queue then 309ae832-4d84-5d78-a3ef-76a7eda21496 waiting: back then if nobody has repliedmxr desk later 309ae832-4d84-5d78-a3ef-76a7eda21496 --at "in 3d"Set 1 conversation for Saturday 3 October, 15:58 (in 3 days). 309ae832-4d84-5d78-a3ef-76a7eda21496 waiting: back then if nobody has repliedUndo with: mxr undo 01a0f2d3-5a6c-7db2-8456-4781c4303b08Snooze is different: it takes the conversation out of the inbox until it wakes. Reply later leaves the inbox alone and only changes the desk and the reply queue.
Put a row away with Done
Section titled “Put a row away with Done”Use Done when a row needs nothing from you: a thank-you, a thread that resolved itself, a promise you already kept. What Done does depends on the lane:
| Lane | Done |
|---|---|
| You owe, New from people | Archives the conversation, marks it read, and keeps it off the desk. |
| Waiting on | Marks it read and stops waiting. Nothing is archived. |
| Due | Marks the promise kept and the conversation read. Other promises in the conversation stay. |
Every lane also takes the conversation out of your reply-later queue and drops any time set to bring it back. It stays off the desk until someone writes in it again, you or them.
- Web app: the check at the end of the row. On the desk the archive key
(
e) is Done, in every lane and on a selection, and from the reader when you opened the conversation from the desk.wwas Done too until it became Wake; on the desk it says Done iseuntil 0.6.206. With a mouse the check shows when you point at the row; on a touch screen it is always there, and a short swipe right is Done too. - TUI: the archive key on a desk row, or in the conversation opened beside the desk.
- CLI: preview first, then put it away:
mxr desk done 080a03cf-08ab-5aca-a5e6-73c9f269800d --dry-runWould put away 1 conversation. 080a03cf-08ab-5aca-a5e6-73c9f269800d owed would archive 5, mark 1 read, off the desk until someone writesmxr desk done 080a03cf-08ab-5aca-a5e6-73c9f269800dDone: 1 conversation. 080a03cf-08ab-5aca-a5e6-73c9f269800d owed archived 5, marked 1 read, off the desk until someone writesUndo with: mxr undo 01a0e733-f0fb-7510-9fb5-0462837a28aeThe thread id is the row’s thread_id in mxr desk --format json, or a
line of mxr desk --format ids. Without --lane, Done picks Waiting on when
you wrote last and You owe otherwise. For a Due row, pass the promise:
mxr desk done THREAD_ID --promise COMMITMENT_ID --dry-runWould put away 1 conversation. 93d1de1e-0556-5bcb-b5d9-9effb317b6b6 due promise kept, off the desk until someone writesKeys for every surface are in the keybindings reference. Holding a key down in the web app does not put away row after row. In the TUI a held key repeats, so tap once per row.
Undo puts everything back as it was: the messages return to the inbox, each read or unread as before, the row returns to the desk and to reply-later, and a promise is open again. Use the toast’s Undo in the web app or TUI, or the id Done printed:
mxr undo 01a0e733-f0fb-7510-9fb5-0462837a28aeUndoneThe undo window is about a minute.
If a conversation cannot be put away (its account is offline, say), its row
stays, the rest are done, and mxr desk done exits non-zero. The first
Done’s undo id still restores everything it changed. Run Done again to retry;
the retry gets its own undo id.
Stop waiting without marking read
Section titled “Stop waiting without marking read”mxr desk dismiss takes a Waiting on row off the desk until a new message
arrives, and changes nothing else:
mxr desk dismiss 309ae832-4d84-5d78-a3ef-76a7eda21496 --dry-runWould stop waiting on 1 conversation. 309ae832-4d84-5d78-a3ef-76a7eda21496mxr desk restore THREAD_ID puts it back in Waiting on.
Script the desk
Section titled “Script the desk”--format json returns every lane with its rows and totals. Row fields are
listed in the desk reference.
# Subjects of the replies you owe, most overdue first.mxr desk --format json | jq -r '.owed.rows[] | .subject'
# Read the most overdue one.mxr cat "$(mxr desk --format json | jq -r '.owed.rows[0].message_id')"Make the inbox your home instead
Section titled “Make the inbox your home instead”In the web app, set Settings > Appearance > Home to Inbox. The
arrival-order inbox shows everything, Updates and Reading mail included,
and Now stays one key away (g h).
When a conversation is not where you expect
Section titled “When a conversation is not where you expect”- Not on the desk at all: run
mxr why MESSAGE_ID. A newsletter or notification goes to Reading or Updates, and a screened-out sender never shows. To count a sender as a person, move them to People (move a sender). - Gone after you archived it: You owe and New from people show only while the conversation is in the inbox. Undo, or move it back and wait for the next message.
- Came back after Done: someone wrote in the conversation again. Done holds only until the next message, on purpose: new mail is new information.
- Gone after
b: you set a time. It comes back then; until then it is still in the inbox.uright away, orbagain with a new time, changes it. - In You owe instead of New from people: you have written to them before, or replied in that conversation.
- In New from people after you moved them to People: moving a sender to People makes their mail count as from a person. It lands in You owe once you have written to them.