Extend the data accessible to an agent during a session by mounting resources. Resources are managed independently and can be reused across multiple sessions.
Mounting Resources
Mounting resources is the only context-related capability that operates independently of session management. Once created via the console or API, resources can be mounted to one or more sessions — their lifecycle is decoupled from that of any session.
| Resource Type | Description |
|---|---|
| File Upload and Mount | Files uploaded to the platform; when mounted, they appear as copies at a specified path inside the session sandbox. Individual files must not exceed 10 MB. |
Relationship Between Resources and Sessions
When Resources Are Mounted
- At Session Creation: Specify a list of resources and their mount paths in the
resourcesfield. - At Runtime: Append additional resources using a POST request to
/sessions/{session_id}/resources. Changes take effect immediately without requiring a session restart.
Path Conventions
All mounted resources are placed under the prefix /mnt/session/uploads. You may reference the full path directly in the system prompt, enabling the agent to access the resource via tools.
Session Isolation
When a resource is mounted, the platform internally copies it into the session’s sandbox. Modifications made within a session do not affect the original resource or other sessions that have mounted the same resource. Upon unmounting, the copy inside the session is cleaned up, leaving the original resource unchanged.
Next Steps
- File Upload and Mount: Upload files and mount them into sessions.
- Initiate a Session: Specify mounted resources when creating a session.
- Define an Agent: Configure the system prompt and tools.