Summary

Add TensorLake MicroVM Sandbox as a new execution environment, enabling Harbor benchmark runs to be distributed across TensorLake's cloud infrastructure with support for high concurrency, GPU access, and optional internet isolation.

Context

Harbor supports multiple sandbox environment backends (E2B, Modal, Runloop, GKE, Daytona, Apple Container) to allow agents to execute tasks in isolated compute environments. TensorLake's sandbox offering provides ubuntu:24.04-based MicroVM sandboxes with a simple SDK that fits the same lifecycle interface. Adding it as a first-class environment lets users of the TensorLake platform run benchmarks without needing to provision their own Kubernetes or cloud infrastructure.

Changes

• Added TensorLakeEnvironment class implementing the full BaseEnvironment interface: start, stop, exec, upload_file, upload_dir, download_file, download_dir, is_dir, is_file, and attach
• Added TensorLakeClientManager singleton to share a single SandboxClient across all concurrent environment instances, with automatic cleanup at program exit
• Registered TensorLakeEnvironment in EnvironmentFactory and added TENSORLAKE to the EnvironmentType enum
• Added tensorlake>=0.4.20 as a project dependency
• Added an integration test covering the full lifecycle: start → exec → file upload → file download → stop/delete

Key Implementation Details

• Sandbox creation uses create_and_connect() which polls until SandboxStatus.RUNNING before returning, preventing SANDBOX_NOT_RUNNING errors on the first exec() call
• All synchronous SDK calls are dispatched via loop.run_in_executor to avoid blocking the async event loop during concurrent benchmark runs
• Retry logic (via tenacity) is applied to sandbox creation, deletion, and file I/O operations
• force_build=True is accepted for interface parity but emits a warning — TensorLake uses a fixed ubuntu:24.04 base image; custom dependencies must be installed via exec() after start, or via a pre-built snapshot passed as snapshot_id
• _validate_definition() is overridden to a no-op since no Dockerfile is required
• attach() delegates to tl sbx ssh <id> for interactive shell access

Use Cases

export ANTHROPIC_API_KEY=<YOUR-KEY>
export TENSORLAKE_API_KEY=<YOUR-KEY>

harbor run --dataset [email protected] \
  --agent claude-code \
  --model anthropic/claude-sonnet-4-6 \
  --n-concurrent 10 \
  --env tensorlake \
  --timeout-multiplier 16.0 \
  --ae CLAUDE_CODE_MAX_OUTPUT_TOKENS=100000 \
  --debug

Testing

# Install dependencies
pip install tensorlake tenacity

# Set API key
export TENSORLAKE_API_KEY="your-api-key"

# Run the integration test (requires a live TensorLake account)
pytest tests/integration/test_tensorlake.py -v -m integration

The integration test covers:

1. Sandbox start
2. Command execution (echo round-trip)
3. File upload and remote read verification
4. File download and local content verification
5. Sandbox stop and deletion