Skip to content
Get Pricing Try Now
Work Context for Meta Muse

Give Muse context on how you actually work.

Muse already reads your calendar and inbox. Larridin Work Context adds what those apps cannot show it: the deal you spent the morning on, who you keep going back and forth with, and what is blocked. Private by default, governed by your org.

Request Access See how it works
Works with ChatGPTChatGPT dots Meta MuseMeta Muse InstinctInstinct ClaudeClaude Your own agent

What should I focus on today?

Muse

You have four meetings today. Your inbox has 12 unread messages.

Reads: calendar, inbox.

Muse + Larridin Work Context

The Acme renewal. You have been in the pricing sheet all week and the invoice is still unsent. Priya pinged you about it twice. That is blocking the Q4 forecast.

Reads: calendar, inbox, and how you actually worked this week.

Same Muse. Same question. Different answer.

Trusted by AI-forward enterprises

  • Vertiv
  • OK! magazine
  • Gainsight
  • The Signatry
  • Klaviyo
  • SurveyMonkey
  • Globality
  • TigerConnect
  • ConnectPay
  • The Joint Chiropractic
  • EcoVadis
  • Sundt
  • Polk County, WI
  • Source Advisors
  • Andelyn Biosciences
  • University of Hertfordshire

Why your agent needs it

Your agent is only as useful as what it knows about you.

Connectors give it a slice: your calendar, not your day. The explainer shows the gap, and what changes when your agent can see how you actually work.

Work Context, explained 1:40
0:12Connectors give your agent a sliceEmail, calendar, chat, Jira: each one shows your agent one app. You need dozens for the full picture.
0:29It sees your calendar, not your dayWhich deal you spent the morning on, who you keep going back and forth with, where you are stuck.
1:01Same question, different answerWith Work Context: the renewal, the unsent invoice, Priya waiting, the forecast it blocks.

How it works

Your agent sees how you actually work.

The desktop sensor observes how work happens across every app, not just the ones with an API: the projects you are on, the people you are working with, the things that are blocked. All of it becomes context your agent reads over MCP, with privacy controls that put you in control.

FinderFileEditViewWindowLarridinContext onTue 10:42
Pricing sheet.xlsxSpreadsheet
ABCD 1Line itemQtyUnitTotal 2Platform seats240$600$144,000 3Context add-on240$120$28,800 4Premium support1$11,200$11,200 5Acme renewal total$184,000 6Scenario B (-6%)$172,960
Q4 forecast.pptxSlides
Q4 forecast
Pending: Acme renewal
InvoicesBilling
INV-1041GlobalityPaid
INV-1042Acme CorpUnsent
INV-1043VertivDraft
Acme renewalCustomer record
StageNegotiation
Amount$184,000
CloseOct 31

Activity

Priya Shah: “Any update on the invoice?” · 2 h ago

Priya Shah: “Finance needs it before Thursday.” · yesterday

Dan Ortiz updated the pricing sheet · Monday

no API needed no API needed

LarridinWork Context

Your work context

The projectAcme renewal, $184,000, closing Oct 31. Pricing scenario B is the live one.
The peoplePriya Shah, waiting on the invoice. Dan Ortiz on pricing.
What is blockedINV-1042 is unsent, and the Q4 forecast waits on it.

All of it, available to your agent

Step 1

Install and sign in

IT pushes the desktop sensor through Jamf, Intune or Kandji, or you download it. Sign in with Okta, Entra or Google.

Step 2

Choose what it observes

Org policy sets the allowed and denied apps. You opt in or out inside that boundary, see every memory, and switch context off any time.

Step 3

Connect your agent

Add the Larridin connector in Meta Muse, sign in once with your work account, and every work question is answered in context.

Set up Meta Muse

Connect Larridin to Muse.

Larridin connects to Muse as a connector. You sign in once, and Muse asks before it uses a tool for the first time.

Step 1

Open Connectors

In Muse, go to Settings, then Connectors, and choose Add custom connector. You can also ask Muse to connect Larridin.

Step 2

Sign in with your work account

Paste the Larridin URL your admin shares, then sign in with Okta, Entra or Google. Muse gets read access to your own work context only.

Step 3

Ask Muse about your work

Try "What should I focus on today?" or "What is waiting on me?" Muse answers from your projects, people and blockers.

Try asking Muse What should I focus on today?What is waiting on me from Priya?Summarize what I got done this week.

Using a different agent? See every agent Work Context supports.

Work Context · Admin policy

Org-wide · Policy level only

Single sign-onOkta · Entra · Google SSO ProvisioningCreate, update and remove access from your IdP SCIM What’s capturedGmailSlackSalesforceSpreadsheetsSlidesBillingPassword managers: deniedIncognito: always off What’s sharedPrivate to youThe employee decides. Unsure means private.

With whom

ChatGPTChatGPT dotsOpenAI clientAllowed
Meta MuseMeta MuseMeta clientAllowed
InstinctInstinctInstinct clientAllowed
ClaudeClaudeAnthropic clientAllowed
Unregistered MCP clientunknownRefused
Admins see individual contextLocked off. Admins work at the policy level only. Locked

Built for the enterprise from day one

You decide what is captured, what is shared, and with whom.

SSO, SCIM and granular privacy controls. Org policy sets the boundary, each employee chooses inside it, and admins never see an individual’s context.

Agents authenticate as registered OAuth clients, so a random MCP client cannot claim to be one of yours. Every agent on the team gets smarter, on your terms.

Enterprise ready

SOC 2Type II
SSO & SCIMOkta, Entra, Google
MDM deployJamf, Intune, Kandji
Single regionChosen at tenant setup
30 or 90 daysRaw retention, your call
Private by defaultAdmins never see individuals

Give your agent the context it needs to be your chief of staff.

Request access and we will set up Work Context with your identity provider and MDM. Your people keep the agent they already use.

Talk to us Request Access