Skip to content

Track toolkit 0.5.0 / 0.3.0 (structured output + native errors) [blocked on publish]#3

Merged
duharry0915 merged 2 commits into
mainfrom
chore/toolkit-0.5.0-compat
Jul 13, 2026
Merged

Track toolkit 0.5.0 / 0.3.0 (structured output + native errors) [blocked on publish]#3
duharry0915 merged 2 commits into
mainfrom
chore/toolkit-0.5.0-compat

Conversation

@SanjithSambath

Copy link
Copy Markdown
Contributor

Updates the plugin to the new AgentMail Toolkit contract (TypeScript 0.5.0 / Python 0.3.0).

Changes

  • compatibility.json: toolkit TS 0.4.2 → 0.5.0, Python 0.2.7 → 0.3.0.
  • skills/agentmail-toolkit/SKILL.md: the MCP tool object now includes an output schema; successful MCP calls return validated structuredContent + text; failed calls throw / return isError instead of returning an error string (the one breaking behavioral change plugin authors must know). Added a "Results and errors" section, version-gated to toolkit TS ≥ 0.5.0 / Python ≥ 0.3.0.
  • CHANGELOG.md: Unreleased entry.

⚠️ Blocked on publish — this is why it's a draft

scripts/check_compatibility.py gates compatibility.json against each registry's latest. npm currently serves agentmail-toolkit@0.4.2 and PyPI 0.2.7, so the compatibility CI check is intentionally red until 0.5.0 / 0.3.0 are published. That gate is the verification.

Merge sequence: publish agentmail-toolkit@0.5.0 (npm) + 0.3.0 (PyPI) → re-run CI (goes green) → mark ready → merge.

Scope confirmed complete: version literals live only in compatibility.json; README and other skills carry no toolkit version/behavior. The agentmail-mcp skill already points at the hosted endpoint (unchanged here).

🤖 Generated with Claude Code

Bump compatibility pins to agentmail-toolkit TypeScript 0.5.0 / Python 0.3.0 and
document the toolkit's new contract in the agentmail-toolkit skill: every tool
declares an output schema, MCP calls return validated structuredContent, and
adapters signal failures through their framework's native error channel (throw /
isError) instead of returning an error string.

BLOCKED on the 0.5.0 / 0.3.0 npm + PyPI publish: check_compatibility.py gates on
the registry 'latest', so CI stays red until those versions go live. Merge after
publishing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@SanjithSambath SanjithSambath marked this pull request as ready for review July 13, 2026 04:58
The blocking PR gate (validate.yml) type-checks the TypeScript examples against a
hardcoded toolkit version, separate from compatibility.json. Bump it to 0.5.0 so
the plugin's examples are actually validated against the new toolkit (and the
throw-on-error change is exercised). This also makes the gate correctly RED until
0.5.0 is published, since installing an unpublished version 404s.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@duharry0915 duharry0915 merged commit 8afdc9c into main Jul 13, 2026
1 check passed
@SanjithSambath SanjithSambath deleted the chore/toolkit-0.5.0-compat branch July 13, 2026 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants