Skip to main content
This page documents the current system limits for Mesa. These limits will evolve as we scale — if you’re hitting a limit, reach out and we can work with you.

​
Repository limits

ResourceLimit
Repository name length100 characters

​
Git push limits

ResourceLimit
Max pack size per push5 GiB
Max ref updates per push10,000
There are no per-file size limits within a Git push — the constraint is on the total pack size.

​
REST API content limits

When creating or modifying files through the REST API and SDKs, content is sent inline:
ResourceLimit
Inline data per file operation128 KB
Total inline data per API call16 MB
Max file operations per API call10,000
Max operations per streaming message500
Max streaming messages per call200
For files larger than 128 KB, use git push or the virtual filesystem.

​
Diff limits

ResourceLimit
Max blob size for diffs1 MB
Max files in a diff response3,000
Files larger than 1 MB are omitted from diff responses with an omitted marker. The full file content is still accessible via the Content API.

​
Pagination limits

EndpointDefault page sizeMax page size
List refs / bookmarks100500
List tree entries100500
Change history100500
List changes20100
List commits20100

​
Timeouts

ResourceTimeout
API request idle timeout10 minutes
VCS operation idle timeout5 minutes
Long-running Git operations (large clones, big pushes) have up to 10 minutes before the connection is closed due to inactivity.

​
Unsupported features

FeatureStatus
Git LFSNot supported — commit large files directly
Shallow clones (--depth)Not yet supported
Partial clones (--filter)Not yet supported
Git tagsNot supported — use bookmarks