Include
Switch cards on and off
Every card has a toggle. Turn off the noisy screenshot, keep the transcript, ask again. The thread stays intact either way.
No bot joins your call
Ask better questions. Remember every answer.
Context listens from your own machine and prompts you while the call is still live. Nothing joins the meeting.
7 days free · nothing to configure · macOS and Windows
Three calls today
You were listening. You were also typing.
Half your attention is on the notes. By the third call of the day they blur together, and the line that actually mattered is buried in a recording nobody will sit through again.
So the follow-up gets written from memory, and the next call starts from a weaker position than it needed to.
Context does the listening, so you can do the talking.
Dana: procurement capped us at 40 seats
until Q3. Can you get us a bridge?
8.3 Seat counts may be adjusted at the
start of any billing period, provided…
Dana: the blocker is the seat cap,
not the price. Budget resets in Q3.
It collects while you work, not when you remember to.
Five sources, one timeline. Every card records where it came from and what it will cost you in tokens before you ever send it.
Every copy, kept with the app it came from
Context watches the clipboard so you stop keeping a scratch document of things you might need later. Each capture records the app you copied it from.
- Text from any application, tagged with its source app
- Repeated copies are throttled, so a run of ⌘C makes one card
- Paste a YouTube link and the transcript comes with it
Lands in the thread as
Dana: we can't renew on the current tier.
Procurement capped us at 40 seats until Q3.
Can you get us a bridge?
A thread is a topic, and it owns its own context.
Cards land in the thread you have open. What you include is what the model sees. Nothing more, and nothing you have to re-explain.
Meridian renewalCapturing
Threads
- Meridian renewal6
- Q3 pricing14
- Hiring loop9
- Onboarding docs3
- 09:14ClipboardSlackprocurement capped us at 40 seats…84
- 09:16ScreenshotFigmapricing-tiers-v4.png612
- 09:22MeetingZoom · 41 minDana: the blocker is the seat cap…9,840
- 09:31Folder~/Deals/meridian3 files · MSA, seat usage, kickoff3,092
- 09:33ClipboardChromecompetitor changelog, June480
- 09:34NoteYouDana is the economic buyer.41
5 of 6 included0tokens
Draft the bridge offer Dana can actually approve.
Cost
See what it costs as you go
Every conversation shows what it cost, split by model, because transcription and the assistant do not run on the same one. Token counts sit behind that.
Chat
Ask more than once
Conversations live inside the thread and keep their history. Start a new one against the same context whenever the question changes.
Edit
Fix what the machine misheard
Transcripts get names wrong. Edit any card's text in place, or leave a note telling the model how to read it.
Models
Nothing to wire up
Context runs the models for you. No provider accounts, no keys to paste or rotate, and no second bill arriving from somewhere else at the end of the month.
Recall
Come back in three weeks
Threads don't expire and don't need re-priming. The renewal you worked on in March is still assembled in March's thread.
A second read on the call, while the call is happening.
A small window sits over your screen, follows the conversation, tracks what you set out to cover and tells you what is being missed. Your client sees a normal call, because that is all there is on their side.
- It knows which voice is yours
- Your microphone and the system audio are separate streams, so the coach can tell your talking from theirs without waiting on speaker separation.
- It corrects itself
- As the call develops, earlier suggestions get revised rather than left standing. If it decides the ops lead isn't the buyer after all, it says so.
- It watches your objectives
- Write down what the call needs to cover. Items get marked off as they're genuinely addressed, and you can edit the list mid-call.
- It tells you when to stop talking
- Talk uninterrupted for too long and you get a nudge. Afterwards you get a written summary of the call in the thread.
Live · 18:42DirectGentle
- s3Ask what happens to the seat cap when the Q3 budget resets.
- s4They named a date. Get it in writing before the call ends.
- s2Loop in the ops lead for pricing sign-off.
- revised: Dana signs, not the ops lead
Objectives
- Find the real blocker
- Confirm the decision maker
- Agree a next step with a date
Floats above your call · stays out of the recording
Tell it which job you are doing, not what to do each time.
Switch on a role and Context reads the thread the way that job reads it. Selling is not the same as scoping a feature or handling support, and the coaching should not be either.
~/Context/skills/deal-review/SKILL.md
---
name: "deal-review"
description: "Read a deal thread the way our team does."
triggers:
- "review this deal"
tokenBudget: "medium"
---
## How to read a deal thread
Lead with the blocker, not the summary. Quote the
customer verbatim when their words matter.
Score against @./qualification.md
Use the objection handling in @skill(playbook)A toggle, not a setup step
Roles sit beside the coaching window, so you can change how it is reading the room mid-call without leaving the call.
Yours to rewrite
Every role has a prompt behind it you can edit, or build a new one from scratch. Run more than one and Context tells the model which takes precedence.
Budgeted like everything else
Instructions have a ceiling, so a role can't quietly eat the room your actual context needs.
Written in the app
Context ships with a skill for writing skills. Ask it to build one and it will interview you and write the file.
An app that watches your screen should be easy to check on.
Your threads stay on your machine. What has to leave it leaves only when you act, and we are specific about which parts those are.
Storage
Your threads stay on your machine
Cards, screenshots, transcripts and chat history are written to a local database and local files in your user folder. We do not hold a copy of your threads and cannot read them.
Account
An account, for metering and nothing else
You sign in so usage can be counted against your plan. The account carries your usage and billing details. It does not carry your threads.
Models
No API keys to manage
Context runs the transcription and the assistant for you, so there are no provider accounts to open and no keys to paste, rotate or keep safe.
Processing
What leaves, and only when you act
Recorded audio goes out to be transcribed, and the cards you left switched on go out when you send a message. Nothing you capture is used to train models.
Consent
Recording is always deliberate
Nothing records silently. You start a recording yourself, and the app shows while it is running. Whether you may record a given conversation is yours to decide.
Backups
Backups you can open yourself
Export a thread archive as a .ctxbackup zip. Turn on daily backups, and point them at a folder you already sync, or at a hidden Google Drive folder only the app can read.
Priced by the call, because that is how the work happens.
Seven days free with no limit on how much you use it, then $19 a month for about six client calls. Nothing to configure and no keys to paste.
Start here
7 days free*
No card, every feature on, and no cap on your call time for the week. Long enough to run it across a real pipeline.
- Unlimited threads, cards and conversations
- Clipboard, screenshot, file, video and meeting capture
- Speaker separation, so it knows which side is you
- Assisted calls with live coaching and objectives
- Roles and skills you can switch on per thread
- Backups, sync folders and Google Drive
Then
$19/month
240 minutes of live call time, about six client calls. Go past it and you pay for the extra time you used.
- You are charged only while a call is being recorded
- Notes, threads and asking questions are never charged for
- What each call cost, shown while you are still in it
- Where you stand visible before the invoice, not after it
Unlimited means unlimited for real client calls. We only step in if usage looks automated or resold, and we will talk to you before we do.
Before you install it.
Does Context send everything I copy?
No. Capture and sending are separate steps. Cards accumulate locally, and each one has an include toggle. Only what is switched on in the current thread is sent, and only when you send a message.
Do I need an API key or a provider account?
No. That was how earlier versions worked and it is gone. Context runs the transcription and the assistant for you, so you install the app, sign in, and start.
How does the pricing work?
The first seven days are free with no limit on how much you use them, so you can run it across a real pipeline rather than a demo. After that a plan is $19 a month for 240 minutes of live call time, about six client calls. Unlimited during the trial means normal client calls, not automated or resold usage.
How do I know what a conversation cost?
The app shows the cost of each conversation as it runs, broken down by model, because transcription and the assistant can run on different ones. Token counts sit behind that for anyone who wants them.
Do I need everyone's consent to record?
Often, yes. Laws on recording conversations differ by country and by state, and many require consent from everyone involved. Context never records on its own, but deciding whether you may record, and asking, is your responsibility.
How is recording both sides of a call handled?
Context captures your microphone and the system output as separate streams, so the transcript knows which side each line came from, and the coach knows which side it is advising.
Does it work offline?
Capture does. Clipboard, screenshots, files and recording all work with no network. Transcription and the assistant need a connection, since that is where the models run.
Can I move my data to another machine?
Export a .ctxbackup archive and import it on the other machine, or set both machines to the same sync folder. The archive contains the database and its screenshots, thumbnails and audio.
Which platforms are supported?
macOS and Windows, with automatic updates on both. Context lives in the menu bar or tray and answers to global shortcuts wherever you are.
Your next call is the one to try it on.
Install it before your next client call and see whether the first nudge is one you would have acted on.
7 days free · no card · nothing joins the meeting