v0.5.0

Add the Python SDK surface — client.jobs / client.tools / client.files mirroring the CLI command groups — plus jobSource attribution distinguishing the cli and sdk channels. Shared presigned-upload path between the CLI and SDK.

tamarind-cli v0.4.3

Custom Tools lifecycle improvements and explicit SDK/CLI test runs, combining #35 and #37.

• Run a completed version before publishing with tool.test(...) or tamarind custom-tools test.
• Simplified cancellation with optional observed-state checks.
• Internal tool identity hidden from SDK representations and CLI output.
• Improved input validation and recovery guidance for ambiguous submissions.

Compatibility: standard SDK/CLI calls continue sending checksums and validators for older backends. Early upload precondition enforcement and optional low-level header/checksum omissions require website #4848. Test-history integration requires deployed website #4868.

v0.4.2

Fixes

• Catch the correct Click exception family when Typer vendors Click.
• Preserve structured JSON usage errors instead of leaking Python tracebacks.
• Add built-wheel coverage against freshly resolved runtime dependencies.

The Custom Tools, SDK, and command surface are otherwise unchanged from v0.4.1.

tamarind-cli v0.4.1

Patch release for the Custom Tools CLI.

• Detect runtime curl and wget downloads when common flags precede the URL.
• Add regression coverage for flagged shell download commands.

🤖 Generated with Codex

tamarind-cli v0.4.0

Custom Tools in the unified Tamarind CLI

• Add tamarind custom-tools lifecycle commands for listing, creating, updating, validating, building, monitoring, logging, cancelling, publishing, and deleting Custom Tools.
• Keep exact operations on opaque Version IDs and preserve reattachment handles when bounded waits fail.
• Require explicit confirmation for destructive cancellation and deletion in agent/non-interactive use.
• Fix isolated-wheel installation by declaring the direct Click runtime dependency.

GitHub connection and endpoint-renaming work remain intentionally outside this release.

v0.3.2

What changed

• use opaque Custom Tool Version IDs for exact reads, logs, cancellation, and publication
• keep generated SDK signatures synchronized with the standard If-Match OpenAPI contract
• bridge Custom Tools validators at the final SDK transport boundary so Vercel cannot replace committed mutation successes with edge-generated 412 responses
• preserve stale-write protection across update, delete, build, cancel, and publish

Verification

• 400 tests passed across Python 3.10–3.14, macOS, and Windows
• generated-contract freshness, typing, lint, and release artifact checks passed
• live CC create → get → update → verify → delete lifecycle passed with the release code

🤖 Generated with Codex

v0.3.1

What changed

• Fix Custom Tools build, version, log, publish, and cancellation requests for the concise production API routes. Tool generations are now sent through X-Tamarind-Tool-Generation.
• Add typed Pipelines run and node-run molecule resources.

Verification

• 396 tests passed locally.
• Generated-contract freshness, type checking, lint, package build, and wheel smoke checks passed.
• GitHub Actions passed on Python 3.10–3.14, macOS, and Windows.

v0.3.0

What's Changed

• Add a typed Custom Tools Python SDK by @ezhong0 in #21
• Sync Custom Tools contract provenance by @ezhong0 in #22
• Fix Custom Tools optimistic concurrency by @ezhong0 in #23

New Contributors

• @ezhong0 made their first contribution in #21

Full Changelog: v0.2.0...v0.3.0

v0.2.0

What's Changed

• Harden the CLI contract for agent workflows by @AshokDevireddy in #16

Full Changelog: v0.1.4...v0.2.0

v0.1.4

Ships jobSource="CLI" on job submissions (submit-job / submit-batch) for usage tracking.

Install/upgrade:

curl -fsSL https://install.tamarind.bio/cli/install.sh | sh
# or: uv tool install --force tamarind-cli   /   pipx install --force tamarind-cli