When Almanac analyzes data, converts a file, creates a visualization, or produces a document, it may run code in a private Linux sandbox belonging to the conversation.
How the sandbox works
The sandbox starts when a conversation first needs it. Conversations that don’t require code never start one.
Each conversation receives its own sandbox. Other conversations can’t access it, and it has no route to your computer.
What the sandbox contains
The sandbox can contain:
- Your uploads, provided as read-only source files.
- A working area for analysis, drafts, conversions, and created files.
- Patient context, provided read-only when the conversation is connected to a patient.
- Built-in tools for data analysis, document conversion, and visualization.
Almanac can work only within this environment. Attempts to access a path outside it are refused.
See Patients.
Network access and credentials
The sandbox can’t access your computer, local network, browser session, or credentials. Access to the open web is off by default.
You can allow access to approved package registries and code hosts when Almanac needs an additional library. See Internet access.
Credentials, keys, startup files, and file-version history remain protected regardless of your other settings. See Permissions.
Continue across turns
The sandbox pauses when a turn ends and keeps its state. Your next message can continue with the same files, installed libraries, and working directory.
Sandbox activity may contribute to usage. See Usage and billing.
Keep created files
Files Almanac creates are saved to the conversation with their version history. Move a file to your Library or download it if you need it elsewhere. See Files and documents.
If a sandbox task fails
A sandbox command may stop if it exceeds its time limit, and very long output may be shortened before Almanac reads it.
If a required library isn’t available, review the sandbox network setting in Internet access.