Pieces

Everyone has had the same twenty minutes: you know you read something relevant, you know roughly when, and you cannot find it. It was a Slack thread, or an email, or a tab you closed.

That is not a memory failure so much as a systems one. Your work is distributed across a dozen applications that each remember their own piece and none of which remember the sequence.

Pieces' answer is to sit underneath all of it and record the sequence — which is genuinely useful and requires letting software watch what you do.

Pieces: A Memory Layer For Your Desktop

• Runs in the background, forming memories every two seconds from the applications you already use.
• Capture is split explicitly — what you see and what you copy by default; what you hear and say only if you opt in.
• A chronological timeline across Gmail, Outlook, Chrome, Arc, Safari and Slack, searchable by time, topic, person or tool.
• Standups, morning briefs, meeting prep and day recaps generated from what actually happened.
• Mesh Intelligent Technologies, Inc., with a seven-day trial and a published refund policy.

What Does Capturing Every Two Seconds Mean?

Pieces states that it forms memories every two seconds from the apps you already use, running in the background to turn what already happened into what you need next.

It is worth sitting with that sentence rather than skimming it, because the capability and the cost are the same thing.

Capturing at that frequency means the record is genuinely continuous. You can ask what you were doing on a Tuesday afternoon three weeks ago and get an answer, which nothing else in your working life can provide.

It also means everything on your screen during working hours enters that record: the document you had open, the message you were reading, the search you ran, the thing you looked at that had nothing to do with work.

Neither of those is a criticism. They are the same fact viewed from two directions, and the honest framing is that this is a genuinely powerful capability with a genuinely large surface — which is why the capture split matters more than any feature.

The capability and the cost are the same fact. A continuous record is useful because it is continuous.

Captured By Default Versus Opt-In Only

Pieces divides capture into two explicit tiers: captured by default covers what you see from the focused application and what you use from copy and paste, while what you hear and say from meetings and conversations is opt-in only.

That split is well judged and it deserves credit, because the line is drawn at the place people actually care about.

Audio is categorically different from screen content. Recording a meeting captures other people who did not agree to it, which raises consent questions that screen capture of your own work does not.

Making audio opt-in while screen content is default means the default is defensible and the sensitive case requires a deliberate decision — which is the right way round, and the opposite of how many products handle it.

The screen capture default is still worth examining for your own situation. Anyone handling client confidential material, regulated data or another company's information under NDA should check whether a continuous local record is permitted before installing anything — a question that also applies to Dosu and any tool that indexes work automatically.

Standups And Recaps From Real Context

Pieces states that hours of retracing your steps become one click: standup updates, morning briefs, meeting prep and day recaps generated from your real context.

This is the clearest demonstration of why a timeline beats a search index, and it is worth understanding the difference.

Search answers where is the thing I am looking for. A timeline answers what happened, which is a different question and the one those artefacts require.

Writing a standup update means reconstructing yesterday from memory, and people reliably forget the two hours spent on something that produced no visible output. A record does not.

Meeting prep is the more valuable case. Walking into a conversation having been reminded what was agreed last time, what you promised and what has happened since is a meaningful advantage — and it is the kind of preparation almost nobody does because reconstructing it costs more than the meeting is worth.

• Check whether continuous capture is permitted before installing, not after.
• Keep audio capture off unless everyone in the meeting knows.
• Test recall on a week you remember, to calibrate what it actually finds.
• Use it for meeting prep, which is where the payoff is largest.
• Decide what happens to the record if you leave your job.

Why This Runs On Your Machine

Pieces is a desktop application — Windows 10 version 1809 or later, with all platforms available — rather than a cloud service, and that architecture is central to the proposition.

The reason is that the alternative is much harder to accept. A continuous record of your screen activity sitting on somebody else's infrastructure is a different risk category from one sitting on your own machine.

Local processing also makes the capability possible at all. Streaming everything on your screen to a server every two seconds would be expensive, slow and considerably harder to justify to an employer.

The trade is the usual one for local software: it consumes your machine's resources, its capability is bounded by your hardware, and the memory lives on one device rather than following you.

That last point is worth thinking through practically. A memory layer tied to a laptop is a memory layer you lose when the laptop is replaced, which is a question about export and continuity rather than about privacy.

That architecture puts it in the same category as other locally-run assistants rather than with hosted note tools. Products like Khoj make the same trade — capability bounded by your hardware, in exchange for material that never leaves the device — and the decision between local and hosted is usually about policy rather than preference.

Where A Memory Layer Stops Helping

Continuous capture solves a specific problem and leaves several adjacent ones untouched.

It records what you saw, not what you understood. The document was open; whether you read it, agreed with it or noticed the important paragraph is not in the record, and a timeline can mislead by implying attention that was not there.

It does not capture what happened without you. Decisions made in a meeting you missed, a conversation in a channel you do not follow, or a document you were never sent are outside the record by definition.

It does not organise. A timeline is chronological rather than structured, so it is excellent at when and much weaker at how things relate — which is what a knowledge base does and this is not.

And it is personal rather than shared. Team knowledge that everyone needs belongs somewhere everyone can reach, which is the space documentation platforms such as GitBook occupy, and no amount of individual memory substitutes for it.

Deciding Whether To Let Pieces Watch

This is a decision that deserves more than the ten seconds most software installations get, because the permission is unusually broad.

This sequence establishes whether it is permitted and whether it is useful, in that order.

1. Check your employment or client terms on continuous local capture before installing.
2. Leave audio capture off entirely until you have decided how to handle consent.
3. Run it for a fortnight, then test recall on a week you already remember.
4. Use it for meeting prep first, which is where the value is clearest.
5. Check what the record contains that you would not want it to, and whether that can be excluded.
6. Establish how the memory is exported or deleted before it becomes valuable to you.

Memory Layer Terms

The vocabulary of continuous capture, and what each term actually covers.

undefined

undefined

undefined

undefined

undefined

undefined

Pieces: Capture And Company

Should Pieces Run On Your Machine?

Let it run when

• You regularly lose time trying to find something you know you saw.
• Your work is spread across email, browsers, chat and documents.
• Meeting prep is something you would do if it were not so expensive.
• Writing standups from memory consistently misses what you actually did.
• You are comfortable with a continuous local record and permitted to keep one.

Keep it off when

• You handle client confidential or regulated material under terms that forbid it.
• Your employer has not approved continuous capture on a work machine.
• You share the device with anyone else.
• The knowledge you need is team knowledge, which belongs somewhere shared.
• Your hardware would struggle with continuous background processing.