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.
Context listens from your own machine and prompts you while the call is still live. Nothing joins the meeting.
First 30 minutes free · nothing to configure · macOS and Windows
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.
Five sources, one timeline. Every card records where it came from and what it will cost you in tokens before you ever send it.
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.
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?
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.
Threads
Include
Every card has a toggle. Turn off the noisy screenshot, keep the transcript, ask again. The thread stays intact either way.
Cost
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
Conversations live inside the thread and keep their history. Start a new one against the same context whenever the question changes.
Edit
Transcripts get names wrong. Edit any card's text in place, or leave a note telling the model how to read it.
Models
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
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 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.
Objectives
Floats above your call · stays out of the recording
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.
---
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)Roles sit beside the coaching window, so you can change how it is reading the room mid-call without leaving the call.
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.
Instructions have a ceiling, so a role can't quietly eat the room your actual context needs.
Context ships with a skill for writing skills. Ask it to build one and it will interview you and write the file.
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
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
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
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
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
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
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.
$19 a month covers about six client calls. Nothing to configure, no keys to paste, and the app shows what a call cost while you are still in it.
Start here
First 30 minutes
Free, no card, every feature on. Enough for a real client call, not a demo you click through.
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.
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.
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.
Your first 30 minutes are free, which is a real client call rather than a demo. After that a plan is $19 a month for 240 minutes of live call time, about six client calls.
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.
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.
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.
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.
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.
macOS and Windows, with automatic updates on both. Context lives in the menu bar or tray and answers to global shortcuts wherever you are.
Install it before your next client call and see whether the first nudge is one you would have acted on.
First 30 minutes free · no card · nothing joins the meeting