A file that remembers what happened to it.
Filement is a workspace for project documents. Each file keeps the note someone wrote on it, what replaced it and what answered it. Your team reads that. So does every AI tool you connect.
Free. Sign up with an email address.
Requirements
Passkeys for every account, with a recovery flow we have not agreed on yet.
3. Recovery
Open question: email link or support call. The client has not said.
Someone writes one line.
A note is a person's own words about a file. It sits under the title, every model that touches the file reads it first, and it outranks anything a model guesses.
NotesAn answer arrives, and says so.
Drop one file on another and Filement asks what kind of link this is, and why. Four kinds. The reason is required, because it is what anyone following the link later needs.
RelationshipsA new version replaces the old one. The old one stays.
The January brief is marked superseded, with the reason beside it, and it is still there to read. Open it and it points you to the version that counts.
Work answers the version that counts.
Implementation responds to V2, not to the brief V2 replaced. A person follows the links to find what to read next. So does a model.
Filement notices what nobody linked.
A link the AI found sits in its own section, dashed, with its confidence next to it. It never passes as something a person drew. Accept it and it becomes yours. Ignore it and it stays a suggestion.
Then an agent asks, and reads the same thing.
Every workspace is an MCP server. Claude Code, Codex or Cursor searches by meaning and follows the links to what is current, the same way you would.
Connect an agentAcme is an example project. Everything in the window is illustrative.
It opens as a file manager. On purpose.
A board you arrange yourself: projects, folders, documents, laid out where you put them. Upload anything, write in the editor, drag one thing onto another. Everything else waits one click deeper.
Acme onboarding/Requirements
Search or ask⌘KAskRequirements
4 files
Note · Client-signed scope. The newest agreed version wins.
Requirements V2.md
Edited 2h ago
Kickoff deck.pptx
12 Mar · 8.4 MB
Beta screenshots.png
6 Mar · 1.2 MB
One note. Three readers.
Write the note once and draw the link once. A teammate opening the file sees them. The assistant answering about it reads them. An agent working over MCP gets the same thing, as data. Nobody writes it twice.
Opens the file and sees the note under the title, and what replaced or answered it, with the reasons.
Note · Agreed with the client on 12 March.
- supersedesRequirements.md· This is the version that counts now.
- answered byImplementation.md· Passkeys shipped behind a flag.
- Client feedback.md· Suggested. Accept or ignore.
Connect an agent. It reads what you read.
Every workspace is an MCP server. Sign in from Claude Code, Codex, Cursor or anything else that speaks MCP, pick the workspace, and the agent can search by meaning, read documents with their notes, follow links to what is current, and write back if you let it.
$ claude mcp add --transport http filement <your server URL>Your server URL is in Settings, under Agents.
- Claude Code
- Codex
- Cursor
- VS Code
- Claude
- ChatGPT
- Gemini CLI
- Windsurf
- workspace_overview · Acme · read and write
- search "passkey recovery" · 3 documents
- get_relationships Requirements.md · superseded by Requirements V2.md
- read_document Requirements V2.md · with its note
- edit_document Implementation.md · v5 · restore any time
Added the recovery flow to Implementation.md, under the section V2 asks for. The brief it replaced was left alone.
- It sees exactly what you can see, and nothing you cannot.
- A link it draws is marked as AI-suggested, never passed off as yours.
- Every edit is a version. Undo an agent's afternoon in one go.
Access, versions, undo.
- Access holds everywhere.
- Roles for the workspace, restrictions for a folder or a document. What a person cannot open, their assistant cannot read, and their agents cannot read either.
- Nothing is overwritten.
- Every document keeps every version, uploads included. Restoring an old one adds a version on top rather than rewriting what came before.
- Undo for 30 days. Then gone for good.
- Trash holds an item for 30 days. After that the file, its versions, its summaries and its search entries are deleted, and that is final.
Stop re-explaining your projects.
Put the files in, write one line on the ones that matter, and draw the links. Teammates and AI tools read all of it.
Free. Sign up with an email address.
- Note writtena person
- Answered by Client feedback.mda person
- Superseded by Requirements V2.mda person
- Implementation.md responds to V2a person
- Related to Client feedback.md · 0.82suggested by the AI
- Read over MCPan agent, read-only