tamarind-cli 0.4.2__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.
Files changed (139) hide show
  1. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/.github/workflows/ci.yml +2 -2
  2. tamarind_cli-0.4.2/README.md → tamarind_cli-0.5.0/PKG-INFO +69 -7
  3. tamarind_cli-0.4.2/PKG-INFO → tamarind_cli-0.5.0/README.md +43 -33
  4. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/docs/architecture.md +8 -4
  5. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/docs/custom-tools.md +78 -25
  6. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/openapi/public-v1.json +517 -288
  7. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/openapi/public-v1.lock.json +2 -2
  8. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/pyproject.toml +2 -2
  9. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/scripts/check_custom_tools_provenance.py +21 -4
  10. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/scripts/sync_custom_tools_contract.py +8 -8
  11. tamarind_cli-0.5.0/src/tamarind/attribution.py +75 -0
  12. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/custom_tools.py +74 -51
  13. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/files.py +5 -73
  14. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/jobs.py +143 -33
  15. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/inputs.py +18 -6
  16. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/main.py +2 -1
  17. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/__init__.py +2 -0
  18. tamarind_cli-0.4.2/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 +32 -24
  19. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/cancel_custom_tool_build.py +49 -45
  20. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/create_custom_tool_upload.py +24 -1
  21. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/delete_custom_tool.py +16 -20
  22. tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool.py +237 -0
  23. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tool_build_logs.py +49 -25
  24. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tool_versions.py +22 -0
  25. tamarind_cli-0.4.2/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 +48 -45
  26. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/update_custom_tool.py +12 -16
  27. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/__init__.py +6 -0
  28. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_log_page.py +24 -0
  29. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request.py +8 -5
  30. tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/models/public_create_version_request.py +66 -0
  31. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool.py +8 -9
  32. tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/models/public_custom_tool_detail.py +274 -0
  33. tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/models/public_custom_tool_detail_gputype.py +13 -0
  34. tamarind_cli-0.5.0/src/tamarind/custom_tools/_generated/models/public_custom_tool_detail_memory.py +16 -0
  35. {tamarind_cli-0.4.2/src/tamarind/pipelines → tamarind_cli-0.5.0/src/tamarind/custom_tools}/_generated/models/public_problem.py +22 -0
  36. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request.py +20 -11
  37. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_version.py +20 -12
  38. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/client.py +5 -0
  39. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/resources.py +147 -144
  40. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/transport.py +87 -37
  41. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/validation.py +5 -1
  42. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/errors.py +9 -1
  43. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/http.py +3 -0
  44. tamarind_cli-0.5.0/src/tamarind/resources.py +160 -0
  45. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/rest.py +41 -6
  46. tamarind_cli-0.5.0/src/tamarind/uploads.py +73 -0
  47. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_agent_contract.py +34 -8
  48. tamarind_cli-0.5.0/tests/test_attribution.py +58 -0
  49. tamarind_cli-0.5.0/tests/test_batch_prevalidate.py +275 -0
  50. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_bugbash.py +5 -9
  51. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_cli_commands.py +5 -5
  52. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_custom_tools_cli.py +241 -19
  53. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_custom_tools_generation.py +27 -8
  54. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_custom_tools_packaging.py +4 -2
  55. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_custom_tools_sdk.py +489 -122
  56. tamarind_cli-0.5.0/tests/test_errors.py +19 -0
  57. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_inputs.py +26 -1
  58. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_rest.py +24 -3
  59. tamarind_cli-0.5.0/tests/test_sdk_resources.py +81 -0
  60. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/uv.lock +1 -1
  61. tamarind_cli-0.4.2/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool.py +0 -177
  62. tamarind_cli-0.4.2/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool_version.py +0 -199
  63. tamarind_cli-0.4.2/src/tamarind/custom_tools/_generated/models/public_create_version_request.py +0 -50
  64. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/.github/workflows/publish.yml +0 -0
  65. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/.gitignore +0 -0
  66. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/LICENSE +0 -0
  67. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/install.sh +0 -0
  68. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/openapi/openapi-python-client.json +0 -0
  69. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/openapi/pipelines-openapi-python-client.json +0 -0
  70. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/openapi/pipelines-v1.json +0 -0
  71. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/openapi/pipelines-v1.lock.json +0 -0
  72. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/scripts/sync_pipelines_contract.py +0 -0
  73. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/__init__.py +0 -0
  74. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/catalog.py +0 -0
  75. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/__init__.py +0 -0
  76. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/__init__.py +0 -0
  77. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/auth.py +0 -0
  78. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/commands/catalog.py +0 -0
  79. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/guidance.py +0 -0
  80. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/cli/output.py +0 -0
  81. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/config.py +0 -0
  82. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_contract.py +0 -0
  83. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/__init__.py +0 -0
  84. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/__init__.py +0 -0
  85. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/__init__.py +0 -0
  86. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/create_custom_tool.py +0 -0
  87. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tools.py +0 -0
  88. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/client.py +0 -0
  89. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/errors.py +0 -0
  90. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_error.py +0 -0
  91. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_event.py +0 -0
  92. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_result.py +0 -0
  93. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_build_result_action.py +0 -0
  94. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request_gputype.py +0 -0
  95. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request_memory.py +0 -0
  96. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_gputype.py +0 -0
  97. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_memory.py +0 -0
  98. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_page.py +0 -0
  99. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_custom_tool_status.py +0 -0
  100. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_problem_errors_type_0_item.py +0 -0
  101. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request_gpu_type_type_0.py +0 -0
  102. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request_memory_type_0.py +0 -0
  103. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_upload_session.py +0 -0
  104. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_upload_session_uploadheaders.py +0 -0
  105. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_version_page.py +0 -0
  106. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/models/public_version_status.py +0 -0
  107. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/_generated/types.py +0 -0
  108. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/custom_tools/packaging.py +0 -0
  109. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/jobs.py +0 -0
  110. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/__init__.py +0 -0
  111. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/__init__.py +0 -0
  112. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/__init__.py +0 -0
  113. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/pipelines_public/__init__.py +0 -0
  114. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/pipelines_public/get_run.py +0 -0
  115. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/api/pipelines_public/list_node_run_molecules.py +0 -0
  116. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/client.py +0 -0
  117. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/errors.py +0 -0
  118. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/__init__.py +0 -0
  119. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/node_run_status.py +0 -0
  120. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run.py +0 -0
  121. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run_molecule.py +0 -0
  122. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run_molecule_page.py +0 -0
  123. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_node_run_molecule_scores.py +0 -0
  124. {tamarind_cli-0.4.2/src/tamarind/custom_tools → tamarind_cli-0.5.0/src/tamarind/pipelines}/_generated/models/public_problem.py +0 -0
  125. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_problem_errors_type_0_item.py +0 -0
  126. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_run.py +0 -0
  127. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/public_run_inputs.py +0 -0
  128. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/run_status.py +0 -0
  129. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/models/source.py +0 -0
  130. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/_generated/types.py +0 -0
  131. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/resources.py +0 -0
  132. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/pipelines/transport.py +0 -0
  133. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/src/tamarind/py.typed +0 -0
  134. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_config.py +0 -0
  135. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_file_filters.py +0 -0
  136. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_jobs.py +0 -0
  137. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_output.py +0 -0
  138. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_pep561.py +0 -0
  139. {tamarind_cli-0.4.2 → tamarind_cli-0.5.0}/tests/test_pipelines_sdk.py +0 -0
@@ -10,13 +10,13 @@ permissions:
10
10
 
11
11
  jobs:
12
12
  generated:
13
- name: Generated transport is current
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 backend provenance and generated client freshness
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,3 +1,29 @@
1
+ Metadata-Version: 2.5
2
+ Name: tamarind-cli
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
+ Project-URL: Homepage, https://tamarind.bio
6
+ Project-URL: Documentation, https://app.tamarind.bio/api-docs
7
+ Project-URL: Source, https://github.com/Tamarind-Bio/tamarind-cli
8
+ Author: Tamarind Bio
9
+ License: Apache-2.0
10
+ License-File: LICENSE
11
+ Keywords: agents,alphafold,bioinformatics,boltz,cli,protein
12
+ Requires-Python: >=3.10
13
+ Requires-Dist: attrs>=23.1
14
+ Requires-Dist: click>=8.1
15
+ Requires-Dist: httpx>=0.27
16
+ Requires-Dist: pyyaml>=6.0
17
+ Requires-Dist: typer>=0.12
18
+ Requires-Dist: typing-extensions>=4.7
19
+ Provides-Extra: dev
20
+ Requires-Dist: mypy>=1.11; extra == 'dev'
21
+ Requires-Dist: openapi-python-client==0.28.4; extra == 'dev'
22
+ Requires-Dist: pytest>=8.0; extra == 'dev'
23
+ Requires-Dist: respx>=0.21; extra == 'dev'
24
+ Requires-Dist: ruff>=0.5; extra == 'dev'
25
+ Description-Content-Type: text/markdown
26
+
1
27
  # Tamarind CLI
2
28
 
3
29
  [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/LICENSE)
@@ -114,7 +140,7 @@ with Tamarind() as client:
114
140
  result = tool.build("./my-esmfold", idempotency_key="release-2026-08-26")
115
141
  print(result.action) # build, reuse_image, or unchanged
116
142
  version = result.version
117
- print(version.id, version.name) # opaque machine identity, human-facing label
143
+ print(version.version) # numbered version, e.g. v3
118
144
  if not version.terminal:
119
145
  version = version.monitor(timeout=1800, on_event=print)
120
146
  ```
@@ -126,7 +152,7 @@ server returns the already admitted Version. If no key was supplied, fetch the
126
152
  tool's versions before retrying. Interrupting `monitor()` stops local monitoring; it
127
153
  does not cancel the remote build.
128
154
 
129
- Exact Version operations use `version.id`; `version.name` is display-only. If a
155
+ Exact Version operations use `version.version`, such as `v3`. If a
130
156
  mutation reports `412 Precondition Failed`, refetch the affected Tool or Version,
131
157
  confirm the mutation is still desired, and retry using the refreshed resource.
132
158
 
@@ -138,13 +164,44 @@ tamarind custom-tools create my-esmfold --display-name "My ESMFold"
138
164
  tamarind custom-tools build my-esmfold ./my-esmfold \
139
165
  --idempotency-key release-2026-08-31 --wait --timeout 1800
140
166
  tamarind custom-tools versions my-esmfold
141
- tamarind custom-tools publish my-esmfold <opaque-version-id>
167
+ tamarind custom-tools publish my-esmfold v3
142
168
  ```
143
169
 
144
- Build responses contain both a display name such as `v3` and an opaque `id`.
145
- Pass the opaque ID to `version`, `logs`, `cancel`, and `publish`. A local wait
170
+ Build responses contain a numbered `version`, such as `v3`.
171
+ Pass it to `version`, `logs`, `cancel`, and `publish`. A local wait
146
172
  timeout does not cancel the remote build; reattach with
147
- `tamarind custom-tools version NAME VERSION_ID --wait`.
173
+ `tamarind custom-tools version NAME VERSION --wait`.
174
+
175
+ ### Test a completed Custom Tool version
176
+
177
+ After building, submit a test without publishing the version:
178
+
179
+ ```bash
180
+ tamarind custom-tools test my-esmfold --version v3 \
181
+ --input inputs.json --name esmfold-smoke
182
+ tamarind status esmfold-smoke
183
+ tamarind wait esmfold-smoke --timeout 600
184
+ ```
185
+
186
+ Or use the SDK:
187
+
188
+ ```python
189
+ from tamarind import Tamarind
190
+
191
+ with Tamarind() as client:
192
+ tool = client.custom_tools.get("my-esmfold")
193
+ job = tool.test({"sequence": "MKT..."}, version="v3", name="esmfold-smoke")
194
+ print(job.job_name, job.id, job.status)
195
+ ```
196
+
197
+ The command returns after submission and the run appears in the tool's website
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 version number (such as `v3`) from
200
+ `build` or `versions`; the SDK resolves its execution pin and protects against
201
+ deleting and recreating the tool. The selected build must be complete. Design
202
+ splitting is handled by the backend and returns the parent job receipt.
203
+ Normal `submit` commands keep their existing behavior. If submission times out,
204
+ check the job name in the error details before retrying; it may already be running.
148
205
 
149
206
  For the complete CLI workflow, source layout, build monitoring, publishing, and
150
207
  rollback examples, see the
@@ -194,7 +251,7 @@ place them before the command name.
194
251
  | Submit | `validate`, `submit`, `batch` |
195
252
  | Monitor | `jobs`, `status`, `wait`, `results`, `logs` |
196
253
  | Files | `files list`, `files stats`, `files upload`, `files delete`, `files folders` |
197
- | Custom Tools | `custom-tools list`, `get`, `create`, `update`, `validate`, `build`, `versions`, `version`, `logs`, `cancel`, `publish`, `delete` |
254
+ | Custom Tools | `custom-tools list`, `get`, `create`, `update`, `validate`, `build`, `test`, `versions`, `version`, `logs`, `cancel`, `publish`, `delete` |
198
255
  | Lifecycle | `cancel`, `delete` |
199
256
  | Auth | `auth login`, `auth status`, `auth logout` |
200
257
 
@@ -208,6 +265,11 @@ Run `tamarind <command> --help` for full options.
208
265
  | Job API base | `--api-base` | `TAMARIND_API_BASE` | `https://app.tamarind.bio/api/` |
209
266
  | Catalog base | `--catalog-base` | `TAMARIND_CATALOG_BASE` | `https://mcp.tamarind.bio` |
210
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.
211
273
 
212
274
  Profiles (key + endpoints) are stored in `~/.tamarind/config.json`. Use a
213
275
  profile to point at staging:
@@ -1,29 +1,3 @@
1
- Metadata-Version: 2.5
2
- Name: tamarind-cli
3
- Version: 0.4.2
4
- Summary: Command-line interface for the Tamarind Bio platform — submit, monitor, and download protein/molecule jobs from your terminal or an AI agent.
5
- Project-URL: Homepage, https://tamarind.bio
6
- Project-URL: Documentation, https://app.tamarind.bio/api-docs
7
- Project-URL: Source, https://github.com/Tamarind-Bio/tamarind-cli
8
- Author: Tamarind Bio
9
- License: Apache-2.0
10
- License-File: LICENSE
11
- Keywords: agents,alphafold,bioinformatics,boltz,cli,protein
12
- Requires-Python: >=3.10
13
- Requires-Dist: attrs>=23.1
14
- Requires-Dist: click>=8.1
15
- Requires-Dist: httpx>=0.27
16
- Requires-Dist: pyyaml>=6.0
17
- Requires-Dist: typer>=0.12
18
- Requires-Dist: typing-extensions>=4.7
19
- Provides-Extra: dev
20
- Requires-Dist: mypy>=1.11; extra == 'dev'
21
- Requires-Dist: openapi-python-client==0.28.4; extra == 'dev'
22
- Requires-Dist: pytest>=8.0; extra == 'dev'
23
- Requires-Dist: respx>=0.21; extra == 'dev'
24
- Requires-Dist: ruff>=0.5; extra == 'dev'
25
- Description-Content-Type: text/markdown
26
-
27
1
  # Tamarind CLI
28
2
 
29
3
  [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/LICENSE)
@@ -140,7 +114,7 @@ with Tamarind() as client:
140
114
  result = tool.build("./my-esmfold", idempotency_key="release-2026-08-26")
141
115
  print(result.action) # build, reuse_image, or unchanged
142
116
  version = result.version
143
- print(version.id, version.name) # opaque machine identity, human-facing label
117
+ print(version.version) # numbered version, e.g. v3
144
118
  if not version.terminal:
145
119
  version = version.monitor(timeout=1800, on_event=print)
146
120
  ```
@@ -152,7 +126,7 @@ server returns the already admitted Version. If no key was supplied, fetch the
152
126
  tool's versions before retrying. Interrupting `monitor()` stops local monitoring; it
153
127
  does not cancel the remote build.
154
128
 
155
- Exact Version operations use `version.id`; `version.name` is display-only. If a
129
+ Exact Version operations use `version.version`, such as `v3`. If a
156
130
  mutation reports `412 Precondition Failed`, refetch the affected Tool or Version,
157
131
  confirm the mutation is still desired, and retry using the refreshed resource.
158
132
 
@@ -164,13 +138,44 @@ tamarind custom-tools create my-esmfold --display-name "My ESMFold"
164
138
  tamarind custom-tools build my-esmfold ./my-esmfold \
165
139
  --idempotency-key release-2026-08-31 --wait --timeout 1800
166
140
  tamarind custom-tools versions my-esmfold
167
- tamarind custom-tools publish my-esmfold <opaque-version-id>
141
+ tamarind custom-tools publish my-esmfold v3
168
142
  ```
169
143
 
170
- Build responses contain both a display name such as `v3` and an opaque `id`.
171
- Pass the opaque ID to `version`, `logs`, `cancel`, and `publish`. A local wait
144
+ Build responses contain a numbered `version`, such as `v3`.
145
+ Pass it to `version`, `logs`, `cancel`, and `publish`. A local wait
172
146
  timeout does not cancel the remote build; reattach with
173
- `tamarind custom-tools version NAME VERSION_ID --wait`.
147
+ `tamarind custom-tools version NAME VERSION --wait`.
148
+
149
+ ### Test a completed Custom Tool version
150
+
151
+ After building, submit a test without publishing the version:
152
+
153
+ ```bash
154
+ tamarind custom-tools test my-esmfold --version v3 \
155
+ --input inputs.json --name esmfold-smoke
156
+ tamarind status esmfold-smoke
157
+ tamarind wait esmfold-smoke --timeout 600
158
+ ```
159
+
160
+ Or use the SDK:
161
+
162
+ ```python
163
+ from tamarind import Tamarind
164
+
165
+ with Tamarind() as client:
166
+ tool = client.custom_tools.get("my-esmfold")
167
+ job = tool.test({"sequence": "MKT..."}, version="v3", name="esmfold-smoke")
168
+ print(job.job_name, job.id, job.status)
169
+ ```
170
+
171
+ The command returns after submission and the run appears in the tool's website
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 version number (such as `v3`) from
174
+ `build` or `versions`; the SDK resolves its execution pin and protects against
175
+ deleting and recreating the tool. The selected build must be complete. Design
176
+ splitting is handled by the backend and returns the parent job receipt.
177
+ Normal `submit` commands keep their existing behavior. If submission times out,
178
+ check the job name in the error details before retrying; it may already be running.
174
179
 
175
180
  For the complete CLI workflow, source layout, build monitoring, publishing, and
176
181
  rollback examples, see the
@@ -220,7 +225,7 @@ place them before the command name.
220
225
  | Submit | `validate`, `submit`, `batch` |
221
226
  | Monitor | `jobs`, `status`, `wait`, `results`, `logs` |
222
227
  | Files | `files list`, `files stats`, `files upload`, `files delete`, `files folders` |
223
- | Custom Tools | `custom-tools list`, `get`, `create`, `update`, `validate`, `build`, `versions`, `version`, `logs`, `cancel`, `publish`, `delete` |
228
+ | Custom Tools | `custom-tools list`, `get`, `create`, `update`, `validate`, `build`, `test`, `versions`, `version`, `logs`, `cancel`, `publish`, `delete` |
224
229
  | Lifecycle | `cancel`, `delete` |
225
230
  | Auth | `auth login`, `auth status`, `auth logout` |
226
231
 
@@ -234,6 +239,11 @@ Run `tamarind <command> --help` for full options.
234
239
  | Job API base | `--api-base` | `TAMARIND_API_BASE` | `https://app.tamarind.bio/api/` |
235
240
  | Catalog base | `--catalog-base` | `TAMARIND_CATALOG_BASE` | `https://mcp.tamarind.bio` |
236
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.
237
247
 
238
248
  Profiles (key + endpoints) are stored in `~/.tamarind/config.json`. Use a
239
249
  profile to point at staging:
@@ -58,6 +58,11 @@ CI regenerates with the pinned mature generator and rejects drift. The handwritt
58
58
  layer contains only HTTP/error normalization and ergonomic resource composition; it
59
59
  does not parse OpenAPI or maintain a second schema IR/compiler.
60
60
 
61
+ Direct HTTP mutations accept optional `If-Match`. The SDK/CLI resource layer still
62
+ supplies observed validators automatically, preserving stale-snapshot protection.
63
+ The generated endpoints reflect the optional wire contract; the resource facade
64
+ does not require users to manage headers.
65
+
61
66
  The SDK owns archive-local concerns that only the client can decide safely:
62
67
  deterministic ZIP construction, symlink and junction rejection, upload limits,
63
68
  JSON parseability and top-level object shape, and warnings about the networkless
@@ -75,10 +80,9 @@ BuildRequest, queue, lease, claim, or repair state. An ambiguous build response
75
80
  is retried with the same caller-selected `Idempotency-Key`, or handled by listing Versions when
76
81
  the caller did not supply one.
77
82
 
78
- The resource layer treats the returned opaque `Version.id` as the sole machine
79
- selector for exact reads, logs, cancellation, and publication. The numbered
80
- `Version.name` remains presentation metadata and is never reconstructed into an
81
- 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.
82
86
 
83
87
  The generated contract and public SDK signatures use standard `If-Match`. At the
84
88
  final HTTP adapter boundary, the CLI forwards that value as
@@ -38,9 +38,8 @@ my-tool/
38
38
  └── ...
39
39
  ```
40
40
 
41
- `Dockerfile` is required. `run.sh` is strongly recommended because the runtime
42
- invokes it directly. `config.json` is optional for local validation; when it is
43
- present, it must be a JSON object and the server validates its full semantics.
41
+ `Dockerfile` and `config.json` are required. `run.sh` is strongly recommended because the runtime
42
+ invokes it directly. `config.json` must be a JSON object; the server validates its full semantics.
44
43
 
45
44
  Run the lifecycle in this order. First, validate locally. This step does not
46
45
  authenticate, upload, or build anything:
@@ -77,11 +76,11 @@ tamarind --json custom-tools build my-tool ./my-tool \
77
76
  --wait --timeout 1800 --poll-interval 10
78
77
  ```
79
78
 
80
- Finally, publish the completed Version using the opaque `version.id` returned by
79
+ Finally, publish the completed Version using the `version.version` returned by
81
80
  the build:
82
81
 
83
82
  ```bash
84
- tamarind --json custom-tools publish my-tool VERSION_ID
83
+ tamarind --json custom-tools publish my-tool VERSION
85
84
  ```
86
85
 
87
86
  A successful local validation returns:
@@ -96,8 +95,7 @@ A build result has this general shape:
96
95
  {
97
96
  "action": "build",
98
97
  "version": {
99
- "id": "0192d87e-12ab-7cde-9f01-23456789abcd",
100
- "name": "v3",
98
+ "version": "v3",
101
99
  "toolName": "my-tool",
102
100
  "status": "Complete",
103
101
  "terminal": true
@@ -105,17 +103,20 @@ A build result has this general shape:
105
103
  }
106
104
  ```
107
105
 
108
- Always save and use `version.id` for exact Version operations. `version.name`
109
- such as `v3` is a display label, not an endpoint identifier.
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.
110
108
 
111
109
  Use exact reads for identity checks: `custom-tools get NAME` for a Tool and
112
- `custom-tools version NAME VERSION_ID` for a Version. The `list`, `versions`,
110
+ `custom-tools version NAME VERSION` for a Version. The `list`, `versions`,
113
111
  and `logs` commands each return one page; follow `nextCursor` with `--cursor`
114
112
  until it is `null` when a complete collection or log stream is required.
115
113
 
116
114
  Use an idempotency key for builds initiated by automation. If delivery of the
117
115
  first response is ambiguous, retrying with the same key returns the already
118
- admitted Version instead of starting a duplicate build.
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.
119
120
 
120
121
  ## Runtime contract
121
122
 
@@ -143,10 +144,10 @@ entire CLI invocation must be bounded.
143
144
 
144
145
  Exit code 7 means the monitoring timeout elapsed; the remote build may still be
145
146
  running. Do not start a new build just because monitoring timed out. Reattach by
146
- Version ID instead:
147
+ numbered Version instead:
147
148
 
148
149
  ```bash
149
- tamarind --json custom-tools version my-tool VERSION_ID \
150
+ tamarind --json custom-tools version my-tool VERSION \
150
151
  --wait --timeout 1800 --poll-interval 10
151
152
  ```
152
153
 
@@ -154,12 +155,12 @@ Read build logs, following the returned cursor when the response has another
154
155
  page:
155
156
 
156
157
  ```bash
157
- tamarind --json custom-tools logs my-tool VERSION_ID
158
- tamarind --json custom-tools logs my-tool VERSION_ID --cursor NEXT_CURSOR
158
+ tamarind --json custom-tools logs my-tool VERSION
159
+ tamarind --json custom-tools logs my-tool VERSION --cursor NEXT_CURSOR
159
160
  ```
160
161
 
161
162
  Once the CLI has a durable Version, monitoring timeout and failure errors retain
162
- `toolName`, `versionId`, and `versionName` in their structured detail. Errors
163
+ `toolName` and `version` in their structured detail. Errors
163
164
  from the initial `build --wait` monitoring phase also include `action`; errors
164
165
  from a later `version --wait` reattachment do not. A failure before build
165
166
  admission has returned a Version cannot provide this handle, which is why
@@ -168,15 +169,15 @@ automated builds should reuse their idempotency key after an ambiguous request.
168
169
  ## Publish and roll back
169
170
 
170
171
  Publishing changes which completed Version is active. List Versions, inspect the
171
- candidate, and publish its opaque ID:
172
+ candidate, and publish its version number:
172
173
 
173
174
  ```bash
174
175
  tamarind --json custom-tools versions my-tool
175
- tamarind --json custom-tools version my-tool VERSION_ID
176
- tamarind --json custom-tools publish my-tool VERSION_ID
176
+ tamarind --json custom-tools version my-tool VERSION
177
+ tamarind --json custom-tools publish my-tool VERSION
177
178
  ```
178
179
 
179
- Rollback uses the same operation: publish the ID of an older known-good,
180
+ Rollback uses the same operation: publish the number of an older known-good,
180
181
  completed Version.
181
182
 
182
183
  ## Update, cancel, and delete
@@ -192,7 +193,7 @@ Cancellation and deletion are destructive. Non-interactive callers must pass
192
193
  `--yes` explicitly:
193
194
 
194
195
  ```bash
195
- tamarind --json custom-tools cancel my-tool VERSION_ID --yes
196
+ tamarind --json custom-tools cancel my-tool VERSION --yes
196
197
  tamarind --json custom-tools delete my-tool --yes
197
198
  ```
198
199
 
@@ -210,10 +211,10 @@ confirm the mutation is still appropriate, and retry with the refreshed state.
210
211
  | `custom-tools validate FOLDER` | Validate local source without auth or upload | — |
211
212
  | `custom-tools build NAME FOLDER` | Package, upload, build, and optionally monitor a Version | `--idempotency-key`, `--wait`, monitoring `--timeout`, `--poll-interval` |
212
213
  | `custom-tools versions NAME` | Read one page of a tool's Versions | `--limit`, `--cursor` |
213
- | `custom-tools version NAME VERSION_ID` | Read or monitor one exact Version | `--wait`, monitoring `--timeout`, `--poll-interval` |
214
- | `custom-tools logs NAME VERSION_ID` | Read one page of build logs | `--cursor` |
215
- | `custom-tools cancel NAME VERSION_ID` | Cancel an active build | `--yes` |
216
- | `custom-tools publish NAME VERSION_ID` | Make a completed Version active | — |
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 | — |
217
218
  | `custom-tools delete NAME` | Delete a tool | `--yes` |
218
219
 
219
220
  Run `tamarind custom-tools COMMAND --help` for every option and default.
@@ -238,3 +239,55 @@ contract, but they fit different execution environments:
238
239
 
239
240
  GitHub connection and push-to-deploy authorization are not part of the 0.4.0
240
241
  release. The supported CLI path starts from a local source folder.
242
+
243
+ SDK Tool objects are snapshots. Assign `tool = tool.update(...)` after an update, and
244
+ `tool = tool.refresh()` after a build before starting a different build. For builds without an
245
+ idempotency key, upload creation checks the snapshot before transferring bytes; build admission
246
+ checks it again. Keyed builds using the retained Tool snapshot defer the revision check
247
+ to replay-aware admission so a retry can recover a previously committed result. For a different
248
+ build after the tool changes, review its latest state before retrying.
249
+
250
+ `version.cancel()` requests cancellation of that exact active build even if its status advanced.
251
+ Use `version.cancel(if_unchanged=True)` when cancellation should require the observed state.
252
+ Cancellation is asynchronous; continue monitoring until the version is terminal.
253
+
254
+ ## Run a version as a test
255
+
256
+ The `test` command submits a real job using an exact completed build. It does not
257
+ publish the version, and the job appears in the website tool's Test history.
258
+ This uses compute, just like an ordinary submission.
259
+
260
+ ```bash
261
+ tamarind custom-tools versions my-tool
262
+ tamarind --json custom-tools test my-tool --version v3 \
263
+ --input inputs.yaml --set numDesigns=10 --name my-tool-smoke
264
+ tamarind status my-tool-smoke
265
+ tamarind wait my-tool-smoke --timeout 600
266
+ ```
267
+
268
+ `--input` accepts a settings mapping or the existing `{type, jobName, settings}`
269
+ envelope. `--set` overrides individual settings, and `--name` overrides the job
270
+ name from the file. Omit the name for an automatically generated unique name.
271
+ Settings can also come from stdin with `--input -`.
272
+
273
+ The command returns a receipt with `jobName`, `id`, `type`, `status`, and
274
+ `createdAt`; it does not wait for execution. For design-batched tools, this is the
275
+ logical parent job. Use existing `status`, `wait`, and `results` commands to follow
276
+ it. A submission timeout or server failure may mean the job was accepted; error
277
+ details preserve the job name so you can check it before retrying.
278
+
279
+ Python callers use the same implementation:
280
+
281
+ ```python
282
+ from tamarind import Tamarind
283
+
284
+ with Tamarind() as client:
285
+ tool = client.custom_tools.get("my-tool")
286
+ job = tool.test({"numDesigns": 10}, version="v3")
287
+ print(job.job_name, job.status)
288
+ ```
289
+
290
+ `tool.test()` requires a numbered version such as `v3` and returns a `CustomToolTestJob`
291
+ receipt. It resolves the selected version, checks the tool's identity internally to reject
292
+ stale handles, and explicitly marks the run as a test. Version pins alone never
293
+ turn normal submissions into tests.