setup-tangram-remote-tool
Set up Tangram as a remote tool
Sharing this model for a user, not developing it? Follow the
tooluniverse-share-computerguide; no ToolUniverse source checkout is needed. The model runs in its own Python environment, with its dependencies:~/.local/bin/uv venv --python 3.12 ~/.tooluniverse/envs/tangram curl -fsSL -o ~/.tooluniverse/envs/tangram-tooluniverse.txt https://connect.aiscientist.tools/install-requirements.txt curl -fsSL -o ~/.tooluniverse/envs/tangram-requirements.txt https://raw.githubusercontent.com/mims-harvard/ToolUniverse/main/src/tooluniverse/remote/tangram/requirements.txt ~/.local/bin/uv pip install --python ~/.tooluniverse/envs/tangram/bin/python -r ~/.tooluniverse/envs/tangram-tooluniverse.txt -r ~/.tooluniverse/envs/tangram-requirements.txt ~/.local/bin/tu remote check tangram --python ~/.tooluniverse/envs/tangram/bin/python # lists anything still missing ~/.local/bin/tu serve --allow tangram --python ~/.tooluniverse/envs/tangram/bin/python --share --detach --name "<computer name>" --service https://tooluniverse-backend.onrender.comIf the check reports a missing environment variable (a data folder, a model cache, a provider key), set it in the same shell before
tu serve; "Obtain credentials, data, and model weights" below says what each one is. The model reads only the variables it declares.The rest of this guide is for developers working from the ToolUniverse source, and for diagnosing problems with this model.
Validation status (2026-08-16): Tangram dependencies, loopback discovery, and a bounded five-epoch single-cell/spatial mapping call passed with normalized proportions across 72 spots. Public publication, cross-user isolation, production epochs, representative accuracy, broad concurrency, and recovery remain incomplete. Authenticated private Platform import and owner testing passed on 2026-08-16; public publication and independent-caller authorization/isolation remain untested.