Skip to main content
Mesa is designed for machine-driven workflows where state needs to be durable, inspectable, and reversible.

​
Typical use cases

  • Agent-generated code and content revisions
  • Sandbox and CI pipelines that need commit-level outputs
  • Long-running background agents with checkpointing
  • Multi-tenant products with one-repo-per-workspace isolation

​
Choosing repository boundaries

A practical default is one repository per logical workspace (customer, project, or environment).