Docs

Using Waydock

Last updated: July 8, 2026

Waydock brings your mail, calendar, meetings, tasks, and chats into one governed place you can work from every day. This guide is for members using the web app: how to get set up, what each screen does, and how to stay in control of what leaves your account. If you want to connect your own AI agent over MCP, that is covered separately in the Quickstart.

For agents: this page is available as Markdown at /docs/using-waydock.md. If you are an automated client rather than a person reading the app, start with the Quickstart and the Tool reference instead.

First run: connect a mailbox

Setup is one blocking step. After you sign in with Google or Microsoft, you land on a welcome screen with two panels: the left panel is the connect action (Gmail or Outlook), and the right panel is a live status panel that shows your inbox syncing in real time. Connecting is read-only to start; Waydock only reads your mail until you grant an agent more.

Once the first sync finishes, the panel flips to a synced count and a Continue to Waydock button takes you to Today. You can add a second mailbox from the same screen, or skip and finish setup later from inside the app.

Finishing setup on Today

For new users, Today shows a Finish setting up Waydock checklist with three non-blocking tasks:

TaskWhat it doesWhere it goes
Mailbox connectedConfirms Gmail or Outlook is connectedBack to the connect screen
Connect your AI agentMints a scoped MCP key for Claude, Cursor, or any MCP clientSettings, Account, MCP
Turn on your daily briefEnables a morning digest (defaults to 7:00am local)One click, in place

The checklist is optional. Dismiss hides it for good. It disappears on its own once you have connected an agent.

Today

Today (/today) is your landing page. It opens with a time-aware greeting and a short brief paragraph, followed by a Waydock noticed callout listing the top things that need you. Below that:

  • Today's meetings: calendar events happening today, with join links and Fathom prep chips where available.
  • Worth a look: the unread mail that matters, denoised so newsletters and automated mail do not crowd it out.
  • Due today: follow-ups you owe that have crossed their reply threshold.
  • Finance & receipts and Security & codes: collapsed shelves that keep receipts and login or verification mail out of the way until you want them.

The Email me button in the top bar sends the current brief to your inbox. On a personal workspace, Today also shows a Readiness strip with your WHOOP recovery, sleep, and strain.

How mail gets sorted

Waydock classifies each email and sorts it into one of four intent buckets. This is what powers the shelves and the denoising:

BucketIncludesReply expected
securityLogin, security, and verification mailNo
financeInvoices, receipts, purchasesNo
automatedNewsletters and notificationsNo
humanReal person-to-person mail (work, personal, travel, calendar)Yes, when it needs a reply

Self-to-self briefings are suppressed and automated mail is shelved, so the focus surfaces stay about the things that need a person.

Inbox

Inbox (/inbox) is a card-based triage surface for incoming mail. Cards carry the sender, subject, snippet, timestamp, and a classification. Mail is grouped into Focus, Review, and Archived lanes. From a card you can:

  • Read the full message body (this can be turned off by your org).
  • Mute sender or mute domain to route that source to a quieter lane automatically.
  • Create task to push an item into Jira or Linear.

Calendar

Calendar (/calendar) shows your connected Google or Outlook events with attendees, times, and locations, rendered in your timezone.

Meetings

Meetings (/meetings) lists recordings pulled from your notetaker integrations (Fathom, Fireflies, Pocket): title, date, attendees, duration, summary, and extracted action items. Open a meeting for the full detail and transcript.

  • Delete moves a meeting to Trash (you are asked to confirm). It is a soft delete, so nothing is lost.
  • Switch to the Deleted filter to see trashed meetings and restore any of them.

Meetings arrive by webhook from the notetaker, so one shows up once its transcript is ready. Durable, encrypted transcript storage (so records survive a provider's retention window) is an org-level opt-in.

Follow-ups

Follow-ups (/follow-ups) is your commitments tracker. It covers two kinds of item: awaiting reply (an email thread where you are waiting on someone) and meeting action (an action item pulled from a transcript). Filter by:

  • Perspective: Theirs (you are waiting) vs Mine (you owe a reply).
  • Status: Open vs Chased.
  • Source: All, Meetings, or Emails.
  • Assignee and a day-range slider.

On any item you can snooze it (1 day, 3 days, 1 week, or 2 weeks). On an awaiting-reply item, Send nudge drafts an AI-written chase email in your own Gmail or Outlook and gives you a link to open and send it. The nudge is a draft: nothing is sent until you send it yourself.

The old /action-items page now redirects permanently to /follow-ups.

Tasks

Tasks (/tasks) shows your issues from connected task managers (Jira and Linear) in one list, with a link out to the source.

Mail archive

Mail (/mail) is the searchable archive of your past email, separate from the Inbox triage surface. Full email bodies are only kept when your org opts into at-rest body capture (encrypted, retention-bounded). See Integrations for how data flows in.

Teams

If Microsoft Teams is connected, Teams (/teams) holds your archived Teams chat messages. Message body capture is an org-level, encrypted opt-in.

Mira, the in-app assistant

Mira is the chat rail on the right of every app page. Ask it things like "What is on my plate this morning?" or "Draft a reply to the Acme thread," and it reads across your mail, meetings, tasks, and calendar to answer, with the source of each fact shown. Mira runs the same tools and the same guardrails as an agent connected over MCP:

  • When Mira wants to do something with consequences (send an email, message a Teams chat), it pauses and shows an approval card. Nothing happens until you click.
  • Once Mira reads untrusted content (an email body, a transcript), its send and delete abilities switch off for the rest of that turn, so a message in your inbox can never talk your assistant into sending your data.
  • Model calls go direct to the model provider, with no gateways in between, and Waydock never trains on your data.

Mira is billed per active member. On Free you get 3 Mira turns a day; Pro unlocks full Mira with summaries, drafts, and suggested prompts. See Pricing.

The morning brief

Set a daily brief in Settings, Account, Morning Brief. Pick a local send hour and your timezone, then choose one or more channels:

  • Email: the brief lands in your inbox.
  • Webhook: an HTTP endpoint, with the payload shaped for Slack, Teams, Discord, or plain JSON or Markdown (the format is detected from the URL).
  • Telegram: delivered to your linked Telegram chat, where that channel is enabled for your workspace.

The brief is a short digest of top actions, meetings, and nudges. The outbound kill switch (below) stops scheduled brief sends along with everything else.

Connecting your own AI agent

If you use Claude, Cursor, ChatGPT, or your own code, you can give it the same access Mira has. In Settings, Account, MCP ("MCP Keys & Setup"), mint a scoped key:

PresetAccessPlan
Read & email myselfRead everything, and only ever email your own inboxesFree (default)
Full accessRead and act, with sending to other people kept as a separate opt-inPro

Paste the key into your client's MCP config. Every call is scope-checked and written to your audit log, and you can revoke the key in one click. Full setup is in the Quickstart and Authentication.

Settings

SectionWhat you do there
ConnectionsConnect, revoke, or re-authorize any account, and toggle drafting or sending per source
Connect from another deviceGenerate a one-time link to add a provider from a second device
Account, MCPMint and manage scoped agent keys
Email allowlistManage who agents can email, per-recipient HTML, and the outbound kill switch
Morning BriefConfigure your daily digest
SecurityAdd passkeys and TOTP, review sessions and sign-in history
WebhooksGet a real-time ping whenever your account sends anything
ActivityReview sign-in and sync history
Historical AccessSee which agents and keys have touched your data

Staying in control

Every outbound send, whether it comes from Mira, a connected agent, or a scheduled brief, routes through one set of controls you own:

  • Outbound allowlist. Agents can only email addresses you have added in Settings, Account, Email allowlist. A brand-new recipient sits under a 60-second cooldown before the first send.
  • Caps. Sends are capped per day and per recipient (500 a day and 20 per recipient by default), so a mistake cannot fan out.
  • Approval cards. Send, delete, and external-share actions pause for a human click.
  • One audit log. The app and the agent endpoint write to the same place. Revoke a key once and both stop in the same moment.
  • Kill switch. Flip Allow outbound sending off and no mail leaves your account by any path (agent, brief, or automation). It is checked at the moment of send.

If your org has not locked the allowlist, you can opt your own account out of it from the same page. Full detail is on the Security page.

See also