Dropped
The thing you said you’d do.
Promised on Tuesday, gone by Thursday.
For individual contributors
Stop juggling. Start getting things done.
Ambient Assist keeps track of what you owe, brings the right detail at key moments, coaches you through hard conversations and offers to do the busywork. You always know where you are.
Reduced motion is on, so the orb is resting.
The problem
Too much to hold. Something’s about to fall.
Meetings, messages, tickets and promises, all in the air at once. Every interruption wipes out the context you had an hour ago, and the small tasks crowd out the real work.
Caught out
The detail you didn’t have.
Missing right when it counted, with everyone looking at you.
Sideways
The conversation you weren’t ready for.
A hard moment, and no time to think it through.
Buried
The busywork that ate the day.
Busy since nine, and the real work is still waiting.
With Ambient Assist
It keeps the balls in the air, and takes a few off your hands.
Knowing
Always know where you are.
It keeps track of what you owe and what was decided, brings the right detail at key moments and coaches you through hard conversations. Lost? Just ask.
- Action items caught as they’re said
- Claims checked against your tools, during the meeting
- Quiet coaching when it counts
- A record of where you’ve been, with sources
Doing
It offers to do the busywork.
The work scout notices what needs doing and offers to do it: the comparison, the summary, the prep. Nothing runs until you say yes.
- Offers only what it can finish with your tools
- Results land in your feed
- Recurring work on a schedule you set
See it at work
In the meeting, and after it.
An example: what Ambient Assist caught during a call, and what it offered to do once the call was over.
During the meeting
ExampleMaya’s desktop app, in a meeting
Tue, Oct 6 · 10:14 AM
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. Linear 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 AMAfter the meeting
ExampleMaya’s desktop app
Tue, Oct 6 · 10:50 AM
Ambient Assist
YESTERDAY
completed: Morning brief — Last week: Dana asked for a revised launch timeline by Friday, October 9. Open: three action items, the timeline first. Today: no meetings, so time for the load-test plan.
TODAY · SESSION
completed: Morning brief — Yesterday: the load-test plan, and a start on the revised timeline. Open: three action items, the timeline first. Today: launch planning at 10, the Platform sync at 2 and a vendor call at 3:30.
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.
Tuesday, October 6TODAY1 activity · 1 meeting
10:00 AM
Launch planningMeeting · 10:00 AM – 10:45 AM
9:15 AM
ACTIVITYChecked the exports and payments tickets in Linear before planning.
Monday, October 5TODAY4 activities
3:00 PM
ACTIVITYStarted the revised timeline: the open dates, workstream by workstream.
1:30 PM
ACTIVITYReviewed two pull requests for the signup flow.
10:20 AM
ACTIVITYWrote the load-test plan for launch week.
9:10 AM
ACTIVITYCleared the inbox and answered Lena about the pricing page.
TODAY
No activity recorded on this day.
October
2 days with records.
Tuesday, October 6TODAY1 note
Sales would like to launch a week earlier, on November 2. Nobody committed.
TODAY
No notes captured on this day.
October
1 day with captures (of any kind).
Tuesday, October 6TODAY1 action item
Send Dana the revised timeline by Friday.
TODAY
No action items captured on this day.
October
1 day with captures (of any kind).
Index
person
- - Leads Platform and owns the Q4 migration plan. (person, updated Oct 1)
- - Head of Sales. (person, updated Oct 6)
project
- - The revised timeline for the November 9 launch, ready to send Dana. (project, updated Oct 6)
- - Self-serve plans, launching November 9. (project, updated Oct 6)
type: persontitle: Dana Reyesdescription: Leads Platform and owns the Q4 migration plan.
Dana Reyes
Status
Leads Platform and owns the Q4 migration plan. Platform sync · Sep 29, 2:16 PM
Facts
- Prefers a written timeline before committing to dates. Planning call · Sep 22, 10:40 AM
- Asked for the revised launch timeline by Friday, October 9. Launch review · Oct 1, 11:24 AM
type: persontitle: Lena Ortizdescription: Head of Sales.
Lena Ortiz
Status
Head of Sales. Wants self-serve plans in front of customers as early as they can go. Launch planning · Oct 6, 10:31 AM
Facts
- Asked to launch a week earlier, on November 2. Launch planning · Oct 6, 10:31 AM
type: projecttitle: Q4 launchdescription: Self-serve plans, launching November 9.
Q4 launch
Status
Self-serve plans launch November 9. Launch planning · Oct 6, 10:14 AM
Facts
- The export fix (ENG-2412) is merged and releases October 13. Launch planning · Oct 6, 10:14 AM
- Sales asked to launch a week earlier, on November 2. Nobody committed. Launch planning · Oct 6, 10:31 AM
History
- Oct 6: the export release moves to October 13.
type: projecttitle: Launch timelinedescription: The revised timeline for the November 9 launch, ready to send Dana.
Launch timeline
Status
The dates for the Q4 launch, each with where it came from, for Dana by Friday.
Milestones
- Export fix released: October 13. Launch planning · Oct 6, 10:14 AM
- Payments integration done: October 13. Platform sync · Sep 29, 2:16 PM
- Load tests: October 21 to 23. Launch review · Oct 1, 11:20 AM
- Launch: November 9. Launch planning · Oct 6, 10:04 AM
Minedaily13h agoRunweekly2d agoRunmonthly6d agoRunyearlyneverRun
Routinesupdated 13h ago
What happens on a regular or semi-regular basis — the same work, or the same pattern of work.
- Starts with the morning brief, then the inbox (consistent: 4 of the last 5 weekdays).
- Checks Linear before planning meetings (established).
- Keeps Wednesday mornings for writing (emerging).
Preferencesupdated 6d ago
Style & tone, and how the user likes to work.
- Plans as dated lists, each date with its source (established).
- Short written updates over calls (consistent).
Approachesupdated 6d ago
Problem-solving patterns — process, tools, and how problems get thought through.
- Checks a claim against the tracker before it goes into a plan (established).
- Turns a vague ask into dated milestones, then has the owner confirm them (consistent).
Acquired knowledge
When each insight was learned, newest first.
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 revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send Dana
Dana asked for the revised timeline by Friday, and today’s planning moved the export release to October 13.
EVIDENCE
- Today’s launch planning
- Last week’s launch review
- Linear, ENG-2412
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 3H AGO · COMPLETED · Yesterday: the load-test plan, and a start on the revised timeline. Open: three action items, the timeline first. Today: launch planning at 10, the Platform sync at 2 and a vendor call at 3:30.
Put the revised launch timeline in a wiki page, with the October 13 release date and its source, ready to send DanaRun nowDelete
Running
LAST RUN JUST NOW · COMPLETED · The timeline is in projects/launch-timeline.md, every date cited to where it came from.
The scoutScan now
Last scan: 3m ago
Recent results
The timeline is in projects/launch-timeline.md, every date cited to where it came from.
Yesterday: the load-test plan, and a start on the revised timeline. Open: three action items, the timeline first. Today: launch planning at 10, the Platform sync at 2 and a vendor call at 3:30.
Launch planning
Oct 6 · 10:00 AM · 45 min
The export fix (ENG-2412) is merged but not released. Linear 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
- Sales would like to launch a week earlier, on November 2. Nobody committed. 10:31 AM
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 AMLooking back
Know where you’ve been.
An example: your week, a day at a time, with what you worked on and the meetings you were in. Lost your place? Pick a day.
ExampleMaya’s desktop app
Thu, Oct 8 · 4:30 PM
Ambient Assist
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. Today: no meetings, so time for the load-test plan.
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. Today: launch planning at 10, the Platform sync at 2 and a vendor call at 3:30.
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. Today: writing in the morning, and a vendor call at 11:40.
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. Today: launch review at 11, budget review at 3.
offer: Put the three vendor quotes from this week’s calls side by side in a wiki page — review it on the Work tab
MO
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
3:40 PM
ACTIVITYPut the three load-testing quotes in one thread for finance.
3:00 PM
Budget reviewMeeting · 3:00 PM – 3:30 PM
12:30 PM
ACTIVITYUpdated the timeline page with the review’s decision: the date holds at November 9.
11:00 AM
Launch reviewMeeting · 11:00 AM – 11:45 AM
9:00 AM
ACTIVITYRehearsed the launch review with the timeline page open.
Wednesday, October 7TODAY4 activities
4:30 PM
ACTIVITYPaired with Jill on a workaround for the payments sandbox.
3:10 PM
ACTIVITYRead the launch-review brief.
11:40 AM
ACTIVITYA short call with the third load-testing vendor.
9:00 AM
ACTIVITYWrote the launch-week runbook.
Tuesday, October 6TODAY2 activities · 3 meetings
3:30 PM
Vendor callMeeting · 3:30 PM – 4:00 PM
2:00 PM
Platform syncMeeting · 2:00 PM – 2:40 PM
11:25 AM
ACTIVITYRead the drafted timeline page and fixed one owner.
10:00 AM
Launch planningMeeting · 10:00 AM – 10:45 AM
9:15 AM
ACTIVITYChecked the exports and payments tickets in Linear before planning.
Monday, October 5TODAY4 activities
3:00 PM
ACTIVITYStarted the revised timeline: the open dates, workstream by workstream.
1:30 PM
ACTIVITYReviewed two pull requests for the signup flow.
10:20 AM
ACTIVITYWrote the load-test plan for launch week.
9:10 AM
ACTIVITYCleared the inbox and answered Lena about the pricing page.
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).
Index
person
- - Leads Platform and owns the Q4 migration plan. (person, updated Oct 6)
- - Head of Sales. (person, updated Oct 8)
project
- - The revised timeline for the November 9 launch, ready to send Dana. (project, updated Oct 8)
- - The payments vendor’s sandbox, and the work around it. (project, updated Oct 7)
- - Self-serve plans, launching November 9. (project, updated Oct 8)
- - This week’s three load-testing quotes, side by side. (project, updated Oct 8)
type: persontitle: Dana Reyesdescription: Leads Platform and owns the Q4 migration plan.
Dana Reyes
Status
Leads Platform and owns the Q4 migration plan. Platform sync · Sep 29, 2:16 PM
Facts
- Prefers a written timeline before committing to dates. Planning call · Sep 22, 10:40 AM
- Asked for the revised launch timeline by Friday, October 9. Launch review · Oct 1, 11:24 AM
Open questions
- Does the migration plan move if payments slips past October 20?
type: persontitle: Lena Ortizdescription: Head of Sales.
Lena Ortiz
Status
Head of Sales. Wants self-serve plans in front of customers as early as they can go. Launch planning · Oct 6, 10:31 AM
Facts
- Asked to launch a week earlier, on November 2. Launch planning · Oct 6, 10:31 AM
- Agreed at the launch review to wait for exports and payments. Launch review · Oct 8, 11:31 AM
type: projecttitle: Q4 launchdescription: Self-serve plans, launching November 9.
Q4 launch
Status
Self-serve plans launch November 9. The date held at the launch review. Launch review · Oct 8, 11:31 AM
Facts
- The export fix (ENG-2412) is merged and releases October 13. Launch planning · Oct 6, 10:14 AM
- Payments is a week behind because the vendor’s sandbox slipped. Recovery is planned for October 20. Platform sync · Oct 6, 2:22 PM
- Sales asked to launch a week earlier, which waits for exports and payments. Launch planning · Oct 6, 10:31 AM Launch review · Oct 8, 11:31 AM
History
- Oct 8: the date is confirmed.
- Oct 6: the export release moves to October 13.
type: projecttitle: Launch timelinedescription: The revised timeline for the November 9 launch, ready to send Dana.
Launch timeline
Status
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
Milestones
- Export fix released: October 13. Launch planning · Oct 6, 10:14 AM
- Payments integration done: October 20. Platform sync · Oct 6, 2:22 PM
- Load tests: October 21 to 23. Launch review · Oct 1, 11:20 AM
- Launch: November 9. Launch review · Oct 8, 11:31 AM
type: projecttitle: Payments sandboxdescription: The payments vendor’s sandbox, and the work around it.
Payments sandbox
Status
The vendor’s sandbox slipped a week, so payments is behind. Recovery is planned for October 20. Platform sync · Oct 6, 2:22 PM
Facts
- Jill is working on a sandbox workaround with the vendor. Platform sync · Oct 6, 2:28 PM
Open questions
- What happens to the launch if the sandbox isn’t back by October 20?
type: projecttitle: Vendor quotesdescription: This week’s three load-testing quotes, side by side.
Vendor quotes
Status
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
Quotes
- Vendor A: $18,400 for three days, with a report the day after. Vendor call · Oct 6, 3:52 PM
- Vendor B: $22,000 for three days, with an engineer on call during the tests. Vendor call · Oct 6, 3:52 PM
- Vendor C: $15,900 for two days, a third day at $6,000. Note · Oct 7, 11:52 AM
Open questions
- Do two days cover the load-test plan, or does it need all three?
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.
- Starts with the morning brief, then the inbox (consistent: 4 of the last 5 weekdays).
- Checks Linear before planning meetings (established).
- Keeps Wednesday mornings for writing (emerging).
Preferencesupdated 2d ago
Style & tone, and how the user likes to work.
- Plans as dated lists, each date with its source (established).
- Short written updates over calls (consistent).
- Takes offers that finish the job, like a page ready to send, over summaries (emerging).
Approachesupdated 19h ago
Problem-solving patterns — process, tools, and how problems get thought through.
- Checks a claim against the tracker before it goes into a plan (established).
- Turns a vague ask into dated milestones, then has the owner confirm them (consistent).
- Rehearses a review with the source page open (emerging).
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
- Tuesday’s vendor call
- Wednesday’s call
- Thursday’s budget review
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. Today: launch review at 11, budget review at 3.
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. Today: launch review at 11, budget review at 3.
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. Linear 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
- Sales would like to launch a week earlier, on November 2. Nobody committed. 10:31 AM
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 AMWhy Ambient Assist
We know the juggle.
Holding twenty things in your head and feeling one about to fall. Ambient Assist keeps the balls in the air, so your head is free for the work only you can do.
Quiet by default
It speaks up only when it matters, and stays out of the way the rest of the time.
Checked against your tools
Linear, Slack, email, your code and the other tools you connect.
Shows its work
Every note it keeps cites the moment it came from.
Your choice of AI
Claude, OpenAI, OpenRouter, Ollama or a model on your own machine.
[Quote from an individual contributor about not juggling it all anymore.]
How it works
Up and running in three steps.
-
Install it and choose your AI.
Windows or macOS. Bring Claude, OpenAI, OpenRouter, Ollama or a model on your own machine.
-
Connect your tools.
Your tracker, docs, calendar and email, so it can check what’s said and finish what it offers.
-
Work as usual, and ask when you’re lost.
It stays quiet, brings the detail at key moments, offers to help and answers when you ask.
Our promises
- Every note shows its source
- No rankings or scores, ever
- Nothing runs until you say yes
- Sensitive details are masked
How it works, in detail: see the FAQ on the homepage, or book a call.
The short version
Your head is for great work.
You do the work, and the work comes with a long trail of meetings, messages and promises. Keeping it all in your head means something eventually falls. Ambient Assist keeps track for you. It catches what you owe as you say it, checks what’s said against your tools, brings the right detail when you need it and coaches you through the hard moments. When it spots busywork it can finish, it offers to do it, and nothing runs until you say yes. Get lost? Just ask. Get Ambient Assist, and stop juggling.
Stop juggling. Get things done.
Install it, choose your AI and go to your next meeting. Ambient Assist takes it from there.
Windows 10 and 11 · macOS 13 or later · Contact us for pricing