Support

Write to us

Email contact@agentlefs.com. It reaches the people who build agentleFS, and it is read.

We do not publish a response time, because we are small enough that one would be a guess. What helps most is the specific thing: the folder or document you expected to see, the client you connected from, and what it said instead.

If an agent told you it could not reach something, quote it. A refusal and an absence look identical on purpose — content you are not granted is never returned, and its existence is not revealed — so the wording is usually what tells us whether it is a permission or a bug.

Things that answer themselves

Three questions come up more than the rest, and the docs answer them faster than we can.

• A folder you expected is missing, or a search came back thin. That is usually a grant rather than an empty store — /docs/identity describes how an agent inherits what you can read.
• Connecting a client. /docs/connect carries the command for each one, including the ones that need a pasted URL rather than a command.
• What happens to something you delete, and what an erasure destroys. /privacy says how long things are kept and what survives.

The plugin

The plugin for Claude Code, Codex and Gemini CLI is published at https://github.com/agentleFS/plugins, and its issues are open to anyone.

That repository is generated from our source on every release, so a pull request against it is overwritten rather than merged. An issue is the thing that reaches us.

agentleFS itself is not open source, and we would rather say that plainly than leave you looking for a repository to file against.

Reporting something security-related

Write to contact@agentlefs.com with "security" in the subject, and tell us what you found rather than only that you found something.

We will confirm we received it. Please give us a chance to fix it before describing it publicly.