Friday Sandbox

Workspace management and interchangeable Docker, subprocess and mock execution backends for agent tools. Backend choice determines the isolation boundary.

Distribution: friday-framework-sandbox · Import: friday_sandbox Python: 3.13.4+ · Status: alpha · License: MIT

Installation

python -m pip install "friday-framework-sandbox==0.1.0a4"

Friday distributions use the same release version; keep internal Friday dependencies aligned.

Quick start: test without executing code

import asyncio

from friday_sandbox import ExecutionResult, get_mock_sandbox

async def main() -> None:
    sandbox = get_mock_sandbox()()
    sandbox.set_response(ExecutionResult(stdout="Hello from a fixture", exit_code=0))
    result = await sandbox.execute("print('not actually executed')")
    print(result.stdout)

asyncio.run(main())

Expected output: Hello from a fixture. The mock records the request and returns the configured result; it does not execute the string or verify real isolation.

Backends and ownership

The factory helpers return classes, not connected instances. Inspect the selected backend's constructor and lifecycle before use. Workspace TTL and cleanup policies manage files; they do not create an operating-system security boundary. Subprocess execution is not container isolation. Docker isolation still depends on image, mounts, capabilities, network and daemon configuration; do not describe any backend as safe for arbitrary hostile code by default.

Development

Work from the monorepo root after the shared contributor setup. Run the focused suite:

uv run --no-sync pytest packages/friday-sandbox/tests_sandbox -q

Documentation and support

Execution tools · Sandbox design and contracts · Source · Issues · Contributing

License

MIT.