Robin

A personal attention router

What matters.
All connected.

The email you should read. The reply you owe. The things to stay ahead of. Robin connects your mail, messages, calendars and other sources to bring you what needs your attention, with the context to do something about it.

See how it comes together

Your machine. Your context. Your attention.

Thursday · Your attention, in context

GmailQuote needs a reply
FastmailDue Tue · In transit
Google Calendar09:00 · Meeting
Slack“Now at the studio.”
Robin

What deserves your attention

  • Read & reply

    Maya Chen needs your decision.

    Her revised quote is in. She needs an answer today.

  • Coming up

    Your 09:00 moved to the studio.

    The new address is in the message, alongside the meeting.

  • Follow up

    Your parcel is overdue.

    It was due Tuesday. The latest notice still says in transit.

Illustrative scenario · Includes planned sources and proactive features.

Read what matters.
Stay ahead of the rest.

An important email, a changed meeting, an order that needs chasing. Robin joins the context, surfaces what needs you, and keeps routine updates for later.

01 / Attention, with context

Your life doesn’t fit
inside one app.

Read the message with the context behind it. Catch a change of plan. Notice when an expected update never arrives. Robin is being built to connect the pieces and bring the right things to your attention.

Illustrative scenarios · The proactive features we’re building toward

01 / Read what matters

The email that
needs you.

A person is waiting on your answer. Robin brings the message forward with the context you need to respond.

  • GmailMaya Chen sent a revised quote and needs your decision today.
  • Google CalendarYou’re meeting the supplier tomorrow at 09:00.

Robin brings you the email and the reason to read it

“Maya Chen needs a decision today. Here’s her revised quote, with the context for your supplier call.”

02 / Remember what’s still open

The flight is booked.
Is your passport ready?

A renewal email weeks ago. A flight booked today. Different accounts, different threads; a connection worth checking before you travel.

  • Personal · FastmailYour passport renewal was still in progress a few weeks ago.
  • Work · WorkspaceA flight booking for you arrives in your work account.
  • Robin checksNo later message confirms that the new passport is ready.

Robin connects the two and asks once

“Your work flight is booked. Last I saw, your passport renewal was still in progress. Have you received the new passport?”

03 / Catch the mismatch

The plan changed.
Did the booking?

Your latest instruction matters. So does the confirmation that still says something else. A small question now can save a surprise later.

  • Booking emailYour ski-pass confirmation says Saturday.
  • Your conversation“We’re going on Sunday instead.”

Robin asks while there’s time to act

“You said Sunday, but your ski pass says Saturday. Does the pass cover Sunday too?”

04 / Notice what’s missing

The parcel that
went quiet.

An order and its updates can land in different inboxes. The useful question is whether it’s actually getting to you.

  • GmailOrder confirmed. Delivery expected Tuesday.
  • FastmailA carrier notice for the same tracking number.
  • Time passesThursday arrives. No delivery or further update.

Robin connects the order and follows up

“Your parcel was due Tuesday. There’s been no delivery update. It may be worth checking with the merchant.”

Mail and calendar reads work today. These examples show the direction: proactive checks, meeting briefs and questions that connect the evidence, arriving in stages.

02 / More of your world, connected

Different providers.
One picture.

Mail, calendars, messages and the world outside. Each source adds context to the same assistant, so a change in one place can make sense of something in another.

Connected today

Mail & calendars

Personal and work accounts, considered together.

  • Gmail
  • Google Workspace
  • Fastmail

Planned

Traffic & weather

Travel times, forecasts and weather alerts, connected to your plans.

  • Google Routes
  • Google Weather
  • Weather alerts

Planned

Messages & channels

Information sources that help Robin follow what matters across conversations.

  • Slack
  • Telegram
  • WhatsApp

The pieces work together

A meeting on your calendar. A changed address in a message. Traffic on the way, and rain in the forecast. Robin’s goal is to bring you the useful answer: when to leave, where to go, and what to prepare for.

03 / A familiar way to talk

Call Robin.
Or let Robin call.

A personal assistant should be a conversation away. Ask a question, give an instruction, or hand over the call you’ve been putting off.

Phone capabilities · On the roadmap

You → Robin

Your assistant, on the line.

Call Robin to ask questions about your day, catch up on what changed, or give instructions by voice. The same context as your chat, wherever you’re calling from.

“What do I need to know before my next meeting?”

Robin → On your behalf

Let Robin handle the call.

Make a reservation, arrange an appointment or get an answer. You approve who to call, the goal and the limits; Robin makes the call on your behalf and brings back the outcome.

“Call the restaurant and book a table for two, around eight.”

One continuous conversation, whether you type or call.

04 / Attention, considered

Everything gets considered.
Only some things need you.

A message arriving and a message mattering are two different events. Robin’s routing policy gives each one a place.

Try an example

RobinA considered decision

Interrupt

This one deserves you.

A direct message from someone you’ve replied to before. Bring it to your attention.

NowBatchDigestQuiet

Illustrative policy examples. Live notifications and order tracking are being built.

01Rules first. Use a model when judgement is needed.

02Uncertainty stays visible. It never becomes silent confidence.

03Keep the reason. Decisions can be inspected and replayed.

05 / Good ideas have a lineage

Modern intelligence.
Old-school discipline.

qmail, for separation.

Robin’s process design is heavily inspired by qmail: small processes with narrow jobs and only the access they need. Keeping untrusted mail, credentials and model work apart helps limit what a failure or malicious message can reach.

OTP, for recovery.

Robin takes inspiration from Erlang’s OTP through Suture, bundled with its Go code. Supervised services can recover from failures, so a recoverable worker can restart without taking healthy neighbours with it. The benefit is an assistant built to keep going.

06 / Personal, by design

Close to your life.
Careful with its reach.

Robin is built for one person, running on their own infrastructure. A continuous conversation, with your context behind it.

Your state stays yours.

Mail, calendars, conversation and decision history live on your host. Model requests go to the configured vendor; self-hosted does not mean local-only inference.

Reading isn’t permission to act.

Mail triage runs in a fresh context with no tools. The conversation agent gets a restricted read bridge. Write actions belong to a separate, approval-gated actuator in the design.

A reason you can come back to.

Robin records how a decision was made. The audit view and replay tools let you inspect it, instead of guessing what the assistant was thinking.

In active development

Taking shape.
One careful step at a time.

Robin is running with Gmail, Google Workspace and Fastmail, mail and calendar ingestion, read-only chat, shadow triage and an inspectable decision history.

Next: policy-driven notifications, digests, and orders that stay connected to their updates. Phone calls, traffic, weather and messaging sources are part of the longer-term direction.

An early project, built in stages. Public installation instructions and downloads are still to come.

A little more space
for everything else.

Back to the beginning

Fastmail and its logo are trademarks of Fastmail Pty Ltd. © Fastmail Pty Ltd. Other provider marks belong to their respective owners.