Mirage

this is a strong example of `filesystem-as-agent-interface` competing with SDK/MCP sprawl by collapsing many tools into one high-prior fluency layer.

Original source

Imported from historical reading log.

  • Extracted main post via api.fxtwitter.com fallback and checked the linked repo strukto-ai/mirage.
  • Zecheng Zhang introduces Mirage, a unified virtual filesystem for AI agents that mounts heterogeneous systems like S3, Drive, Slack, Gmail, GitHub, Linear, Notion, databases, and SSH into one filesystem abstraction.
  • Core pitch: agents can reuse familiar Unix/bash semantics (cat, grep, head, pipes, wc) across mixed backends and even structured formats like parquet, csv, json, h5, and wav, instead of learning service-specific APIs.
  • Repo/docs framing adds two notable pieces: portable/versioned workspaces with snapshot/clone/rollback, and a two-layer cache so repeated remote reads collapse into local lookups.
  • Why it matters: this is a strong example of filesystem-as-agent-interface competing with SDK/MCP sprawl by collapsing many tools into one high-prior fluency layer.
  • Good angle: AI infra keeps rediscovering Unix, not just for code, but as the control plane for cross-service agent work.