Skip to main content
filepacks is most useful when a workflow already produces files and you need those files to be easier to trust, review, compare, or hand off.

Common use cases

Eval snapshot pattern

When each eval run emits files, package each run immediately:
If compare exits 20, the run changed structurally and needs review.

Agent run handoff

When an agent finishes producing files:
Now the artifact can be uploaded, attached to a ticket, or handed to another reviewer without relying on the original workspace.

Human review workflow

A simple human review loop is:
  1. inspect to confirm the artifact identity and scale.
  2. verify before trusting the artifact.
  3. compare against the previous accepted artifact.
  4. Review the reported changed paths in the original files or your own tooling.

What filepacks is especially good at

filepacks works best when:
  • your workflow already produces files
  • you want a deterministic artifact boundary
  • you need human-readable review plus automation-friendly exit codes
  • you want to preserve evidence locally or in CI without a hosted dependency

When it is not the right tool

filepacks is not a replacement for:
  • Git history and source review
  • a registry or artifact store
  • semantic eval scoring
  • cloud dashboards or workflow orchestration
Use Why filepacks for the conceptual framing and Agent workflows for agent-specific patterns.