Seamless for the Claude app
The tenth chat about a deal should know what the first nine decided.
Seamless gives Claude in the desktop app a record of your work that lives on your own computer. As you go, Claude saves each rule and decision as a plain file, with the date it was made and what it replaced. The next chat reads the record before it answers.
Writing code? See it with Claude Code and Codex
- Free and open source (MIT)
- Runs on your computer, no account
- Claude desktop app for Mac and Windows
- One command to remove
i. at work
The same habit at five different desks.
A chat in the Claude app beside what Seamless keeps for that piece of work. The people and projects are invented; the tools Claude calls, and what they do, are real.
Law
Picking up Harbor. The client agreed to bring the indemnity cap down to 1x fees.
session_startproject: harbor-acquisition
Harbor is loaded. The record has the cap at 2x fees, from your call with the client on Aug 28, and a rule that no cap change goes to the other side without the client’s written OK. Do you have it in writing?
Yes, their general counsel emailed this morning.
memory_writedecision · indemnity-cap-1x-fees · supersedes indemnity-cap-2x-fees
Saved. The 2x entry stays in the record, marked as replaced today. Still open on Harbor: the escrow agent’s KYC list and the disclosure schedule for the leases.
- client-ok-before-cap-changesconstraintNo change to the cap or the basket goes to the other side without the client’s written OK.
- indemnity-cap-1x-feessaved todaydecisionCap at 1x fees. The client’s general counsel confirmed by email, Oct 8.
- indemnity-cap-2x-feesreplacedCap at 2x fees, from the call with the client on Aug 28. Still readable.
- Send the client the escrow agent’s KYC listready
- Disclosure schedule for the leaseswaiting on the rent roll
Investing
Northwind’s founder wants to talk again. Where did we leave it?
session_startproject: northwind
You passed on Sept 30, with a plan to revisit once their Q1 numbers are in. The deck’s $10B market figure is marked refuted: your bottom-up count came to about $1.2B. The reference call with their largest customer never happened, so it’s still open.
Save this article about their competitor’s Series B to the deal.
capture_urlproject: northwind
Saved as a note in Northwind, with the link to the source.
- pass-revisit-after-q1decisionPass for now. Revisit when their Q1 numbers are in. Sept 30.
- market-size-10brefutedThe deck’s $10B market. A bottom-up count of reachable buyers gives about $1.2B.
- no-contact-with-current-investorsconstraintThe founder asked us not to contact their current investors directly.
- harlow-raises-a-40m-series-bsaved todaynoteThe article on their main competitor’s round, captured with its source link.
- Reference call with their largest customerready
Research
Reviewer 2 thinks the Site B effect is a batch artifact. Did we test that?
session_startproject: site-b-cohort
recallbatch effect at site B
We did. It’s marked refuted as of Oct 4: the re-run with randomized plates kept the effect. The analysis plan also fixed site as a random effect on Sept 18. I can draft the reply to Reviewer 2 from those two entries.
- site-b-batch-artifactrefutedBatch processing doesn’t explain the Site B effect. The re-run with randomized plates kept it, Oct 4.
- site-as-random-effectdecisionMixed-effects model with site as a random effect. Sept 18.
- preregistered-outcomes-onlyconstraintOnly the preregistered outcomes go in the main text.
- Reply to Reviewer 2due with the revision
Writing
Let’s draft chapter 14, where Mara reaches the coast.
session_startproject: the-salt-road
Two things from the book’s record before I start. Mara still doesn’t know her father’s name; that waits for Part Three. And since the flood moved to chapter 4, the coast road is washed out, so she takes the ridge path, which adds a day. Here’s a first draft.
- father-name-waits-for-part-threeconstraintMara doesn’t learn her father’s name until Part Three.
- flood-in-chapter-4decisionThe flood happens in chapter 4. Moved from chapter 9 on Oct 1.
- flood-in-chapter-9replacedThe flood happens in chapter 9. Still readable.
- coast-road-geographyreferenceThe coast road runs below the ridge. The ridge path adds a day.
- Fix the timeline gap between chapters 11 and 12ready
Consulting
Draft this month’s steering-committee update for Fenwick.
session_startproject: fenwick
Fenwick is sealed, so only its own record is in play here. Two of its rules apply: no competitor names in anything that leaves the building, and their legal team reviews every external deck, so I’ll mark this as a draft for review. Since last month the pilot moved to two regions, and the data-access request is still open.
- no-competitor-names-externalconstraintNo competitor names in anything that leaves the building.
- legal-reviews-external-decksconstraintFenwick’s legal team reviews every external deck before it goes out.
- pilot-in-two-regionsdecisionRun the pilot in two regions. Sept 22.
- Data-access request with Fenwick’s IT teamwaiting on Fenwick IT
An illustration. Constraints, decisions, refuted findings, references, and notes are files under ~/.seamless; open items are tasks, kept in its database and shown in the console.
ii. what changes
What a chat gets when it starts from the record.
It’s briefed before the first answer.
Name the project, or let a Claude Project’s instructions name it, and Claude loads the project’s rules and latest decisions before it replies.
Decisions keep their history.
A changed position is saved as a replacement. The old entry stays readable, marked with what replaced it and when, so “what did we agree before September 12?” has an answer.
Clients stay apart.
Make a project confidential and chats about your other work can’t read it. Make it sealed and nothing from outside gets in either. You can still see everything yourself.
Open items outlast the chat.
To-dos live in the project, in order when one waits on another, until someone closes them.
The record is a folder you can open.
Rules, decisions, and notes are plain text files on your computer. Read them in any text editor, search them, and back them up with everything else.
Your other AI tools read it too.
Claude Code, Codex, and other apps that connect to MCP servers read and write the same projects, so a decision made in a chat reaches the agent doing the work.
iii. next to Claude’s memory
Claude already remembers some things. Here’s where Seamless differs.
Claude’s apps have a memory of their own, on by default for individual plans. Claude generates it from your chats as entries grouped by topic, keeps a separate one for each Claude Project, and lets you read, edit, and delete what it holds. For a lot of people that’s enough. The two sit side by side without conflict: Claude’s memory carries the general picture of you and your work, and Seamless holds the record a matter needs.
| aspect | Claude’s memory | Seamless |
|---|---|---|
| how it’s written | Generated from your chats automatically | Written on purpose, when you or Claude decide something is worth keeping |
| what an entry is | An entry under a topic | A plain file per rule, decision, refuted idea, or note, with its kind, its date, and the conversation it came from |
| when something changes | You or Claude edit the entry | The new entry supersedes the old one, which stays readable with what replaced it and when |
| where it’s kept | With your Anthropic account | In a folder on your computer |
| where it works | Claude on the web, the desktop, and your phone | Chats in the Claude desktop app, plus Claude Code, Codex, and other MCP clients |
| starting a chat with it | Automatic | When you ask, or when a Project’s instructions say so |
| keeping work apart | Each Claude Project has its own memory | Projects you can make confidential or sealed, enforced for every tool that connects |
| open items | Not part of memory | Tasks, in order when one waits on another, that outlast the chat |
| taking it with you | Ask Claude to write it out | It’s already plain files |
| setup | On by default on Free, Pro, and Max; an owner turns it on for Team and Enterprise | One command in a terminal, then restart the app |
Use Claude’s memory alone if you work on the web or your phone as much as on the desktop, you’d rather install nothing, and automatic memory covers what you need to carry between chats.
Claude’s memory as Anthropic’s help center describes it, checked October 2026. Anthropic doesn’t offer it to organizations under HIPAA, public-sector, or custom data-retention agreements. Something out of date? Open an issue.
iv. your files
Every entry is a file on your own computer.
Seamless is a small program that runs in the background. It has no account and no cloud, sends no usage data, and only answers your own machine. This is the entry Harbor’s chat replaced today, still on disk and marked with what replaced it.
~/.seamless/memory/harbor-acquisition/indemnity-cap-2x-fees.md
---
id: 01M4D9K2QX7ZR3VWN8T5B6HJ4C
kind: decision
name: indemnity-cap-2x-fees
description: Indemnity cap at 2x fees, from the call with the client on Aug 28.
project: harbor-acquisition
created: 2026-08-28T16:12:40Z
invalid_at: 2026-10-08T09:41:05Z
superseded_by: 01M4ETQ8V2N7KD5XG1HZ3R9WMP
source_session: 01M3ZB4W7T0QH9C2X8R5D1KJNE
---
The client wants the indemnity cap at 2x fees in the first draft, with the basket at 0.5%. Any move on either needs the client’s written OK first.
- invalid_at When it was replaced. It drops out of briefings and search, and stays on disk.
- superseded_by The entry that replaced it, indemnity-cap-1x-fees. Ask Claude what changed and it can show you both.
- source_session The chat that wrote it, so a fact can always be traced to where it came from.
- the body Plain text. Edit it in any editor and Seamless picks up the change.
- Your chats still go to Anthropic. When Claude reads an entry into a conversation, that text becomes part of the chat and is handled like everything else you type, under your Claude plan’s terms. Seamless doesn’t change what Anthropic receives or keeps.
- Search stays on your machine unless you change it. Out of the box, search is keyword-only and offline. Search by meaning is optional: with an OpenAI key, the text of your entries is sent to OpenAI to be indexed; with Ollama, it stays on your computer.
- The walls are between conversations. A sealed project keeps one client’s record out of another client’s chats. It isn’t a lock: anyone who can sign in to your computer account can open the folder.
- No compliance claims. Whether this setup fits your professional obligations is a judgment for you, or for your firm.
v. set it up
About ten minutes, once.
You need the Claude desktop app for Mac or Windows, and a few minutes in the terminal. Everything after that happens in Claude.
-
1Open the terminal
Press ⌘-Space, type Terminal, and press Return.
Open the Start menu, type PowerShell, and press Enter.
-
2Paste this, then press Return
Mac
curl -fsSL https://thereisnospoon.org/install | shWindows
irm https://thereisnospoon.org/install.ps1 | iexwhat it prints, abridged (Mac)
checksum ok
warning: cosign not found -- archive verified by checksum only.
installed /Users/you/.local/bin/seamlessd, /Users/you/.local/bin/seam
…
service org.thereisnospoon.seamless (launchd)
healthz ok -- http://127.0.0.1:8081/healthz
…
chat in the Claude app -- the seamless MCP tools load after an app restart
what it prints, abridged (Windows)
checksum ok
WARNING: cosign not found -- archive verified by checksum only.
installed C:\Users\you\.local\bin\seamlessd.exe, C:\Users\you\.local\bin\seam.exe
…
service Seamless (Scheduled Task, at logon)
healthz ok -- http://127.0.0.1:8081/healthz
…
chat in the Claude app -- the seamless MCP tools load after an app restart
It checks the download against its published checksum, installs Seamless for your user only, starts it in the background, and connects the Claude app. If it also finds Claude Code or Codex, it asks which to connect; pressing Return keeps what it found.
Two lines that look like problems, and aren’t
The cosign warning means an optional signing tool isn’t installed; the download still matched its published checksum. On a Mac it may also suggest adding a folder to your PATH, which the Claude app doesn’t need. The installer is one readable script (PowerShell), if you’d like to look first.
-
3Quit Claude and open it again
Claude loads its connections when it starts. Quit it completely, not just its window, then reopen it.
-
4Start your first project
In a new chat, ask in plain words:
in a chatCreate a sealed Seamless project called Harbor acquisition, then start a Seamless session in it.When Claude first reaches for a Seamless tool, the app asks for your approval; allow it once or always. From then on, tell Claude what to keep as you work: “save that as a decision”, or “that’s a rule for this client”.
-
5Make every chat start from the record optional
A chat doesn’t load the record by itself. If you keep this work in a Claude Project, add a line to the Project’s instructions so that each chat in it starts by loading the record:
instructionsAt the start of every chat, call the Seamless session_start tool with project harbor-acquisition and read the briefing before answering. When we settle a rule or a decision, save it to Seamless, and when a decision changes, save the new one as superseding the old. -
6Read what’s been saved optional
Ask Claude what Seamless has on a project, or open the console, a private page in your browser that lists every project, entry, and open item. Run this in the terminal:
Mac
~/.local/bin/seamlessd console-openWindows, in a new PowerShell window
seamlessd console-openOr open the folder itself: in the Finder, press ⌘-Shift-G and paste
~/.seamless/memory.
fair questions
What it doesn’t do.
Short answers, including the ones that might rule it out for you. The technical setup guide has the rest.
Does it work on claude.ai or on my phone?
No. Seamless runs on your computer and connects through a setting that only the Claude desktop app reads, so Claude on the web, the phone apps, and Cowork tasks can’t reach it.
Will Claude load my project on its own?
Not in a chat. Claude Code gets a briefing automatically at the start of every session, but a chat has no such hook. Claude loads a project when you ask, or when a Claude Project’s instructions tell it to (step 5 above).
Does it read my documents or my email?
No. It keeps what you and Claude decide to write down, plus any web page you ask it to capture. Contracts and decks still belong in a Claude Project, a document system, or a folder.
Can my team share it?
It’s set up for one person on one computer. A trusted team can share one copy over a network, but there are no per-person permissions: everyone with access sees everything.
Does it work on Windows?
It should. The Windows app is wired the same way and the installer handles it, but the chat connection has only been checked end to end on a Mac so far. If you try it on Windows, tell us how it went.
Do I have to use the terminal?
Twice: once to install, and once if you remove it. Everything in between happens in Claude, and reading the files yourself is optional.
What does it cost?
Nothing. Seamless is free and open source under the MIT license, and there’s no account to create.
Try it on one matter this week.
Start one project, work in it for a few chats, then open the folder and read what Claude wrote down. If it isn’t for you, one command takes Seamless back out and leaves your files where they are.
Mac
curl -fsSL https://thereisnospoon.org/install | shWindows
irm https://thereisnospoon.org/install.ps1 | iex