Reference
Current limits
The explicit boundaries of the current Amics remote-execution contract.
Amics currently provides single-node, bounded remote command execution.
Execution limits
| Boundary | Current maximum |
|---|---|
| Files in one source snapshot | 25,000 |
| Total uncompressed snapshot content | 1 GiB |
| Retained output per run | 64 MiB |
| Command runtime | 24 hours |
| Warm reuse window | 24 hours |
| Attached disk per machine | 10,000 GB; default 50 GB |
The CLI performs additional checks before upload. The service limit is the effective limit whenever it is stricter. Use external storage for datasets and large artifacts instead of including them in every source snapshot.
It does not provide:
- a locally attached CUDA device;
- an SSH session or remote desktop;
- a live filesystem mount;
- automatic remote-to-local artifact synchronization;
- multi-node command execution through
amics run; - guaranteed uninterrupted Spot capacity;
- automatic replay after an ambiguous outcome;
- implicit forwarding of local credentials;
- implicit persistent storage;
- a production MCP server.
Use external storage for data that must outlive compute. Download or upload artifacts explicitly when they must move between the local tree and the remote environment.
These boundaries are deliberate. They keep the command, spend, data lifecycle, and replay decision visible to both people and agents.