Skip to content

Command codes

Put a short code on the first line of the email you forward to Nora. Codes tell Nora what to do and how. Plain English works too.

Safety first

Nora only ever prepares text for you to review and send. It never sends to a recipient and never books or schedules anything. Codes that imply those actions are understood, but Nora replies that they aren't available — it never acts on your behalf.

Grammar

  • A code sequence starts with NB and is dash-split; refinements attach with dots. Example: NB-RE-MN.I = reply, in my name, informal.
  • A bare single code also works: RE, S.
  • Extra instructions go in [square brackets]: RE [keep it brief and warm].

Actions

Code Meaning Available now
RE Reply — draft a reply
SC / S Summarize the email + attachments
AC Analyze — a critical, constructive analysis
AR Analyze a report
PR Prepare a report (as email text) ✅ text
FI / I Find / research info on people & company ⏳ recognized, not yet available
BM / SM Book / schedule a meeting ⏳ never auto-booked

⏳ means Nora understands the code and tells you it isn't available yet, offering the closest text deliverable instead — it never silently fails.

Refinements

Code Effect
.MN Write in your own name / voice
.F / .I Formal / informal tone (default: neutral)
.Long / .Short Longer / shorter
@from / @cc / @<email> Who the message is aimed at
C Confidential — keep internal
P High priority
[ ... ] Extra instructions in plain text

Examples

You send Nora does
NB-RE-MN.I [keep it brief] A brief, informal reply in your name
NB-SC.Short A short summary
AC A critical analysis
NB-PR.E [focus on risks] A report (email text) emphasizing risks
plain English: "reply declining politely" A polite declining draft

Revising a draft

Reply to Nora's email with the change — e.g. "make it warmer" or "shorter" — and Nora sends back a revised draft. You're always the one who sends the final email.