---
title: "Filesystem agent showcase"
description: "Projects that lean on the filesystem paradigm to organize agent context, skills, and backends."
updatedDate: "15 Jul 2026"
source: "/showcase.md"
---

These projects are not FILESYSTEM.md-certified products. They are useful references for filesystem-first agent design: durable context, skills as files, and storage backends that speak `ls` / `cat` / `write` semantics. Map their patterns onto the ANF contract (`FILESYSTEM.md` + `AGENTS.md` + memory/skills/logs) rather than copying any one vendor layout.

## OpenViking

**ByteDance open-source context OS for agents**

Filesystem-first memory: contexts are files, not loose text chunks. Layered loading trims tokens while memories stay traceable.

- Unified place for skills, resources, and memory
- On-demand layers keep context lean
- Retrieval is visualized end-to-end

**FILESYSTEM.md alignment:** clear context layering and explicit file-backed memory map directly to deterministic loading and auditability principles.

[View project →](https://github.com/volcengine/OpenViking)

---

## AGFS (Aggregated File System)

**Aggregated File System — Everything is a file, in RESTful APIs**

Unifies queues, databases, storage, and KV as file paths so agents just read and write.

**Examples:**

- `redis.set("key", "value")` → `echo "value" > /kvfs/keys/mykey`
- `sqs.send_message(queue, msg)` → `echo "msg" > /queuefs/q/enqueue`
- `s3.put_object(bucket, key, data)` → `cp file /s3fs/bucket/key`

**Benefits:**

- Native mental model for LLMs: ls, cat, echo
- Single interface reduces coordination overhead
- Pipes and redirects keep composition and debugging simple

**FILESYSTEM.md alignment:** demonstrates "filesystem as API" at system scale by mapping service operations to paths and file operations.

[View project →](https://github.com/c4pt0r/agfs)

---

## AgentFS

**SQLite-backed filesystem purpose-built for agent state**

Stores every tool call and file operation in SQLite while exposing the filesystem over FUSE (Linux) or NFS (macOS), plus SDKs for TypeScript, Python, and Rust.

- Full audit log of agent behavior lives alongside files
- CLI and mounts let agents use `ls`, `cat`, and friends without extra plumbing
- Specs and SDKs keep storage layout consistent across runtimes

**FILESYSTEM.md alignment:** strongly supports append-only traceability, deterministic structure, and interoperability across runtimes.

[View project →](https://github.com/tursodatabase/agentfs)

---

## VectorVFS

**Your Linux filesystem as a vector database**

Keeps embeddings in VFS extended attributes so files stay the source of truth—no separate index services.

- Embeddings stored as xattrs; moves and renames stay in sync
- Works with Meta Perception Encoders by default; pluggable models coming
- Search files by similarity using the existing directory layout

**FILESYSTEM.md alignment:** keeps semantic memory attached to files instead of hidden side stores, reinforcing the filesystem as the source of truth.

[View project →](https://github.com/perone/vectorvfs)

---

## FUSE is All You Need

**Giving agents access to anything via filesystems**

Jakob Emmerling (2026-01-11) on exposing domains as files via FUSE.

- Notes recent agent harnesses (Turso AgentFS, Anthropic Agent SDK, Vercel) built on shell+FS
- Shows long-context handling, scratch space, and progressive disclosure by mounting data (e.g., email) as directories
- Example: email as directories/files so agents use `ls`, `cat`, `mv`

**Takeaway:** "everything as files" gives agents a single, calm UI layer.

**FILESYSTEM.md alignment:** the article validates progressive disclosure and filesystem-native workflows as a practical default for agent systems.

[Read article →](https://jakobemmerling.de/posts/fuse-is-all-you-need/)