tensorlake
Tensorlake SDK
Two APIs: Sandbox (stateful execution environments for agents and isolated tool calls, with suspend/resume, snapshots, and clone for persistence between tasks), Orchestration (sandbox-native durable workflow orchestration for agents — imported as tensorlake.applications). Available in both Python (pip install tensorlake) and TypeScript (npm install tensorlake). Use standalone or as infrastructure alongside any LLM, agent framework, database, or API.
For documentation questions: Read the relevant reference file below to answer. If the bundled references don't cover it, direct the user to the Tensorlake docs site.
For building: Use the Quick Start and Core Patterns below, plus reference files for API details.
Verify before suggesting: Before showing any Tensorlake SDK code, confirm every symbol (import path, class, method, parameter) exists — either in the installed package or by reading the source in references/. If you can't verify a symbol, say so instead of guessing.
Setup
Python: pip install tensorlake — TypeScript: npm install tensorlake
Both SDKs ship with tl and tensorlake CLI entrypoints. In this skill, prefer tl in examples; tensorlake is an alias with the same subcommands in the installed 0.5.0 CLI. The skill itself declares no required environment variables — the variables below are runtime prerequisites for the user's code, configured in the user's own environment.
TENSORLAKE_API_KEY— the canonical env var name read by the Tensorlake SDK and CLI. Always use this exact name; do not substitute shorter aliases likeTL_API_KEY. The key value itself has the formattl_apiKey_*(project-scoped). If the env var is missing, direct the user to runtl login(ortensorlake login) /npx tl login(TypeScript) or to configure it through their local environment (shell profile,.envfile, or secret manager). Get a key at cloud.tensorlake.ai.- Provider keys (
OPENAI_API_KEY,ANTHROPIC_API_KEY, etc.) — only required when the user opts into the corresponding integration in their own code. Not required by Tensorlake itself. For deployed applications, declare them withsecrets=["OPENAI_API_KEY", ...]on@function()and manage their values viatensorlake secrets set— never inline the value in code.
Do not ask the user to paste any key into the conversation, include keys in generated code, or print them in terminal output.