tamarind-cli 0.4.0__tar.gz → 0.4.1__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 (127) hide show
  1. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/PKG-INFO +12 -5
  2. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/README.md +11 -4
  3. tamarind_cli-0.4.1/docs/custom-tools.md +240 -0
  4. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/pyproject.toml +1 -1
  5. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/validation.py +3 -1
  6. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_custom_tools_packaging.py +12 -2
  7. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/uv.lock +1 -1
  8. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/.github/workflows/ci.yml +0 -0
  9. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/.github/workflows/publish.yml +0 -0
  10. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/.gitignore +0 -0
  11. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/LICENSE +0 -0
  12. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/docs/architecture.md +0 -0
  13. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/install.sh +0 -0
  14. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/openapi/openapi-python-client.json +0 -0
  15. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/openapi/pipelines-openapi-python-client.json +0 -0
  16. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/openapi/pipelines-v1.json +0 -0
  17. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/openapi/pipelines-v1.lock.json +0 -0
  18. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/openapi/public-v1.json +0 -0
  19. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/openapi/public-v1.lock.json +0 -0
  20. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/scripts/check_custom_tools_provenance.py +0 -0
  21. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/scripts/sync_custom_tools_contract.py +0 -0
  22. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/scripts/sync_pipelines_contract.py +0 -0
  23. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/__init__.py +0 -0
  24. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/catalog.py +0 -0
  25. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/__init__.py +0 -0
  26. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/commands/__init__.py +0 -0
  27. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/commands/auth.py +0 -0
  28. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/commands/catalog.py +0 -0
  29. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/commands/custom_tools.py +0 -0
  30. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/commands/files.py +0 -0
  31. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/commands/jobs.py +0 -0
  32. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/guidance.py +0 -0
  33. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/inputs.py +0 -0
  34. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/main.py +0 -0
  35. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/cli/output.py +0 -0
  36. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/config.py +0 -0
  37. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/__init__.py +0 -0
  38. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_contract.py +0 -0
  39. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/__init__.py +0 -0
  40. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/__init__.py +0 -0
  41. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/__init__.py +0 -0
  42. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/build_custom_tool_version.py +0 -0
  43. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/cancel_custom_tool_build.py +0 -0
  44. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/create_custom_tool.py +0 -0
  45. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/create_custom_tool_upload.py +0 -0
  46. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/delete_custom_tool.py +0 -0
  47. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool.py +0 -0
  48. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/get_custom_tool_version.py +0 -0
  49. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tool_build_logs.py +0 -0
  50. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tool_versions.py +0 -0
  51. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/list_custom_tools.py +0 -0
  52. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/publish_custom_tool_version.py +0 -0
  53. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/api/custom_tools/update_custom_tool.py +0 -0
  54. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/client.py +0 -0
  55. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/errors.py +0 -0
  56. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/__init__.py +0 -0
  57. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_build_error.py +0 -0
  58. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_build_event.py +0 -0
  59. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_build_log_page.py +0 -0
  60. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_build_result.py +0 -0
  61. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_build_result_action.py +0 -0
  62. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request.py +0 -0
  63. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request_gputype.py +0 -0
  64. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_create_custom_tool_request_memory.py +0 -0
  65. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_create_version_request.py +0 -0
  66. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_custom_tool.py +0 -0
  67. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_custom_tool_gputype.py +0 -0
  68. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_custom_tool_memory.py +0 -0
  69. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_custom_tool_page.py +0 -0
  70. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_custom_tool_status.py +0 -0
  71. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_problem.py +0 -0
  72. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_problem_errors_type_0_item.py +0 -0
  73. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request.py +0 -0
  74. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request_gpu_type_type_0.py +0 -0
  75. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_update_custom_tool_request_memory_type_0.py +0 -0
  76. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_upload_session.py +0 -0
  77. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_upload_session_uploadheaders.py +0 -0
  78. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_version.py +0 -0
  79. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_version_page.py +0 -0
  80. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/models/public_version_status.py +0 -0
  81. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/_generated/types.py +0 -0
  82. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/client.py +0 -0
  83. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/packaging.py +0 -0
  84. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/resources.py +0 -0
  85. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/custom_tools/transport.py +0 -0
  86. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/errors.py +0 -0
  87. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/http.py +0 -0
  88. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/jobs.py +0 -0
  89. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/__init__.py +0 -0
  90. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/__init__.py +0 -0
  91. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/api/__init__.py +0 -0
  92. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/api/pipelines_public/__init__.py +0 -0
  93. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/api/pipelines_public/get_run.py +0 -0
  94. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/api/pipelines_public/list_node_run_molecules.py +0 -0
  95. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/client.py +0 -0
  96. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/errors.py +0 -0
  97. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/__init__.py +0 -0
  98. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/node_run_status.py +0 -0
  99. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_node_run.py +0 -0
  100. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_node_run_molecule.py +0 -0
  101. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_node_run_molecule_page.py +0 -0
  102. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_node_run_molecule_scores.py +0 -0
  103. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_problem.py +0 -0
  104. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_problem_errors_type_0_item.py +0 -0
  105. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_run.py +0 -0
  106. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/public_run_inputs.py +0 -0
  107. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/run_status.py +0 -0
  108. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/models/source.py +0 -0
  109. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/_generated/types.py +0 -0
  110. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/resources.py +0 -0
  111. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/pipelines/transport.py +0 -0
  112. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/py.typed +0 -0
  113. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/src/tamarind/rest.py +0 -0
  114. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_agent_contract.py +0 -0
  115. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_bugbash.py +0 -0
  116. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_cli_commands.py +0 -0
  117. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_config.py +0 -0
  118. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_custom_tools_cli.py +0 -0
  119. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_custom_tools_generation.py +0 -0
  120. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_custom_tools_sdk.py +0 -0
  121. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_file_filters.py +0 -0
  122. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_inputs.py +0 -0
  123. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_jobs.py +0 -0
  124. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_output.py +0 -0
  125. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_pep561.py +0 -0
  126. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_pipelines_sdk.py +0 -0
  127. {tamarind_cli-0.4.0 → tamarind_cli-0.4.1}/tests/test_rest.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: tamarind-cli
3
- Version: 0.4.0
3
+ Version: 0.4.1
4
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
5
  Project-URL: Homepage, https://tamarind.bio
6
6
  Project-URL: Documentation, https://app.tamarind.bio/api-docs
@@ -26,7 +26,7 @@ Description-Content-Type: text/markdown
26
26
 
27
27
  # Tamarind CLI
28
28
 
29
- [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
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)
30
30
  [![Python](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
31
31
 
32
32
  Command-line interface for the [Tamarind Bio](https://tamarind.bio) platform.
@@ -36,7 +36,8 @@ and download results — from your terminal, a script, CI, or an AI coding agent
36
36
 
37
37
  The CLI is a thin client over the same API the [Tamarind MCP
38
38
  server](https://mcp.tamarind.bio) uses, so the two stay in lockstep. See
39
- [`docs/architecture.md`](docs/architecture.md) for how drift is prevented.
39
+ [`docs/architecture.md`](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/docs/architecture.md)
40
+ for how drift is prevented.
40
41
 
41
42
  ## Install
42
43
 
@@ -58,7 +59,8 @@ uv tool install "git+https://github.com/Tamarind-Bio/tamarind-cli"
58
59
  # or: pipx install "git+https://github.com/Tamarind-Bio/tamarind-cli"
59
60
  ```
60
61
 
61
- > Releasing: tag a GitHub Release and the [`publish.yml`](.github/workflows/publish.yml)
62
+ > Releasing: tag a GitHub Release and the
63
+ > [`publish.yml`](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/.github/workflows/publish.yml)
62
64
  > workflow builds and uploads to PyPI via Trusted Publishing (configure the
63
65
  > trusted publisher for `tamarind-cli` on PyPI first).
64
66
 
@@ -170,6 +172,10 @@ Pass the opaque ID to `version`, `logs`, `cancel`, and `publish`. A local wait
170
172
  timeout does not cancel the remote build; reattach with
171
173
  `tamarind custom-tools version NAME VERSION_ID --wait`.
172
174
 
175
+ For the complete CLI workflow, source layout, build monitoring, publishing, and
176
+ rollback examples, see the
177
+ [Custom Tools CLI guide](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/docs/custom-tools.md).
178
+
173
179
  ## Output for agents
174
180
 
175
181
  Every command emits JSON when stdout is not a TTY, or with `--json`. Result
@@ -247,4 +253,5 @@ Questions or need help? Contact us at [info@tamarind.bio](mailto:info@tamarind.b
247
253
 
248
254
  ## License
249
255
 
250
- Licensed under the [Apache License 2.0](LICENSE).
256
+ Licensed under the
257
+ [Apache License 2.0](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/LICENSE).
@@ -1,6 +1,6 @@
1
1
  # Tamarind CLI
2
2
 
3
- [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
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)
4
4
  [![Python](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
5
5
 
6
6
  Command-line interface for the [Tamarind Bio](https://tamarind.bio) platform.
@@ -10,7 +10,8 @@ and download results — from your terminal, a script, CI, or an AI coding agent
10
10
 
11
11
  The CLI is a thin client over the same API the [Tamarind MCP
12
12
  server](https://mcp.tamarind.bio) uses, so the two stay in lockstep. See
13
- [`docs/architecture.md`](docs/architecture.md) for how drift is prevented.
13
+ [`docs/architecture.md`](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/docs/architecture.md)
14
+ for how drift is prevented.
14
15
 
15
16
  ## Install
16
17
 
@@ -32,7 +33,8 @@ uv tool install "git+https://github.com/Tamarind-Bio/tamarind-cli"
32
33
  # or: pipx install "git+https://github.com/Tamarind-Bio/tamarind-cli"
33
34
  ```
34
35
 
35
- > Releasing: tag a GitHub Release and the [`publish.yml`](.github/workflows/publish.yml)
36
+ > Releasing: tag a GitHub Release and the
37
+ > [`publish.yml`](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/.github/workflows/publish.yml)
36
38
  > workflow builds and uploads to PyPI via Trusted Publishing (configure the
37
39
  > trusted publisher for `tamarind-cli` on PyPI first).
38
40
 
@@ -144,6 +146,10 @@ Pass the opaque ID to `version`, `logs`, `cancel`, and `publish`. A local wait
144
146
  timeout does not cancel the remote build; reattach with
145
147
  `tamarind custom-tools version NAME VERSION_ID --wait`.
146
148
 
149
+ For the complete CLI workflow, source layout, build monitoring, publishing, and
150
+ rollback examples, see the
151
+ [Custom Tools CLI guide](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/docs/custom-tools.md).
152
+
147
153
  ## Output for agents
148
154
 
149
155
  Every command emits JSON when stdout is not a TTY, or with `--json`. Result
@@ -221,4 +227,5 @@ Questions or need help? Contact us at [info@tamarind.bio](mailto:info@tamarind.b
221
227
 
222
228
  ## License
223
229
 
224
- Licensed under the [Apache License 2.0](LICENSE).
230
+ Licensed under the
231
+ [Apache License 2.0](https://github.com/Tamarind-Bio/tamarind-cli/blob/main/LICENSE).
@@ -0,0 +1,240 @@
1
+ # Custom Tools CLI
2
+
3
+ The Custom Tools CLI, available in `tamarind-cli` 0.4.0 and later, takes a local
4
+ tool folder through validation, build, monitoring, and publication. It is useful
5
+ for a person working in a terminal, a CI job, or an agent with filesystem access.
6
+
7
+ ## Install and authenticate
8
+
9
+ Install or upgrade the CLI and confirm the installed version:
10
+
11
+ ```bash
12
+ uv tool install --upgrade tamarind-cli
13
+ tamarind --version
14
+ ```
15
+
16
+ Authenticate with an API key from the Tamarind web app (Settings → API):
17
+
18
+ ```bash
19
+ export TAMARIND_API_KEY="sk_..." # recommended for agents and CI
20
+
21
+ # Or store the key in ~/.tamarind/config.json:
22
+ tamarind auth login
23
+ ```
24
+
25
+ The examples below use `--json` so their output is stable for scripts and
26
+ agents. Global options such as `--json`, `--profile`, and `--api-base` must
27
+ appear before `custom-tools`.
28
+
29
+ ## End-to-end workflow
30
+
31
+ Suppose the source is in `./my-tool` and has this typical shape:
32
+
33
+ ```text
34
+ my-tool/
35
+ ├── Dockerfile
36
+ ├── run.sh
37
+ ├── config.json
38
+ └── ...
39
+ ```
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.
44
+
45
+ Run the lifecycle in this order. First, validate locally. This step does not
46
+ authenticate, upload, or build anything:
47
+
48
+ ```bash
49
+ tamarind --json custom-tools validate ./my-tool
50
+ ```
51
+
52
+ Next, resolve the durable Tool identity with an exact lookup:
53
+
54
+ ```bash
55
+ tamarind --json custom-tools get my-tool
56
+ ```
57
+
58
+ Branch on that command's exit code before continuing:
59
+
60
+ | Exit | Meaning | Next step |
61
+ |---|---|---|
62
+ | `0` | The Tool exists and is visible | Reuse it; do not run `create` |
63
+ | `4` | The Tool was not found or is not visible | Confirm the name is unclaimed, then run `create` |
64
+ | any other nonzero value | Authentication, transport, or another failure | Stop and handle the error |
65
+
66
+ For a confirmed unclaimed name, create the identity once:
67
+
68
+ ```bash
69
+ tamarind --json custom-tools create my-tool --display-name "My Tool"
70
+ ```
71
+
72
+ Package, upload, and build a Version, then wait for monitoring to finish:
73
+
74
+ ```bash
75
+ tamarind --json custom-tools build my-tool ./my-tool \
76
+ --idempotency-key release-1 \
77
+ --wait --timeout 1800 --poll-interval 10
78
+ ```
79
+
80
+ Finally, publish the completed Version using the opaque `version.id` returned by
81
+ the build:
82
+
83
+ ```bash
84
+ tamarind --json custom-tools publish my-tool VERSION_ID
85
+ ```
86
+
87
+ A successful local validation returns:
88
+
89
+ ```json
90
+ {"valid": true, "errors": [], "warnings": []}
91
+ ```
92
+
93
+ A build result has this general shape:
94
+
95
+ ```json
96
+ {
97
+ "action": "build",
98
+ "version": {
99
+ "id": "0192d87e-12ab-7cde-9f01-23456789abcd",
100
+ "name": "v3",
101
+ "toolName": "my-tool",
102
+ "status": "Complete",
103
+ "terminal": true
104
+ }
105
+ }
106
+ ```
107
+
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.
110
+
111
+ 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`,
113
+ and `logs` commands each return one page; follow `nextCursor` with `--cursor`
114
+ until it is `null` when a complete collection or log stream is required.
115
+
116
+ Use an idempotency key for builds initiated by automation. If delivery of the
117
+ first response is ambiguous, retrying with the same key returns the already
118
+ admitted Version instead of starting a duplicate build.
119
+
120
+ ## Runtime contract
121
+
122
+ The built tool runs with the following contract:
123
+
124
+ - The working directory is `/app`.
125
+ - Scalar inputs are supplied through environment variables.
126
+ - File inputs are mounted read-only under `/app/inputs/`.
127
+ - Write durable result files under `/app/out/`.
128
+ - Runtime network access is unavailable; include required weights and assets in
129
+ the image or inputs.
130
+ - Network access is available while the image is built.
131
+
132
+ The local validator catches archive hazards, a missing `Dockerfile`, and basic
133
+ `config.json` syntax/shape problems before upload. The server remains
134
+ authoritative for the full configuration contract and build outcome.
135
+
136
+ ## Monitor and reattach
137
+
138
+ For both `build --wait` and `version --wait`, `--timeout` starts when Version
139
+ monitoring begins. It does not include earlier work: local validation,
140
+ packaging, upload, and build admission for `build`, or the initial Tool and
141
+ Version reads for `version`. Use a process-level or CI deadline as well when the
142
+ entire CLI invocation must be bounded.
143
+
144
+ Exit code 7 means the monitoring timeout elapsed; the remote build may still be
145
+ running. Do not start a new build just because monitoring timed out. Reattach by
146
+ Version ID instead:
147
+
148
+ ```bash
149
+ tamarind --json custom-tools version my-tool VERSION_ID \
150
+ --wait --timeout 1800 --poll-interval 10
151
+ ```
152
+
153
+ Read build logs, following the returned cursor when the response has another
154
+ page:
155
+
156
+ ```bash
157
+ tamarind --json custom-tools logs my-tool VERSION_ID
158
+ tamarind --json custom-tools logs my-tool VERSION_ID --cursor NEXT_CURSOR
159
+ ```
160
+
161
+ Once the CLI has a durable Version, monitoring timeout and failure errors retain
162
+ `toolName`, `versionId`, and `versionName` in their structured detail. Errors
163
+ from the initial `build --wait` monitoring phase also include `action`; errors
164
+ from a later `version --wait` reattachment do not. A failure before build
165
+ admission has returned a Version cannot provide this handle, which is why
166
+ automated builds should reuse their idempotency key after an ambiguous request.
167
+
168
+ ## Publish and roll back
169
+
170
+ Publishing changes which completed Version is active. List Versions, inspect the
171
+ candidate, and publish its opaque ID:
172
+
173
+ ```bash
174
+ 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
177
+ ```
178
+
179
+ Rollback uses the same operation: publish the ID of an older known-good,
180
+ completed Version.
181
+
182
+ ## Update, cancel, and delete
183
+
184
+ Inspect and update the tool metadata:
185
+
186
+ ```bash
187
+ tamarind --json custom-tools get my-tool
188
+ tamarind --json custom-tools update my-tool --display-name "My Renamed Tool"
189
+ ```
190
+
191
+ Cancellation and deletion are destructive. Non-interactive callers must pass
192
+ `--yes` explicitly:
193
+
194
+ ```bash
195
+ tamarind --json custom-tools cancel my-tool VERSION_ID --yes
196
+ tamarind --json custom-tools delete my-tool --yes
197
+ ```
198
+
199
+ If a mutation returns `412 Precondition Failed`, refetch the Tool or Version,
200
+ confirm the mutation is still appropriate, and retry with the refreshed state.
201
+
202
+ ## Command reference
203
+
204
+ | Command | Purpose | Useful options |
205
+ |---|---|---|
206
+ | `custom-tools list` | Read one page of visible tools | `--limit`, `--cursor` |
207
+ | `custom-tools get NAME` | Read one tool | — |
208
+ | `custom-tools create NAME` | Create a tool identity | `--display-name` |
209
+ | `custom-tools update NAME` | Change tool metadata | metadata options |
210
+ | `custom-tools validate FOLDER` | Validate local source without auth or upload | — |
211
+ | `custom-tools build NAME FOLDER` | Package, upload, build, and optionally monitor a Version | `--idempotency-key`, `--wait`, monitoring `--timeout`, `--poll-interval` |
212
+ | `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 | — |
217
+ | `custom-tools delete NAME` | Delete a tool | `--yes` |
218
+
219
+ Run `tamarind custom-tools COMMAND --help` for every option and default.
220
+
221
+ ## CLI and MCP
222
+
223
+ The CLI and MCP are peer adapters over the public Tamarind API:
224
+
225
+ ```text
226
+ ┌─ Python SDK ─ CLI
227
+ Public Custom Tools API ─┤
228
+ └─ async HTTP adapter ─ MCP
229
+ ```
230
+
231
+ The MCP server does not shell out to the CLI. Both surfaces use the same public
232
+ contract, but they fit different execution environments:
233
+
234
+ - Use the CLI for local folders, shell scripts, CI, and agents with filesystem
235
+ and process access.
236
+ - Use MCP for remotely authenticated agents. Its equivalent lifecycle tools are
237
+ `deployCustomTool` and `getCustomTool`.
238
+
239
+ GitHub connection and push-to-deploy authorization are not part of the 0.4.0
240
+ release. The supported CLI path starts from a local source folder.
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "tamarind-cli"
3
- version = "0.4.0"
3
+ version = "0.4.1"
4
4
  description = "Command-line interface for the Tamarind Bio platform — submit, monitor, and download protein/molecule jobs from your terminal or an AI agent."
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.10"
@@ -17,7 +17,9 @@ from tamarind.errors import CustomToolUploadError
17
17
 
18
18
 
19
19
  _NETWORK_PATTERN = re.compile(
20
- r"\b(?:curl|wget)\b\s+https?://|\b(?:requests|httpx)\.(?:get|post)\s*\(|\burllib\.request\.urlopen\s*\(",
20
+ r"\b(?:curl|wget)\b[^\r\n;&|]*\bhttps?://|"
21
+ r"\b(?:requests|httpx)\.(?:get|post)\s*\(|"
22
+ r"\burllib\.request\.urlopen\s*\(",
21
23
  re.IGNORECASE,
22
24
  )
23
25
  _MAX_NETWORK_SCAN_BYTES = 1024 * 1024
@@ -618,9 +618,19 @@ def test_archive_rejects_windows_junctions(tmp_path: Path) -> None:
618
618
  (tmp_path / "junction").rmdir()
619
619
 
620
620
 
621
- def test_validation_leaves_config_semantics_to_the_server(tmp_path: Path) -> None:
621
+ @pytest.mark.parametrize(
622
+ "network_command",
623
+ [
624
+ "curl https://example.com/model.bin",
625
+ "curl -fsSL https://example.com/model.bin -o /tmp/model.bin",
626
+ "wget -q https://example.com/model.bin -O /tmp/model.bin",
627
+ ],
628
+ )
629
+ def test_validation_warns_for_shell_runtime_network_access(
630
+ tmp_path: Path, network_command: str
631
+ ) -> None:
622
632
  (tmp_path / "Dockerfile").write_text("FROM python:3.12-slim\n")
623
- (tmp_path / "run.sh").write_text("#!/bin/sh\ncurl https://example.com/model.bin\n")
633
+ (tmp_path / "run.sh").write_text(f"#!/bin/sh\n{network_command}\n")
624
634
  (tmp_path / "config.json").write_text(
625
635
  json.dumps(
626
636
  {
@@ -893,7 +893,7 @@ wheels = [
893
893
 
894
894
  [[package]]
895
895
  name = "tamarind-cli"
896
- version = "0.4.0"
896
+ version = "0.4.1"
897
897
  source = { editable = "." }
898
898
  dependencies = [
899
899
  { name = "attrs" },
File without changes
File without changes
File without changes