Persistent agent workspaces that survive restarts

An agent's files used to last only as long as one sandbox. Close the conversation, or follow up on a finished run, and its scratch files, downloaded data, and half-written scripts were gone. Now every conversation and every execution has a persistent work folder, and agents run code the way an engineer does: with bash.

How it works

• Saved and restored. The folder is saved to storage about once a minute after changes settle, and restored when the next turn or run starts, so a crash loses at most about a minute of work. Workspaces hold up to 1 GiB, and binary files like spreadsheets and PDFs round-trip byte for byte.
• Follow-ups keep context. A follow-up on a finished agent run, or a run resuming after a question, continues with the previous files.
• Bash as the primitive. Agent workflow scripts run directly in shell, Python, or JavaScript, receive credentials as environment variables, and call platform services over HTTP.
• Faster first answers. The sandbox boots in the background while the model starts responding; only the first tool call waits.

Also shipped

• Uploaded files stay on disk with a short reference in the conversation, so a large CSV no longer overflows the model's context.
• ffmpeg, ImageMagick, and YouTube tools come preinstalled in the sandbox.