ChromaFs vs Eyeball

ChromaFs is an open architectural approach (and reference implementation) built by Mintlify that replaces expensive container sandboxes for AI documentation assistants with a virtual filesystem layer over a Chroma vector database. Instead of spinning up an isolated container with a real filesystem for each conversation, ChromaFs intercepts Unix commands (grep, cat, ls, find, cd) and translates them into Chroma database queries — giving the LLM the filesystem UX it's trained on without any container overhead. The system stores the entire documentation file tree as a single gzipped JSON document in Chroma. On session init, it downloads and constructs the virtual directory table in memory in milliseconds. The results are dramatic: session creation time dropped from ~46 seconds (sandbox boot) to ~100ms, and marginal per-conversation cost dropped from ~$0.014 to essentially zero by reusing the already-indexed database. At 30,000+ conversations per day, this eliminated tens of thousands of dollars in monthly infrastructure costs. Mintlify published the full technical writeup on April 2, 2026. While ChromaFs itself is embedded in their product rather than released as a standalone library, the architecture pattern is directly reproducible for anyone building RAG-powered document assistants at scale. It's the smartest RAG optimization paper of 2026 so far.

Eyeball is an indie tool that fights AI hallucination in document analysis by embedding inline screenshots of the actual source passages alongside each AI-generated claim. When you analyze a PDF or document with Eyeball, the output is a Word doc where every statement has a highlighted screenshot of the precise text it came from — because screenshots are harder to hallucinate than quotes. The tool emerged from a simple observation: AI systems routinely fabricate citations and misquote sources, and quote-only verification still requires humans to manually hunt down the original text. Eyeball short-circuits that by attaching the visual evidence directly to each claim in the output document. Legal, compliance, and research reviewers can audit AI outputs at a glance rather than cross-referencing. Built in Python, Apache 2.0 licensed, launched as a Show HN six days ago and gaining traction. The approach is low-tech by design — no vector embeddings, no proprietary API calls — just precise text highlighting, screenshot capture, and Word document assembly. The simplicity is the point: verifiable AI outputs shouldn't require a research budget.