Stale
The project that was green until it wasn’t.
By the time status reaches you, it’s late, filtered and polished.
For Windows and macOS
Ambient Assist AI quietly follows your meetings and your work, so you always know what’s going on. Then it offers to take things off your plate, so you get more done.
Reduced motion is on, so the orb is resting.
The problem
Status is stale the moment it’s written, answers are scattered across tools and people, and the small tasks never stop arriving. So everyone, from the CEO to the newest hire, guesses at what’s true and falls behind on what matters.
Stale
By the time status reaches you, it’s late, filtered and polished.
Busywork
Look-ups, write-ups and to-dos that crowd out the real work.
Forgotten
Said once, in passing. Remembered by only one side.
Unchecked
Someone said it shipped. Nobody checked.
Who it’s for
One assistant, three ways of knowing.
Leaders
Every project and team, updated through the day, with a chat you can ask plain questions. Lead from the record, not hope.
Managers
A live read on your team’s work, answers about anyone on it, and a heads-up when something needs you. Walk into every update already knowing the answer.
Individual contributors
Stop juggling. It keeps track of what you owe, brings the right detail at key moments and coaches you through hard conversations.
See it in a meeting
An example of what you’d see: the conversation on the left, and what Ambient Assist AI made of it on the right, while the meeting is still going.
ExampleMaya’s desktop app, in a meeting
Tue, Oct 6 · 10:14 AM
In the call
Launch planningLIVE
Live · started 10:00 AM
Nothing recorded yet — insights and chat land here as the meeting runs.
The export fix (ENG-2412) is merged but not released. Your launch page has its release on October 13.
You: send Dana the revised timeline by Friday.
Ask what a week earlier is worth to them before you commit.
10:14 AMThem S1The export fix shipped last sprint, so that one’s closed.
10:14 AMYouGreat. Then I can get Dana the new timeline by Friday.
10:15 AMThem S2Could we pull the launch in by a week?
Speakers
Them S11
You1
Them S21
Meeting NotesAuto-generated
The recap is written when the meeting ends.
Send Dana the revised timeline by Friday.
10:14 AMChecks withYour notes · your wiki · your team’s and organization’s wikis
It offers to help
The work scout looks at your recent work and your wiki, and offers to take things off your plate: the comparison, the summary, the prep. Nothing it offers runs until you say yes.
ExampleMaya’s desktop app
Thu, Oct 8 · 4:30 PM
Ambient Assist AI
MON, OCT 5
completed: Morning brief — Last week: Dana asked for a revised launch timeline by Friday, October 9. Open: three action items, the timeline first.
TUE, OCT 6
completed: Morning brief — Yesterday: the load-test plan, and a start on the revised timeline. Open: three action items, the timeline first.
offer: Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send Dana — review it on the Work tab
accepted: Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send Dana
completed: Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send Dana — The timeline is in projects/launch-timeline.md, every date cited to where it came from.
YESTERDAY
completed: Morning brief — Yesterday: launch planning, the Platform sync and a vendor call; the timeline page is drafted. Open: send Dana the revised timeline, due Friday.
offer: Prepare a one-page brief for Thursday’s launch review — review it on the Work tab
accepted: Prepare a one-page brief for Thursday’s launch review
completed: Prepare a one-page brief for Thursday’s launch review — Launch review brief. Exports: merged, releases October 13. Billing: on schedule. Payments: about a week behind, recovery planned for October 20. Pulling in: not before both land.
TODAY · SESSION
Dana’s revised launch timeline is due Friday. The page is drafted, but it hasn’t gone to her. Launch planning · Oct 6, 10:14 AM
completed: Morning brief — Yesterday: the launch-week runbook, and the third load-testing quote. Open: send Dana the revised timeline, due Friday.
offer: Put the three vendor quotes from this week’s calls side by side in a wiki page — review it on the Work tab
What did we decide about pulling the launch in?
Not to, for now. This morning’s launch review kept November 9. Pulling in waits for the export fix on October 13 and payments on October 20. [Launch review, Oct 8]
accepted: Put the three vendor quotes from this week’s calls side by side in a wiki page
completed: Put the three vendor quotes from this week’s calls side by side in a wiki page — The comparison is in projects/vendor-quotes.md, with the call each number came from.
Thursday, October 8TODAY3 activities · 2 meetings
Wednesday, October 7TODAY4 activities
Tuesday, October 6TODAY2 activities · 3 meetings
Monday, October 5TODAY4 activities
TODAY
No activity recorded on this day.
October
4 days with records.
Thursday, October 8TODAY2 notes
The launch date holds at November 9. Pulling in waits until exports ships (October 13) and payments recovers (October 20).
Finance wants the load-testing spend approved by October 16.
Tuesday, October 6TODAY3 notes
Sales would like to launch a week earlier, on November 2. Nobody committed.
The payments vendor’s sandbox slipped a week. The team plans to recover by October 20.
Two quotes are in. The third vendor calls on Wednesday.
TODAY
No notes captured on this day.
October
2 days with captures (of any kind).
Tuesday, October 6TODAY2 action items
Send Dana the revised timeline by Friday.
Check the sandbox workaround with Jill on Wednesday.
Thursday, October 8TODAY2 action items
Share the load-test results with Marcus before launch week.
Get the load-testing spend approved by October 16.
TODAY
No action items captured on this day.
October
2 days with captures (of any kind).
type: persontitle: Dana Reyesdescription: Leads Platform and owns the Q4 migration plan.
Leads Platform and owns the Q4 migration plan. Platform sync · Sep 29, 2:16 PM
type: persontitle: Lena Ortizdescription: Head of Sales.
Head of Sales. Wants self-serve plans in front of customers as early as they can go. Launch planning · Oct 6, 10:31 AM
type: projecttitle: Q4 launchdescription: Self-serve plans, launching November 9.
Self-serve plans launch November 9. The date held at the launch review. Launch review · Oct 8, 11:31 AM
type: projecttitle: Launch timelinedescription: The revised timeline for the November 9 launch, ready to send Dana.
The dates for the Q4 launch, each with where it came from, for Dana by Friday. The launch review kept November 9. Launch review · Oct 8, 11:31 AM
type: projecttitle: Payments sandboxdescription: The payments vendor’s sandbox, and the work around it.
The vendor’s sandbox slipped a week, so payments is behind. Recovery is planned for October 20. Platform sync · Oct 6, 2:22 PM
type: projecttitle: Vendor quotesdescription: This week’s three load-testing quotes, side by side.
Three quotes for the load tests on October 21 to 23. Finance wants the spend approved by October 16. Budget review · Oct 8, 3:24 PM
Minedaily19h agoRunweekly4d agoRunmonthly8d agoRunyearlyneverRun
Routinesupdated 3d ago
What happens on a regular or semi-regular basis — the same work, or the same pattern of work.
Preferencesupdated 2d ago
Style & tone, and how the user likes to work.
Approachesupdated 19h ago
Problem-solving patterns — process, tools, and how problems get thought through.
Acquired knowledge
When each insight was learned, newest first.
WED, OCT 7
Rewrote the timeline page the same day the plan changed.
TUE, OCT 6
Chose a page ready to send over a summary.
MON, OCT 5
The morning brief, then the inbox: 4 of the last 5 weekdays.
SUN, OCT 4
Wednesday mornings go to writing, three weeks running.
Offerswork the agent proposes to take off your plate — nothing runs without your accept
Put the three vendor quotes from this week’s calls side by side in a wiki page
Finance wants the load-testing spend decided by October 16.
EVIDENCE
No open offers.
Scheduled workaccepted offers and jobs you created in chat — ask “every morning at 8, summarize yesterday”
Morning briefPauseRun nowDelete
Every morning at 8, summarize yesterday and my open action items.
LAST RUN 8H AGO · COMPLETED · Yesterday: the launch-week runbook, and the third load-testing quote. Open: send Dana the revised timeline, due Friday.
Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send DanaRun nowDelete
LAST RUN 2D AGO · COMPLETED · The timeline is in projects/launch-timeline.md, every date cited to where it came from.
Prepare a one-page brief for Thursday’s launch reviewRun nowDelete
LAST RUN 25H AGO · COMPLETED · Launch review brief. Exports: merged, releases October 13. Billing: on schedule. Payments: about a week behind, recovery planned for October 20. Pulling in: not before both land.
Put the three vendor quotes from this week’s calls side by side in a wiki pageRun nowDelete
Running
LAST RUN JUST NOW · COMPLETED · The comparison is in projects/vendor-quotes.md, with the call each number came from.
The scoutScan now
Last scan: 20m ago
Recent results
The comparison is in projects/vendor-quotes.md, with the call each number came from.
Yesterday: the launch-week runbook, and the third load-testing quote. Open: send Dana the revised timeline, due Friday.
Launch review brief. Exports: merged, releases October 13. Billing: on schedule. Payments: about a week behind, recovery planned for October 20. Pulling in: not before both land.
The timeline is in projects/launch-timeline.md, every date cited to where it came from.
Launch planning
Oct 6 · 10:00 AM · 45 min
The export fix (ENG-2412) is merged but not released. Your launch page has its release on October 13.
You: send Dana the revised timeline by Friday.
Ask what a week earlier is worth to them before you commit.
Sales would like to launch a week earlier, on November 2. Nobody committed.
10:14 AMThem S1The export fix shipped last sprint, so that one’s closed.
10:14 AMYouGreat. Then I can get Dana the new timeline by Friday.
10:15 AMThem S2Could we pull the launch in by a week?
Speakers
Them S11
You1
Them S21
Meeting NotesAuto-generated
Recap
Planning went through the three workstreams for the November 9 launch. The export fix is merged and releases October 13, not last sprint. Sales asked to launch a week earlier, on November 2; nobody committed. Platform is stretched: three launches share two engineers until November 2. Maya sends Dana the revised timeline by Friday.
Send Dana the revised timeline by Friday.
10:14 AMOffers, not surprises
An offer runs only when you accept it, and every run lands in your feed.
Only what it can finish
It offers only what it can finish itself: a summary, a comparison, a page in your wiki.
For managers
When everyone’s busywork is offered up and handled, the team’s hours go to the work that matters.
Between meetings
Every person, project and decision in one place, each fact with where it came from.
ExampleMaya’s desktop app
Thu, Oct 8 · 4:30 PM
Ambient Assist AI
MON, OCT 5
completed: Morning brief — Last week: Dana asked for a revised launch timeline by Friday, October 9. Open: three action items, the timeline first.
TUE, OCT 6
completed: Morning brief — Yesterday: the load-test plan, and a start on the revised timeline. Open: three action items, the timeline first.
offer: Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send Dana — review it on the Work tab
accepted: Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send Dana
completed: Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send Dana — The timeline is in projects/launch-timeline.md, every date cited to where it came from.
YESTERDAY
completed: Morning brief — Yesterday: launch planning, the Platform sync and a vendor call; the timeline page is drafted. Open: send Dana the revised timeline, due Friday.
offer: Prepare a one-page brief for Thursday’s launch review — review it on the Work tab
accepted: Prepare a one-page brief for Thursday’s launch review
completed: Prepare a one-page brief for Thursday’s launch review — Launch review brief. Exports: merged, releases October 13. Billing: on schedule. Payments: about a week behind, recovery planned for October 20. Pulling in: not before both land.
TODAY · SESSION
Dana’s revised launch timeline is due Friday. The page is drafted, but it hasn’t gone to her. Launch planning · Oct 6, 10:14 AM
completed: Morning brief — Yesterday: the launch-week runbook, and the third load-testing quote. Open: send Dana the revised timeline, due Friday.
offer: Put the three vendor quotes from this week’s calls side by side in a wiki page — review it on the Work tab
What did we decide about pulling the launch in?
Not to, for now. This morning’s launch review kept November 9. Pulling in waits for the export fix on October 13 and payments on October 20. [Launch review, Oct 8]
accepted: Put the three vendor quotes from this week’s calls side by side in a wiki page
completed: Put the three vendor quotes from this week’s calls side by side in a wiki page — The comparison is in projects/vendor-quotes.md, with the call each number came from.
Thursday, October 8TODAY3 activities · 2 meetings
Wednesday, October 7TODAY4 activities
Tuesday, October 6TODAY2 activities · 3 meetings
Monday, October 5TODAY4 activities
TODAY
No activity recorded on this day.
October
4 days with records.
Thursday, October 8TODAY2 notes
The launch date holds at November 9. Pulling in waits until exports ships (October 13) and payments recovers (October 20).
Finance wants the load-testing spend approved by October 16.
Tuesday, October 6TODAY3 notes
Sales would like to launch a week earlier, on November 2. Nobody committed.
The payments vendor’s sandbox slipped a week. The team plans to recover by October 20.
Two quotes are in. The third vendor calls on Wednesday.
TODAY
No notes captured on this day.
October
2 days with captures (of any kind).
Tuesday, October 6TODAY2 action items
Send Dana the revised timeline by Friday.
Check the sandbox workaround with Jill on Wednesday.
Thursday, October 8TODAY2 action items
Share the load-test results with Marcus before launch week.
Get the load-testing spend approved by October 16.
TODAY
No action items captured on this day.
October
2 days with captures (of any kind).
type: persontitle: Dana Reyesdescription: Leads Platform and owns the Q4 migration plan.
Leads Platform and owns the Q4 migration plan. Platform sync · Sep 29, 2:16 PM
type: persontitle: Lena Ortizdescription: Head of Sales.
Head of Sales. Wants self-serve plans in front of customers as early as they can go. Launch planning · Oct 6, 10:31 AM
type: projecttitle: Q4 launchdescription: Self-serve plans, launching November 9.
Self-serve plans launch November 9. The date held at the launch review. Launch review · Oct 8, 11:31 AM
type: projecttitle: Launch timelinedescription: The revised timeline for the November 9 launch, ready to send Dana.
The dates for the Q4 launch, each with where it came from, for Dana by Friday. The launch review kept November 9. Launch review · Oct 8, 11:31 AM
type: projecttitle: Payments sandboxdescription: The payments vendor’s sandbox, and the work around it.
The vendor’s sandbox slipped a week, so payments is behind. Recovery is planned for October 20. Platform sync · Oct 6, 2:22 PM
type: projecttitle: Vendor quotesdescription: This week’s three load-testing quotes, side by side.
Three quotes for the load tests on October 21 to 23. Finance wants the spend approved by October 16. Budget review · Oct 8, 3:24 PM
Minedaily19h agoRunweekly4d agoRunmonthly8d agoRunyearlyneverRun
Routinesupdated 3d ago
What happens on a regular or semi-regular basis — the same work, or the same pattern of work.
Preferencesupdated 2d ago
Style & tone, and how the user likes to work.
Approachesupdated 19h ago
Problem-solving patterns — process, tools, and how problems get thought through.
Acquired knowledge
When each insight was learned, newest first.
WED, OCT 7
Rewrote the timeline page the same day the plan changed.
TUE, OCT 6
Chose a page ready to send over a summary.
MON, OCT 5
The morning brief, then the inbox: 4 of the last 5 weekdays.
SUN, OCT 4
Wednesday mornings go to writing, three weeks running.
Offerswork the agent proposes to take off your plate — nothing runs without your accept
Put the three vendor quotes from this week’s calls side by side in a wiki page
Finance wants the load-testing spend decided by October 16.
EVIDENCE
No open offers.
Scheduled workaccepted offers and jobs you created in chat — ask “every morning at 8, summarize yesterday”
Morning briefPauseRun nowDelete
Every morning at 8, summarize yesterday and my open action items.
LAST RUN 8H AGO · COMPLETED · Yesterday: the launch-week runbook, and the third load-testing quote. Open: send Dana the revised timeline, due Friday.
Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send DanaRun nowDelete
LAST RUN 2D AGO · COMPLETED · The timeline is in projects/launch-timeline.md, every date cited to where it came from.
Prepare a one-page brief for Thursday’s launch reviewRun nowDelete
LAST RUN 25H AGO · COMPLETED · Launch review brief. Exports: merged, releases October 13. Billing: on schedule. Payments: about a week behind, recovery planned for October 20. Pulling in: not before both land.
Put the three vendor quotes from this week’s calls side by side in a wiki pageRun nowDelete
Running
LAST RUN JUST NOW · COMPLETED · The comparison is in projects/vendor-quotes.md, with the call each number came from.
The scoutScan now
Last scan: 20m ago
Recent results
The comparison is in projects/vendor-quotes.md, with the call each number came from.
Yesterday: the launch-week runbook, and the third load-testing quote. Open: send Dana the revised timeline, due Friday.
Launch review brief. Exports: merged, releases October 13. Billing: on schedule. Payments: about a week behind, recovery planned for October 20. Pulling in: not before both land.
The timeline is in projects/launch-timeline.md, every date cited to where it came from.
Launch planning
Oct 6 · 10:00 AM · 45 min
The export fix (ENG-2412) is merged but not released. Your launch page has its release on October 13.
You: send Dana the revised timeline by Friday.
Ask what a week earlier is worth to them before you commit.
Sales would like to launch a week earlier, on November 2. Nobody committed.
10:14 AMThem S1The export fix shipped last sprint, so that one’s closed.
10:14 AMYouGreat. Then I can get Dana the new timeline by Friday.
10:15 AMThem S2Could we pull the launch in by a week?
Speakers
Them S11
You1
Them S21
Meeting NotesAuto-generated
Recap
Planning went through the three workstreams for the November 9 launch. The export fix is merged and releases October 13, not last sprint. Sales asked to launch a week earlier, on November 2; nobody committed. Platform is stretched: three launches share two engineers until November 2. Maya sends Dana the revised timeline by Friday.
Send Dana the revised timeline by Friday.
10:14 AMNothing to write up
Notes, decisions and action items are ready when the meeting ends.
Kept current
When a date moves or a decision changes, the page catches up within hours.
Just ask
Where a project stands, who owns what, what was decided: ask, and get a straight answer from the record.
Why Ambient Assist AI
We’ve given the confident status update that turned out wrong, and left the meeting unsure who owned what. We built Ambient Assist AI so knowing is the default, at every level of the work.
Quiet by default
It speaks up only when it matters, and stays out of the way the rest of the time.
Checked against the record
Your notes, your wiki and the wikis your team shares.
Shows its work
Each fact in its wiki cites the moment it came from.
Your organization’s AI
Anthropic, OpenAI, OpenRouter, an OpenAI-compatible service or an Ollama endpoint. Your admin chooses.
[Quote from a manager about knowing where the team stood.]
[Quote from an individual contributor about not juggling it all anymore.]
How it works
Your organization signs an agreement. An admin chooses its AI and what’s on, from one dashboard.
Each person is invited, installs the desktop app on Windows or macOS and joins your organization.
It stays quiet, flags what doesn’t match the record, offers to help and answers when you ask.
Everyone signs in with your organization, set up from one dashboard.
Our promises
Being trusted at work comes with promises. These are ours.
Work it offers waits for the person to accept it, and every run lands in their feed.
Each fact in the wiki and each heads-up links to the moment it came from. Ask about a person, and the answer is built to cite the records it read.
No feature ranks or scores people, and the assistant that answers about someone is told never to compare them.
Your organization chooses for everyone, from one admin dashboard.
Emails, phone numbers, amounts and secrets it recognizes in transcripts and desktop activity are masked before the AI reads them.
Your organization brings its own AI keys.
How it works, in detail: see the FAQ, or book a call and we’ll walk you through it.
The short version
Every day, you make decisions about work you can’t fully see. Status goes stale, answers scatter and promises slip, so you fill the gaps with guesses and hope they hold. Ambient Assist AI replaces the guesswork with a record you can check. It follows your meetings and your work as they happen, flags what doesn’t match the record and keeps track of decisions and commitments. Ask it anything and get a straight answer. When it spots work it can take off your plate, it offers, and nothing it offers runs until you say yes. Whether you lead the company, run a team or do the work, you’ll know where things stand and get more done. Book a call, and stop guessing.
Choose your plan
Pricing is set with you, on a call.
Team
For managers who want a live read on their team.
Organization
For leaders who want to see the whole company.
FAQ
What it uses, who decides, and how it’s protected.
No. Nothing joins the call, and nobody else gets an invite.
Not for transcription. Speech is transcribed on the computer, short audio buffers are discarded, and the transcript goes to your organization’s cloud service. If meeting recording is on, the recording is uploaded there too, and it can include screen video.
No. Where it’s enabled, input rhythm shows activity such as typing or mouse use. It doesn’t capture a stream of individual keys or identify what a click lands on.
Only where your organization switches it on. Then it reads text from the apps your organization lists, or from every open app if it chooses that, which can include background windows and unsent drafts, and plain text from the clipboard. The images used to read the screen aren’t kept. Apps marked private are left out of screen reading. On Windows and on a Mac, system audio pauses while one plays sound, and the microphone pauses while one uses a microphone or plays sound through speakers. A microphone can still hear people nearby. These filters reduce what’s captured, but they don’t guarantee that every sensitive item or nearby conversation is left out.
Emails, phone numbers, amounts, card and Social Security numbers, passwords and keys it recognizes are replaced with placeholders in transcripts and desktop activity before a model reads them. This is reversible protection, not anonymization: names, topics and the substance of the work aren’t masked, and a value it doesn’t recognize, such as a password with no label, can get through. A message typed to the assistant can go to the model as typed. Recordings, meeting names, recaps, work records and intelligence aren’t covered.
The one your organization chooses, with its own credentials: Anthropic, OpenAI, OpenRouter, a public HTTPS OpenAI-compatible service, or a suitable Ollama endpoint.
Your organization’s administrators do, for everyone, from one admin dashboard. They can let a person change a mute setting, or hold it under the organization’s policy.
Each person sees their own. Managers and leaders get answers and insight about the people they lead. Your organization’s admins can see each person’s record. Team and organization wikis draw on members’ work notes and wikis, and their members can read them. Individual heads-ups can go to team leads.
Transcripts, the desktop activity your organization enables and any meeting recordings go to its cloud service. Requests to the AI come from that service.
Many places, and most companies, require everyone’s consent. Ask first. Ambient Assist AI doesn’t announce itself to people on a call, so your organization and its people must give any notice and get any permission that applies.
We’ll walk you through how it works on a call.
Book a call, and we’ll walk you through it.
Windows 10 (22H2) and 11, 64-bit · macOS 14 or later, Intel or Apple silicon