Text version of the 16 slides. Status labels: shipped means verified in the current product; in development means code exists but is not released or proven; planned means designed but not built; hypothesis means an assumption not yet tested; historical means true once and no longer current.
Inkfold
Inkfold
Project memory for artificial-intelligence coding tools, built on the FusionLayer engine, in a focused private beta with volunteer testers.
The one-minute version
Inkfold keeps a project's decisions in one place and hands them to each artificial-intelligence coding tool.
A focused private beta with volunteer testers. Nothing is charged yet and there are no paying customers. The hand-off between coding tools is in development.
The problem
Who has the problem and how they cope
Three groups, in order. The pain is Inkfold's hypothesis; no interview has confirmed it yet.
| Group | The pain and how they cope today | Status |
|---|---|---|
| Developers who use two or more coding tools on one project | They re-explain decisions when they switch tools or start a session, and cope by copy and paste or hand-written project files | hypothesis |
| Small teams | A decision made once should reach the next teammate's session; today each person re-teaches their own tool | hypothesis |
| People who pay for several artificial-intelligence chat products | Each product remembers separately, so the same context is repeated across them | hypothesis |
| Common to all three | Other options: one tool's own memory, or a separate memory tool that keeps context in its own store | hypothesis |
The product today
What works and what is in development
Shipped means verified in the current code. Invited testers use the web application today.
| Capability | Status | Evidence date |
|---|---|---|
| Chat in the web application with the person's own model keys | shipped | 24 September 2026 |
| Import of past chats from five assistants, or pasted text | shipped | 24 September 2026 |
| Receipt under each answer of the memories it used | shipped | 24 September 2026 |
| Memory Center: library, revisions and review inbox | shipped | 6 September 2026 |
| Data export and account deletion in Settings | shipped | 22 September 2026 |
| One-click correction of a remembered decision | in development | 15 September 2026 |
| Memory home screen and import of a repository's decisions | in development | 22 September 2026 |
| Team workspaces and shared memory (beta) | in development | 22 September 2026 |
| Native iPhone and Android apps | planned | 22 September 2026 |
How it works
From a decision to the next tool
Each step has its own status. Import and the receipt work today.
- Import shipped Past chats or pasted text, so memory does not start empty.
- Capture in development A local program reads supported tool files; each decision keeps its source, date and revision.
- Receipt shipped A line under each answer shows which remembered decisions were used.
- Correct and hand on in development The person marks a memory wrong or outdated; in Smart mode a brief is written into the next tool's files.
Storage modes
Three modes, chosen per conversation
Each row names its mode. All three modes are free on every indicative plan.
| Mode | What is stored and who can read it | Status |
|---|---|---|
| Smart (default) | Stored on Inkfold servers, encrypted at rest with a key Inkfold holds. Inkfold can read and index it. | shipped |
| Private | Encrypted in the browser with a key from a phrase only the person knows; only encrypted content is stored. A request's text passes through the servers in memory. | shipped |
| Incognito | Nothing from the conversation is stored after it ends. | shipped |
| Any mode, remote model | The text needed for that request goes to the model provider the person chose. | shipped |
| Independent assessment | No independent security assessment of the whole product has been done yet. | planned |
Tool coverage
Which tools work on which systems
In development means a preview, not verified on a clean machine. Prompt rewriting works only in the web application.
| Tool | Capture, Windows | Capture, macOS and Linux | Recall | Injection |
|---|---|---|---|---|
| Claude Code | in development | in development | in development | in development |
| Codex command-line tool | in development | in development | in development | in development |
| Gemini command-line tool | in development | in development | in development | in development |
| Cursor | in development | in development | in development | in development |
| Copilot in Visual Studio Code | planned | planned | in development | in development |
| JetBrains editors | in development | in development | in development | in development |
| Zed | Not available | in development | in development | in development |
| Google Antigravity | planned | planned | Not available | Not available |
Inkfold Desktop
The desktop client, an early tester build
Identity and the shell exist. Vaults, device sync and file sharing are not built yet.
| Capability | Status | Note |
|---|---|---|
| Windows installer for invited testers, version 0.1.0 | in development | Unsigned; Windows warns first |
| Anonymous identity with a 24-word recovery phrase | shipped | Keys in secure system storage |
| Tray controls, permission guidance, open at sign-in | in development | In progress |
| On-device encrypted index: 'Ask about these files' | in development | Local only; no model call |
| Personal vault, two-device sync, relay fallback | planned | Not built |
| File shares and team vaults with expiry | planned | Not built |
| macOS and Linux versions | planned | No build yet |
Status labels: shipped means verified in the current product; in development means code exists but is not released or proven; planned means designed but not built; hypothesis means an assumption not yet tested; historical means true once and no longer current.
Pricing
Indicative plans; nothing is charged yet
Pricing is in validation. Prices as shown on inkfold.app, 24 September 2026.
| Plan | Indicative price | What the site lists | Status |
|---|---|---|---|
| Free | $0 | 90-day history, 2 devices, your own model keys | hypothesis |
| Pro | $19 a month or $190 a year | Unlimited history and devices, own storage bucket, cost reports | hypothesis |
| Team | $32 per seat a month | Shared memory (beta), admin console, activity log | hypothesis |
| Founding member | $190 a year, first 20 people | Pro features, price locked while subscribed | hypothesis |
| Managed messages and credits | Credits at cost plus a small margin | Listed on the site; bring your own key is the beta path | planned |
Competition
Alternatives people use today
Vendor-published or third-party descriptions, September 2026; not tested by Inkfold.
| Option | What it offers |
|---|---|
| Hand-written project files | AGENTS.md, CLAUDE.md or Cursor rules; read by most coding tools, kept current by hand |
| Claude Code's own memory | Automatic memory for one tool and one project |
| Supermemory | Cross-tool memory, often over the Model Context Protocol |
| Pieces for Developers | Long-term memory across applications |
| Mem0, ByteRover Cipher | Open-source memory layers; team sharing for coding agents |
| Zep, Letta, Augment Context Services | Memory and context services for agents and coding tools |
| Inkfold (hypothesis) | Decisions kept with their sources, written into files the tools already read, under one privacy policy |
Differentiation
Where Inkfold aims to differ
Inkfold's view, not yet measured. No side-by-side comparison has been published.
hypothesis Delivery into real tools
Keeping memory is common. Delivering it reliably into each coding tool's own files is the slower work Inkfold focuses on.
hypothesis Sources and corrections
Each memory keeps its source, date and revisions. One-click correction, in development, lets the person mark it wrong or outdated.
hypothesis Files the person keeps
In Smart mode, briefs go into project files the person owns, so leaving Inkfold leaves the files behind. Switching cost stays low.
hypothesis Privacy on every plan
Smart, Private and Incognito modes are free on every plan, including Free. Whether others find this hard to match is untested.
The private beta
How the beta works
Invite-only, with unpaid volunteer testers. Nothing is charged yet.
shipped Who takes part
Volunteer testers admitted by invitation, unpaid. Each accepts a tester agreement at first sign-in; no credit card is needed.
shipped How feedback works
An in-app reporter opens a pre-filled report in a public feedback repository, which holds no source code.
planned What is measured next
Active use, weekly return, willingness to pay and time saved. The measurement tools exist; no figures are recorded yet.
Where things stand today
Evidence so far
Nothing is charged yet and there are no paying customers.
- paying customers
- 0
- Nothing is charged yet; checkout is not open
- tester reports
- 12
- Filed 18 August to 5 September 2026; all closed
- web application tests passed
- 2,676
- Recorded on 22 September 2026
- tool pairs verified on a clean machine
- 0
- The two-tool journey is the next step
Test results show engineering quality, not demand.
What comes next
Next steps, in order
A proposed order without fixed dates. Each stage carries its own status.
in development Now
- Release the memory-first web build
- One-click correction of memories
- Team workspaces, in beta
planned Next
- Verify one two-tool journey on a clean machine
- Compare it with a shared project file
planned Opening checkout
- Founding cohort of 20 at an indicative $190 a year
- Billing tested end to end first
planned Desktop and later
- Signed Windows release of Inkfold Desktop
- Vaults and two-device sync
- One Inkfold mobile app
Glossary
Terms used in this presentation
| Term | Meaning |
|---|---|
| Model Context Protocol | An open standard that lets artificial-intelligence tools call outside tools and memory. |
| Smart, Private, Incognito | The three storage modes: readable by Inkfold, encrypted in the browser, or not kept. |
| Bring your own key | The person supplies model provider keys, so the provider bills the usage. |
| Project instruction files | Files such as AGENTS.md, CLAUDE.md and Cursor rules that coding tools read at the start of a session. |
| Memory receipt | A line under each answer showing which remembered decisions were used. |
| Local runtime | A program on the person's computer that watches supported tool files and writes briefs. |
| Clean machine | A fresh computer with nothing preinstalled, used to verify an installation end to end. |
| Shipped, in development | Shipped: verified in the current code. In development: code exists, not yet released or proven. |
| Planned, hypothesis | Planned: designed or scheduled, not built. Hypothesis: an assumption not yet tested. |
Inkfold
Project memory for artificial-intelligence coding tools, built on the FusionLayer engine.
A focused private beta with invited volunteer testers: inkfold.app
Facts as of 24 September 2026. Status labels: shipped, in development, planned, hypothesis.