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
Know where things stand. Get more done.
Ambient Assist 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
Most work runs on guesswork and busywork.
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.
Busywork
The follow-ups that ate the afternoon.
Look-ups, write-ups and to-dos that crowd out the real work.
Forgotten
The promise nobody wrote down.
Said once, in passing. Remembered by only one side.
Unchecked
The wrong fact that became the plan.
Someone said it shipped. Nobody checked.
Who it’s for
Whatever your role, know with certainty.
One assistant, three ways of knowing.
Leaders
Know how your company is really executing.
Every project and team as the work happens, with a chat you can ask plain questions. Lead from certainty, not hope.
- Every project and team, as it happens
- Plain answers, with their sources
- Problems seen while they’re small
- More done across the company
Managers
Keep your finger on the team’s pulse.
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.
- Heads-ups while problems are small
- Updates for your boss in minutes
- Ask about anyone on your team, anytime
- A team that gets more done, without more hours
Individual contributors
Know where you are, and where you’ve been.
Stop juggling. It keeps track of what you owe, brings the right detail at key moments and coaches you through hard conversations.
- Action items caught as they’re said
- The detail you need, when you need it
- Lost? Just ask
- Offers to do the busywork for you
See it in a meeting
The wrong date gets caught before it becomes the plan.
An example of what you’d see: the conversation on the left, and what Ambient Assist 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
- TomThe export fix shipped last sprint, so that one’s closed.
- YouGreat. Then I can get Dana the new timeline by Friday.
- LenaCould we pull the launch in by a week?
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 AMChecks withLinear · Slack · email · your code · the other tools you connect
It offers to help
It doesn’t just know the work. It offers to do it.
The work scout looks at what’s happened and what’s coming, and offers to take things off your plate: the comparison, the summary, the prep. Nothing runs until you say yes.
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 AMOffers, not surprises
Nothing runs until you accept it, and every run lands in your feed.
Only what it can finish
It offers only what your connected tools can actually complete.
For managers
When everyone’s busywork is offered up and handled, the team’s hours go to the work that matters.
Between meetings
Know where you’ve been.
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
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 AMNothing to write up
Notes, decisions and action items are ready when the meeting ends.
Always current
When a date moves or a decision changes, the page changes with it.
Just ask
Where a project stands, who owns what, what was decided: ask, and get a straight answer with its source.
Why Ambient Assist
We’ve worked on guesswork too.
We’ve given the confident status update that turned out wrong, and left the meeting unsure who owned what. We built Ambient Assist 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 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 a manager about knowing where the team stood.]
[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 against what’s true.
-
Get on with your day.
It stays quiet, checks what it can, offers to help and answers when you ask.
Get Ambient Assist
For a team? Everyone signs in with your organization, set up from one dashboard.
Our promises
Promises we keep.
Being trusted at work comes with promises. These are ours.
Nothing runs without a yes.
Work it offers waits for the person to accept it, and every run lands in their feed.
Every answer has a source.
Each note, heads-up and answer links to where it came from.
No rankings, no scores.
It never ranks, scores or compares people. Not for anyone, not ever.
You decide what’s on.
At work, your organization chooses for everyone, from one admin dashboard. On your own computer, you do.
Sensitive details masked.
Emails, phone numbers, amounts and secrets are masked before the AI sees them.
Your AI keys.
Your organization brings its own AI keys and controls its data. On your own, bring yours or run a local model.
How it works, in detail: see the FAQ, or book a call and we’ll walk you through it.
The short version
Stop guessing. Get more done.
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 replaces the guesswork with knowing. It follows your meetings and your work as they happen, checks what’s said against the tools you already use and keeps a record of every decision and commitment, with its source. Ask it anything and get a straight answer. When it spots work it can take off your plate, it offers, and nothing 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. Get Ambient Assist, and stop guessing.
Choose your plan
For you, your team or your whole company.
Personal
Contact us for pricing
For one person, on Windows or macOS.
- Claim checks, action items and coaching
- Work offers and scheduled jobs
- Your own journal and wiki
- Your own AI key, or a local model
Team
Contact us for pricing
For managers who want a live read on their team.
- Everything in Personal
- Sign in with your organization
- An admin dashboard and shared settings
- AI keys your organization controls
Organization
Contact us for pricing
For leaders who want to see the whole company.
- Everything in Team
- Every project and team, as it happens
- Plain questions, answered across the company
- Every answer with its source
FAQ
Questions, answered.
What it uses, who decides, and how it’s protected.
Does a bot join our calls?
No. Nothing joins the call, and nobody else gets an invite.
Does audio leave the computer?
No. It’s transcribed on the computer itself, and the audio never leaves it.
Does it log keystrokes?
No, never.
Does it read the screen?
Only once it’s switched on: by you, or at work by your organization. Apps marked private are never read on screen. On Windows, system audio pauses while one plays sound, and the microphone while one uses a microphone or plays sound through speakers. On a Mac, their sound is left out of system audio, but the microphone still hears the room.
What about sensitive details?
Emails, phone numbers, amounts and secrets are masked before the AI sees them.
Which AI does it use?
The one you choose: Claude, OpenAI, OpenRouter, Ollama or a model on your own computer. At work, your organization chooses and holds the keys.
Who decides what’s on?
At work, your organization does, for everyone, from one admin dashboard. On a personal install, you do.
Who sees what?
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.
What leaves my computer on a personal install?
With a local model, nothing. Your notes are plain files you own.
Do we need consent to record?
Many places, and most companies, require everyone’s consent. Ask first.
More questions?
We’ll walk you through how it works on a call.
Know where things stand. Get more 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 · Book a call