Local artifact vault for coding agents

Keep the files your agents create.
Find them when they matter.

Save any file tree with provenance and hashes, search it locally, and restore the exact bytes later. file.cheap gives people, CLIs, and MCP clients one durable lifecycle on the machine that holds the evidence—no cloud account or hosted vault required.

local
source of truth
SHA-256
verified restore
stdio MCP
agent-ready tools
No account requiredLocal manifest authorityPrivate keyword searchVerified recovery
A complete artifact lifecycle

Save the work.
Recover the context.

Temporary folders, traces, screenshots, reports, and generated bundles become named, searchable stashes with an explicit path back to their original bytes.

01

Save the artifact

Copy any file or directory into the local vault. The manifest records its source, producing tool, tags, sizes, hashes, and likely secret findings.

02

Index what matters

Index readable files when you need retrieval. Keyword search stays local; semantic and hybrid modes remain explicit optional choices.

03

Find the evidence

Search across saved files and inspect provenance before restoring. Results are ranked leads, never a substitute for the complete artifact.

04

Restore and prove

Restore into a fresh directory and verify every recovered file against the hashes in its manifest before treating it as faithful evidence.

ArtifactRefV1 · local metadata handoff

Keep one artifact. Give each tool its own job.

Cairntrace and Glyphrun create evidence; file.cheap snapshots and verifies it. For artifacts associated with a Cairn run, a Chalupa report adapter can record the portable reference under that matching raw run ID. The bytes remain in the local vault.

  1. 01Cairntrace or Glyphrun

    Finish a native run pack before any snapshot is taken.

  2. 02file.cheap

    Save the completed pack, then emit its versioned local artifact reference.

  3. 03Optional Chalupa path

    For a matching Cairn run ID, its separately deployed adapter attaches the complete reference during first ingestion.

  4. 04Matching local vault

    An operator resolves and restores only where the stash exists.

people · CLI and Studio

A vault that stays understandable

Inspect manifests, browse stashes, compare a saved tree with current files, and choose exactly when an operation may write or delete.

  • Local SQLite and search indexes
  • Streaming compression and verified restore
  • Explicit retention and cleanup decisions
agents · stdio MCP

A filing system agents can operate safely

Typed tools, resources, prompts, and a version-matched operating guide let any compatible MCP client preserve and retrieve artifacts without inventing storage behavior.

  • Fifteen typed local tools
  • Queryable manifests and bounded search results
  • Safety guidance available inside the protocol