Introduction

Filement is a workspace for project files that also keeps track of what those files mean. It looks and behaves like a file manager: projects, folders, documents, click to open. Underneath, it records the context that usually lives only in people's heads: what a document is, what it answers, what replaced it, and what else matters around it.

That context then goes wherever the work goes. A teammate opening a folder sees it. The built-in assistant uses it when it answers. AI tools such as Claude Code, Codex and Cursor can read it over MCP, under the same access rules as the people in the workspace.

Two layers, kept apart

• The files you organise. Your projects and folders stay exactly as you arranged them. The AI suggests; only you, or a tool you connected, move anything, and every such change can be undone.
• The context around them. Notes people write, relationships between documents and folders, summaries, and connections the AI suggests. All of it sits one click deeper than the file browser, so the first thing you see is always a plain file manager.

Where a person and a model both say something about a document, you can always tell which is which.

Where to go next

• New here: Getting started.
• How the pieces fit: How Filement works, then Notes and Relationships.
• Day-to-day use: the Guide pages, starting with Projects, folders and documents.
• Connecting an AI tool: Connect an agent.

Reading these docs as an agent

Every page is plain markdown, available three ways:

• add .md to any docs URL, for example /docs/getting-started.md;
• request any docs URL with the header Accept: text/markdown;
• read /llms.txt for an index of every page, or /llms-full.txt for all of them in one file.

The same files live in the docs/ folder of the repository, so what you read here and what is in the source are always identical.