Skip to content

v0.7.1

Choose a tag to compare

View all tags
@ashwin-agami ashwin-agami released this 04 Sep 12:46
· 285 commits to main since this release
v0.7.1
e211c64
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

One opt-in change, off by default: a deployment can require the thread_id that links a conversation's tool calls together.

Full notes: CHANGELOG.md

What's new

  • AGAMI_REQUIRE_THREAD_ID promotes thread_id from an optional tool property to a required one, on every tool that declares it. The id that groups a conversation's calls is self-reported — the activity-log directive asks for it and ends "Best-effort; omit if unknown" — and models take the omission. Measured on one deployment across two consecutive conversations: 2 of 10 calls carried one, then 0 of 8. With the property marked required, the same client sent it on 9 of 9.

Upgrading

Nothing changes unless you set the flag. The served tool surface, every schema and every default is identical to 0.7.0 with it unset, and a test pins that.

If you do turn it on, turn it on somewhere you can watch first. The MCP SDK validates arguments against inputSchema before dispatch, so a call omitting a required property returns an input validation error rather than a degraded record — this either works for your client or it takes the tools out of service for it, with no middle ground.

Assets 2
Loading