tamarind-cli 0.4.3__tar.gz → 0.5.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/.github/workflows/ci.yml +2 -2
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/PKG-INFO +16 -11
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/README.md +14 -9
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/docs/architecture.md +3 -4
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/docs/custom-tools.md +28 -30
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/openapi/public-v1.json +496 -261
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/openapi/public-v1.lock.json +2 -2
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/pyproject.toml +2 -2
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/scripts/check_custom_tools_provenance.py +21 -4
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/scripts/sync_custom_tools_contract.py +8 -8
- tamarind_cli-0.5.0/src/tamarind/attribution.py +75 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/custom_tools.py +34 -49
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/files.py +5 -73
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/jobs.py +138 -28
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/main.py +2 -1
- tamarind_cli-0.4.3/src/tamarind/custom_tools/_generated/api/custom_tools/build_custom_tool_version.py → tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/api/custom_tools/build_custom_tool.py +13 -9
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/cancel_custom_tool_build.py +37 -29
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/delete_custom_tool.py +4 -4
- tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool.py +237 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tool_build_logs.py +49 -21
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tool_versions.py +22 -0
- tamarind_cli-0.4.3/src/tamarind/custom_tools/_generated/api/custom_tools/publish_custom_tool_version.py → tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/api/custom_tools/publish_custom_tool.py +36 -25
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/__init__.py +6 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_log_page.py +24 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request.py +8 -5
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool.py +8 -9
- tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/models/public_custom_tool_detail.py +274 -0
- tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/models/public_custom_tool_detail_gputype.py +13 -0
- tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/models/public_custom_tool_detail_memory.py +16 -0
- {tamarind_cli-0.4.3/src/tamarind/pipelines → tamarind_cli-0.5.0/src/tamarind/custom_tools}/_generated/models/public_problem.py +22 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request.py +20 -11
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_version.py +20 -12
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/client.py +5 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/resources.py +63 -141
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/transport.py +61 -41
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/http.py +3 -0
- tamarind_cli-0.5.0/src/tamarind/resources.py +160 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/rest.py +41 -6
- tamarind_cli-0.5.0/src/tamarind/uploads.py +73 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_agent_contract.py +34 -8
- tamarind_cli-0.5.0/tests/test_attribution.py +58 -0
- tamarind_cli-0.5.0/tests/test_batch_prevalidate.py +275 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_cli_commands.py +5 -5
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_custom_tools_cli.py +94 -46
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_custom_tools_generation.py +21 -7
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_custom_tools_sdk.py +303 -183
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_rest.py +24 -3
- tamarind_cli-0.5.0/tests/test_sdk_resources.py +81 -0
- tamarind_cli-0.4.3/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool.py +0 -177
- tamarind_cli-0.4.3/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool_version.py +0 -195
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/.github/workflows/publish.yml +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/.gitignore +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/LICENSE +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/install.sh +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/openapi/openapi-python-client.json +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/openapi/pipelines-openapi-python-client.json +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/openapi/pipelines-v1.json +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/openapi/pipelines-v1.lock.json +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/scripts/sync_pipelines_contract.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/catalog.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/auth.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/catalog.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/guidance.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/inputs.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/cli/output.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/config.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_contract.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/create_custom_tool.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/create_custom_tool_upload.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tools.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/update_custom_tool.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/client.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/errors.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_error.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_event.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_result.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_result_action.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request_gputype.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request_memory.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_create_version_request.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_gputype.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_memory.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_page.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_status.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_problem_errors_type_0_item.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request_gpu_type_type_0.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request_memory_type_0.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_upload_session.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_upload_session_uploadheaders.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_version_page.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_version_status.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/types.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/packaging.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/validation.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/errors.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/jobs.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/pipelines_public/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/pipelines_public/get_run.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/pipelines_public/list_node_run_molecules.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/client.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/errors.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/__init__.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/node_run_status.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run_molecule.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run_molecule_page.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run_molecule_scores.py +0 -0
- {tamarind_cli-0.4.3/src/tamarind/custom_tools → tamarind_cli-0.5.0/src/tamarind/pipelines}/_generated/models/public_problem.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_problem_errors_type_0_item.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_run.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_run_inputs.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/run_status.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/source.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/types.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/resources.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/pipelines/transport.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/src/tamarind/py.typed +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_bugbash.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_config.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_custom_tools_packaging.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_errors.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_file_filters.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_inputs.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_jobs.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_output.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_pep561.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/tests/test_pipelines_sdk.py +0 -0
- {tamarind_cli-0.4.3 → tamarind_cli-0.5.0}/uv.lock +0 -0
|
@@ -10,13 +10,13 @@ permissions:
|
|
|
10
10
|
|
|
11
11
|
jobs:
|
|
12
12
|
generated:
|
|
13
|
-
name: Generated transport
|
|
13
|
+
name: Generated transport matches pinned contracts
|
|
14
14
|
runs-on: ubuntu-latest
|
|
15
15
|
timeout-minutes: 5
|
|
16
16
|
steps:
|
|
17
17
|
- uses: actions/checkout@v4
|
|
18
18
|
- uses: astral-sh/setup-uv@v5
|
|
19
|
-
- name: Verify
|
|
19
|
+
- name: Verify pinned provenance and generated client freshness
|
|
20
20
|
run: |
|
|
21
21
|
uv run --extra dev python scripts/check_custom_tools_provenance.py
|
|
22
22
|
tmp_dir=$(mktemp -d .custom-tools-generated.XXXXXX)
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: tamarind-cli
|
|
3
|
-
Version: 0.
|
|
4
|
-
Summary: Command-line interface for the Tamarind Bio platform — submit, monitor, and download protein/molecule jobs from your terminal or an AI agent.
|
|
3
|
+
Version: 0.5.0
|
|
4
|
+
Summary: Command-line interface AND Python SDK for the Tamarind Bio platform — submit, monitor, and download protein/molecule jobs from your terminal, scripts, or an AI agent.
|
|
5
5
|
Project-URL: Homepage, https://tamarind.bio
|
|
6
6
|
Project-URL: Documentation, https://app.tamarind.bio/api-docs
|
|
7
7
|
Project-URL: Source, https://github.com/Tamarind-Bio/tamarind-cli
|
|
@@ -140,7 +140,7 @@ with Tamarind() as client:
|
|
|
140
140
|
result = tool.build("./my-esmfold", idempotency_key="release-2026-08-26")
|
|
141
141
|
print(result.action) # build, reuse_image, or unchanged
|
|
142
142
|
version = result.version
|
|
143
|
-
print(version.
|
|
143
|
+
print(version.version) # numbered version, e.g. v3
|
|
144
144
|
if not version.terminal:
|
|
145
145
|
version = version.monitor(timeout=1800, on_event=print)
|
|
146
146
|
```
|
|
@@ -152,7 +152,7 @@ server returns the already admitted Version. If no key was supplied, fetch the
|
|
|
152
152
|
tool's versions before retrying. Interrupting `monitor()` stops local monitoring; it
|
|
153
153
|
does not cancel the remote build.
|
|
154
154
|
|
|
155
|
-
Exact Version operations use `version.
|
|
155
|
+
Exact Version operations use `version.version`, such as `v3`. If a
|
|
156
156
|
mutation reports `412 Precondition Failed`, refetch the affected Tool or Version,
|
|
157
157
|
confirm the mutation is still desired, and retry using the refreshed resource.
|
|
158
158
|
|
|
@@ -164,20 +164,20 @@ tamarind custom-tools create my-esmfold --display-name "My ESMFold"
|
|
|
164
164
|
tamarind custom-tools build my-esmfold ./my-esmfold \
|
|
165
165
|
--idempotency-key release-2026-08-31 --wait --timeout 1800
|
|
166
166
|
tamarind custom-tools versions my-esmfold
|
|
167
|
-
tamarind custom-tools publish my-esmfold
|
|
167
|
+
tamarind custom-tools publish my-esmfold v3
|
|
168
168
|
```
|
|
169
169
|
|
|
170
|
-
Build responses contain
|
|
171
|
-
Pass
|
|
170
|
+
Build responses contain a numbered `version`, such as `v3`.
|
|
171
|
+
Pass it to `version`, `logs`, `cancel`, and `publish`. A local wait
|
|
172
172
|
timeout does not cancel the remote build; reattach with
|
|
173
|
-
`tamarind custom-tools version NAME
|
|
173
|
+
`tamarind custom-tools version NAME VERSION --wait`.
|
|
174
174
|
|
|
175
175
|
### Test a completed Custom Tool version
|
|
176
176
|
|
|
177
177
|
After building, submit a test without publishing the version:
|
|
178
178
|
|
|
179
179
|
```bash
|
|
180
|
-
tamarind custom-tools test my-esmfold --version
|
|
180
|
+
tamarind custom-tools test my-esmfold --version v3 \
|
|
181
181
|
--input inputs.json --name esmfold-smoke
|
|
182
182
|
tamarind status esmfold-smoke
|
|
183
183
|
tamarind wait esmfold-smoke --timeout 600
|
|
@@ -190,13 +190,13 @@ from tamarind import Tamarind
|
|
|
190
190
|
|
|
191
191
|
with Tamarind() as client:
|
|
192
192
|
tool = client.custom_tools.get("my-esmfold")
|
|
193
|
-
job = tool.test({"sequence": "MKT..."}, version="
|
|
193
|
+
job = tool.test({"sequence": "MKT..."}, version="v3", name="esmfold-smoke")
|
|
194
194
|
print(job.job_name, job.id, job.status)
|
|
195
195
|
```
|
|
196
196
|
|
|
197
197
|
The command returns after submission and the run appears in the tool's website
|
|
198
198
|
Test history. This executes the tool and uses compute; it is not a dry run.
|
|
199
|
-
Omit `name` / `--name` to generate a unique name. Pass the
|
|
199
|
+
Omit `name` / `--name` to generate a unique name. Pass the version number (such as `v3`) from
|
|
200
200
|
`build` or `versions`; the SDK resolves its execution pin and protects against
|
|
201
201
|
deleting and recreating the tool. The selected build must be complete. Design
|
|
202
202
|
splitting is handled by the backend and returns the parent job receipt.
|
|
@@ -265,6 +265,11 @@ Run `tamarind <command> --help` for full options.
|
|
|
265
265
|
| Job API base | `--api-base` | `TAMARIND_API_BASE` | `https://app.tamarind.bio/api/` |
|
|
266
266
|
| Catalog base | `--catalog-base` | `TAMARIND_CATALOG_BASE` | `https://mcp.tamarind.bio` |
|
|
267
267
|
| Profile | `--profile` | `TAMARIND_PROFILE` | `default` |
|
|
268
|
+
| AI agent reported to Tamarind | — | `TAMARIND_AGENT` | detected; `none` to send none |
|
|
269
|
+
|
|
270
|
+
Every request says whether it came from the CLI or the SDK, and which AI agent (Claude Code,
|
|
271
|
+
Codex, Claude Science, ...) is running it when that can be told from the environment. Tamarind
|
|
272
|
+
uses this only to count usage by channel and platform.
|
|
268
273
|
|
|
269
274
|
Profiles (key + endpoints) are stored in `~/.tamarind/config.json`. Use a
|
|
270
275
|
profile to point at staging:
|
|
@@ -114,7 +114,7 @@ with Tamarind() as client:
|
|
|
114
114
|
result = tool.build("./my-esmfold", idempotency_key="release-2026-08-26")
|
|
115
115
|
print(result.action) # build, reuse_image, or unchanged
|
|
116
116
|
version = result.version
|
|
117
|
-
print(version.
|
|
117
|
+
print(version.version) # numbered version, e.g. v3
|
|
118
118
|
if not version.terminal:
|
|
119
119
|
version = version.monitor(timeout=1800, on_event=print)
|
|
120
120
|
```
|
|
@@ -126,7 +126,7 @@ server returns the already admitted Version. If no key was supplied, fetch the
|
|
|
126
126
|
tool's versions before retrying. Interrupting `monitor()` stops local monitoring; it
|
|
127
127
|
does not cancel the remote build.
|
|
128
128
|
|
|
129
|
-
Exact Version operations use `version.
|
|
129
|
+
Exact Version operations use `version.version`, such as `v3`. If a
|
|
130
130
|
mutation reports `412 Precondition Failed`, refetch the affected Tool or Version,
|
|
131
131
|
confirm the mutation is still desired, and retry using the refreshed resource.
|
|
132
132
|
|
|
@@ -138,20 +138,20 @@ tamarind custom-tools create my-esmfold --display-name "My ESMFold"
|
|
|
138
138
|
tamarind custom-tools build my-esmfold ./my-esmfold \
|
|
139
139
|
--idempotency-key release-2026-08-31 --wait --timeout 1800
|
|
140
140
|
tamarind custom-tools versions my-esmfold
|
|
141
|
-
tamarind custom-tools publish my-esmfold
|
|
141
|
+
tamarind custom-tools publish my-esmfold v3
|
|
142
142
|
```
|
|
143
143
|
|
|
144
|
-
Build responses contain
|
|
145
|
-
Pass
|
|
144
|
+
Build responses contain a numbered `version`, such as `v3`.
|
|
145
|
+
Pass it to `version`, `logs`, `cancel`, and `publish`. A local wait
|
|
146
146
|
timeout does not cancel the remote build; reattach with
|
|
147
|
-
`tamarind custom-tools version NAME
|
|
147
|
+
`tamarind custom-tools version NAME VERSION --wait`.
|
|
148
148
|
|
|
149
149
|
### Test a completed Custom Tool version
|
|
150
150
|
|
|
151
151
|
After building, submit a test without publishing the version:
|
|
152
152
|
|
|
153
153
|
```bash
|
|
154
|
-
tamarind custom-tools test my-esmfold --version
|
|
154
|
+
tamarind custom-tools test my-esmfold --version v3 \
|
|
155
155
|
--input inputs.json --name esmfold-smoke
|
|
156
156
|
tamarind status esmfold-smoke
|
|
157
157
|
tamarind wait esmfold-smoke --timeout 600
|
|
@@ -164,13 +164,13 @@ from tamarind import Tamarind
|
|
|
164
164
|
|
|
165
165
|
with Tamarind() as client:
|
|
166
166
|
tool = client.custom_tools.get("my-esmfold")
|
|
167
|
-
job = tool.test({"sequence": "MKT..."}, version="
|
|
167
|
+
job = tool.test({"sequence": "MKT..."}, version="v3", name="esmfold-smoke")
|
|
168
168
|
print(job.job_name, job.id, job.status)
|
|
169
169
|
```
|
|
170
170
|
|
|
171
171
|
The command returns after submission and the run appears in the tool's website
|
|
172
172
|
Test history. This executes the tool and uses compute; it is not a dry run.
|
|
173
|
-
Omit `name` / `--name` to generate a unique name. Pass the
|
|
173
|
+
Omit `name` / `--name` to generate a unique name. Pass the version number (such as `v3`) from
|
|
174
174
|
`build` or `versions`; the SDK resolves its execution pin and protects against
|
|
175
175
|
deleting and recreating the tool. The selected build must be complete. Design
|
|
176
176
|
splitting is handled by the backend and returns the parent job receipt.
|
|
@@ -239,6 +239,11 @@ Run `tamarind <command> --help` for full options.
|
|
|
239
239
|
| Job API base | `--api-base` | `TAMARIND_API_BASE` | `https://app.tamarind.bio/api/` |
|
|
240
240
|
| Catalog base | `--catalog-base` | `TAMARIND_CATALOG_BASE` | `https://mcp.tamarind.bio` |
|
|
241
241
|
| Profile | `--profile` | `TAMARIND_PROFILE` | `default` |
|
|
242
|
+
| AI agent reported to Tamarind | — | `TAMARIND_AGENT` | detected; `none` to send none |
|
|
243
|
+
|
|
244
|
+
Every request says whether it came from the CLI or the SDK, and which AI agent (Claude Code,
|
|
245
|
+
Codex, Claude Science, ...) is running it when that can be told from the environment. Tamarind
|
|
246
|
+
uses this only to count usage by channel and platform.
|
|
242
247
|
|
|
243
248
|
Profiles (key + endpoints) are stored in `~/.tamarind/config.json`. Use a
|
|
244
249
|
profile to point at staging:
|
|
@@ -80,10 +80,9 @@ BuildRequest, queue, lease, claim, or repair state. An ambiguous build response
|
|
|
80
80
|
is retried with the same caller-selected `Idempotency-Key`, or handled by listing Versions when
|
|
81
81
|
the caller did not supply one.
|
|
82
82
|
|
|
83
|
-
The resource layer
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
endpoint path. Tool and Version ETags remain the mutation validators.
|
|
83
|
+
The resource layer uses the returned numbered `Version.version`, such as `v3`,
|
|
84
|
+
to select exact reads, logs, cancellation, and publication. Opaque, server-issued
|
|
85
|
+
Tool and Version ETags remain the identity and mutation validators.
|
|
87
86
|
|
|
88
87
|
The generated contract and public SDK signatures use standard `If-Match`. At the
|
|
89
88
|
final HTTP adapter boundary, the CLI forwards that value as
|
|
@@ -76,11 +76,11 @@ tamarind --json custom-tools build my-tool ./my-tool \
|
|
|
76
76
|
--wait --timeout 1800 --poll-interval 10
|
|
77
77
|
```
|
|
78
78
|
|
|
79
|
-
Finally, publish the completed Version using the
|
|
79
|
+
Finally, publish the completed Version using the `version.version` returned by
|
|
80
80
|
the build:
|
|
81
81
|
|
|
82
82
|
```bash
|
|
83
|
-
tamarind --json custom-tools publish my-tool
|
|
83
|
+
tamarind --json custom-tools publish my-tool VERSION
|
|
84
84
|
```
|
|
85
85
|
|
|
86
86
|
A successful local validation returns:
|
|
@@ -95,8 +95,7 @@ A build result has this general shape:
|
|
|
95
95
|
{
|
|
96
96
|
"action": "build",
|
|
97
97
|
"version": {
|
|
98
|
-
"
|
|
99
|
-
"name": "v3",
|
|
98
|
+
"version": "v3",
|
|
100
99
|
"toolName": "my-tool",
|
|
101
100
|
"status": "Complete",
|
|
102
101
|
"terminal": true
|
|
@@ -104,21 +103,20 @@ A build result has this general shape:
|
|
|
104
103
|
}
|
|
105
104
|
```
|
|
106
105
|
|
|
107
|
-
|
|
108
|
-
|
|
106
|
+
Use `version.version`, such as `v3`, for Version operations. The SDK retains opaque
|
|
107
|
+
ETags internally so existing resource handles cannot cross tool deletion and name reuse.
|
|
109
108
|
|
|
110
109
|
Use exact reads for identity checks: `custom-tools get NAME` for a Tool and
|
|
111
|
-
`custom-tools version NAME
|
|
110
|
+
`custom-tools version NAME VERSION` for a Version. The `list`, `versions`,
|
|
112
111
|
and `logs` commands each return one page; follow `nextCursor` with `--cursor`
|
|
113
112
|
until it is `null` when a complete collection or log stream is required.
|
|
114
113
|
|
|
115
114
|
Use an idempotency key for builds initiated by automation. If delivery of the
|
|
116
115
|
first response is ambiguous, retrying with the same key returns the already
|
|
117
|
-
admitted Version instead of starting a duplicate build. In the SDK,
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
its Tool with `get()` automatically.
|
|
116
|
+
admitted Version instead of starting a duplicate build. In the SDK, retain the
|
|
117
|
+
same Tool snapshot and key for retries. Both `custom_tools.get()` and items from
|
|
118
|
+
`custom_tools.list()` carry the ETag needed for conditional operations and keyed
|
|
119
|
+
builds. The CLI selects its Tool with `get()` automatically.
|
|
122
120
|
|
|
123
121
|
## Runtime contract
|
|
124
122
|
|
|
@@ -146,10 +144,10 @@ entire CLI invocation must be bounded.
|
|
|
146
144
|
|
|
147
145
|
Exit code 7 means the monitoring timeout elapsed; the remote build may still be
|
|
148
146
|
running. Do not start a new build just because monitoring timed out. Reattach by
|
|
149
|
-
Version
|
|
147
|
+
numbered Version instead:
|
|
150
148
|
|
|
151
149
|
```bash
|
|
152
|
-
tamarind --json custom-tools version my-tool
|
|
150
|
+
tamarind --json custom-tools version my-tool VERSION \
|
|
153
151
|
--wait --timeout 1800 --poll-interval 10
|
|
154
152
|
```
|
|
155
153
|
|
|
@@ -157,12 +155,12 @@ Read build logs, following the returned cursor when the response has another
|
|
|
157
155
|
page:
|
|
158
156
|
|
|
159
157
|
```bash
|
|
160
|
-
tamarind --json custom-tools logs my-tool
|
|
161
|
-
tamarind --json custom-tools logs my-tool
|
|
158
|
+
tamarind --json custom-tools logs my-tool VERSION
|
|
159
|
+
tamarind --json custom-tools logs my-tool VERSION --cursor NEXT_CURSOR
|
|
162
160
|
```
|
|
163
161
|
|
|
164
162
|
Once the CLI has a durable Version, monitoring timeout and failure errors retain
|
|
165
|
-
`toolName
|
|
163
|
+
`toolName` and `version` in their structured detail. Errors
|
|
166
164
|
from the initial `build --wait` monitoring phase also include `action`; errors
|
|
167
165
|
from a later `version --wait` reattachment do not. A failure before build
|
|
168
166
|
admission has returned a Version cannot provide this handle, which is why
|
|
@@ -171,15 +169,15 @@ automated builds should reuse their idempotency key after an ambiguous request.
|
|
|
171
169
|
## Publish and roll back
|
|
172
170
|
|
|
173
171
|
Publishing changes which completed Version is active. List Versions, inspect the
|
|
174
|
-
candidate, and publish its
|
|
172
|
+
candidate, and publish its version number:
|
|
175
173
|
|
|
176
174
|
```bash
|
|
177
175
|
tamarind --json custom-tools versions my-tool
|
|
178
|
-
tamarind --json custom-tools version my-tool
|
|
179
|
-
tamarind --json custom-tools publish my-tool
|
|
176
|
+
tamarind --json custom-tools version my-tool VERSION
|
|
177
|
+
tamarind --json custom-tools publish my-tool VERSION
|
|
180
178
|
```
|
|
181
179
|
|
|
182
|
-
Rollback uses the same operation: publish the
|
|
180
|
+
Rollback uses the same operation: publish the number of an older known-good,
|
|
183
181
|
completed Version.
|
|
184
182
|
|
|
185
183
|
## Update, cancel, and delete
|
|
@@ -195,7 +193,7 @@ Cancellation and deletion are destructive. Non-interactive callers must pass
|
|
|
195
193
|
`--yes` explicitly:
|
|
196
194
|
|
|
197
195
|
```bash
|
|
198
|
-
tamarind --json custom-tools cancel my-tool
|
|
196
|
+
tamarind --json custom-tools cancel my-tool VERSION --yes
|
|
199
197
|
tamarind --json custom-tools delete my-tool --yes
|
|
200
198
|
```
|
|
201
199
|
|
|
@@ -213,10 +211,10 @@ confirm the mutation is still appropriate, and retry with the refreshed state.
|
|
|
213
211
|
| `custom-tools validate FOLDER` | Validate local source without auth or upload | — |
|
|
214
212
|
| `custom-tools build NAME FOLDER` | Package, upload, build, and optionally monitor a Version | `--idempotency-key`, `--wait`, monitoring `--timeout`, `--poll-interval` |
|
|
215
213
|
| `custom-tools versions NAME` | Read one page of a tool's Versions | `--limit`, `--cursor` |
|
|
216
|
-
| `custom-tools version NAME
|
|
217
|
-
| `custom-tools logs NAME
|
|
218
|
-
| `custom-tools cancel NAME
|
|
219
|
-
| `custom-tools publish NAME
|
|
214
|
+
| `custom-tools version NAME VERSION` | Read or monitor one exact Version | `--wait`, monitoring `--timeout`, `--poll-interval` |
|
|
215
|
+
| `custom-tools logs NAME VERSION` | Read one page of build logs | `--cursor` |
|
|
216
|
+
| `custom-tools cancel NAME VERSION` | Cancel an active build | `--yes` |
|
|
217
|
+
| `custom-tools publish NAME VERSION` | Make a completed Version active | — |
|
|
220
218
|
| `custom-tools delete NAME` | Delete a tool | `--yes` |
|
|
221
219
|
|
|
222
220
|
Run `tamarind custom-tools COMMAND --help` for every option and default.
|
|
@@ -245,7 +243,7 @@ release. The supported CLI path starts from a local source folder.
|
|
|
245
243
|
SDK Tool objects are snapshots. Assign `tool = tool.update(...)` after an update, and
|
|
246
244
|
`tool = tool.refresh()` after a build before starting a different build. For builds without an
|
|
247
245
|
idempotency key, upload creation checks the snapshot before transferring bytes; build admission
|
|
248
|
-
checks it again. Keyed builds using
|
|
246
|
+
checks it again. Keyed builds using the retained Tool snapshot defer the revision check
|
|
249
247
|
to replay-aware admission so a retry can recover a previously committed result. For a different
|
|
250
248
|
build after the tool changes, review its latest state before retrying.
|
|
251
249
|
|
|
@@ -261,7 +259,7 @@ This uses compute, just like an ordinary submission.
|
|
|
261
259
|
|
|
262
260
|
```bash
|
|
263
261
|
tamarind custom-tools versions my-tool
|
|
264
|
-
tamarind --json custom-tools test my-tool --version
|
|
262
|
+
tamarind --json custom-tools test my-tool --version v3 \
|
|
265
263
|
--input inputs.yaml --set numDesigns=10 --name my-tool-smoke
|
|
266
264
|
tamarind status my-tool-smoke
|
|
267
265
|
tamarind wait my-tool-smoke --timeout 600
|
|
@@ -285,11 +283,11 @@ from tamarind import Tamarind
|
|
|
285
283
|
|
|
286
284
|
with Tamarind() as client:
|
|
287
285
|
tool = client.custom_tools.get("my-tool")
|
|
288
|
-
job = tool.test({"numDesigns": 10}, version="
|
|
286
|
+
job = tool.test({"numDesigns": 10}, version="v3")
|
|
289
287
|
print(job.job_name, job.status)
|
|
290
288
|
```
|
|
291
289
|
|
|
292
|
-
`tool.test()` requires
|
|
290
|
+
`tool.test()` requires a numbered version such as `v3` and returns a `CustomToolTestJob`
|
|
293
291
|
receipt. It resolves the selected version, checks the tool's identity internally to reject
|
|
294
292
|
stale handles, and explicitly marks the run as a test. Version pins alone never
|
|
295
293
|
turn normal submissions into tests.
|