StackMap
Subscribe

computer vs mirage

Virtual filesystem for agents inside a Cloudflare Durable Object — SQLite-authoritative state with pluggable execution: FUSE-mounted containers, isolate shell (just-bash) or isolate JavaScript. — versus — Unified virtual filesystem for AI agents — mounts S3, Slack, Gmail, Postgres and ~50 backends as one tree so any bash-speaking LLM can grep and pipe across services. Snapshotable, embeddable.

The curated verdict

Both hand agents a virtual filesystem: mirage federates ~50 external backends into one read tree; computer owns authoritative state and adds execution surfaces on top.

computermirage
Stars5.7k3.4k
Forks286249
LanguageTypeScriptTypeScript
LicenseMITApache-2.0
Last activity2 days ago3 days ago
Topicsagentsagents, coding
Curated connections34

computer — the curator's take

The interesting inversion: the filesystem is the durable object and execution surfaces attach to IT — container, isolate shell and isolate JS all project the same authoritative SQLite state, so agent state survives any runtime. When NOT: PREVIEW ONLY by its own banner — APIs unstable, explicitly not for production, and the spec docs describe intent, not the code; it's also Cloudflare-shaped through and through — no Workers, no computer.

mirage — the curator's take

One interface instead of N SDKs and M MCP servers: mount S3, Slack, Gmail, GitHub, Postgres, Redis (~50 backends) side-by-side as one filesystem, and any LLM that already knows bash can cat, grep and pipe across all of them with zero new tool vocabulary — plus per-resource command overrides (cat a Parquet as JSON rows), snapshotable/portable workspaces, and in-process Python/TS SDKs with OpenAI Agents/LangChain/Pydantic AI adapters and a CLI+daemon for Claude Code/Codex. Reach for it when your agent touches many external systems and tool-schema sprawl is eating your context window. NOT for a single data source (just use its SDK), heavy binary/streaming workloads, or Windows — FUSE mounts need macOS/Linux.