A key can hold only the actions its code calls, on every plan
POST /v2/keys takes actions, such as ["sandboxes:create", "sandboxes:exec", "sandboxes:get"]: the key acts as an agent of its own, granted a role of exactly those actions, and each must be one its maker may do where the key acts. Give a worker a key that cannot delete, and a dashboard a key that only reads. It holds its maker's limits too (spend cap, rate, allowed addresses, end), acts in every project its maker reaches (a key held to one project starts at Growth), and a key made with it holds the same actions. Deleting the key deletes its role at once and its agent with its row. Keys made by 1.0's POST /v1/keys, each with an agent of its own, now take that agent with them too, and no other key can be made to act as it. See API keys and access.
Same day.
- runtime sandboxes exec --cmd 'text' runs its text as a shell command line, and prints the command's own outputOne --cmd is now sent as text, which the API runs with bash -lc; before, it was sent as a one-item list, so the whole text was looked for…
- RUNTIME_PROJECT scopes every call, whatever the keyWith RUNTIME_PROJECT set (or project passed to the client), every SDK and the MCP bridge now send it as Runtime-Project on every call.
- Every ID has one form: its kind's prefix and 32 hex digitsMachines, processes, previews, snapshots, images, agents and sessions are now named by a prefixed ID, such as sbx_3f2a9c0d1e7b4a6f8c5d2e1…
Cut your cloud billby 74%.
7 days of Pro for $0, and no card to sign up. Billed by the second after.