You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 01d5beb
Browse filesBrowse the repository at this point in the historyBrowse files
The Python, TypeScript and Ruby SDK upgrades switched those clients to
2026-10-21; this brings Go and Rust along so all five send the same version.
- Go: anthropic-sdk-go v2 (new module path; no other changes needed)
- Rust: anthropic-version 2026-10-21, key sent as Authorization: Bearer
- Ruby: require anthropic >= 2.3.0
- Tests: the fake API checks the version and auth headers on every request
Copy file name to clipboardExpand all lines: tests/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Tool calls reach the live NWS API. When it is unreachable the tools return an er
25
25
26
26
Connecting and listing tools does not exercise the chat loop, so each client is also driven through nine scripted queries with `tool-loop-test.ts`. No real API is involved: the helper starts a fake Anthropic Messages API on a loopback port and hands it to the client through `ANTHROPIC_BASE_URL`, which every quickstart SDK reads. The client talks to the mock MCP server as in the no-key test. The helper types each query only after the client shows its `Query:` prompt, as a person would.
27
27
28
-
The fake API picks a script from the query text and checks every request the client sends. Every request must carry the same system prompt, and its history must be one the real API accepts: no message empty, and every `tool_use` answered by a `tool_result` in the next message.
28
+
The fake API picks a script from the query text and checks every request the client sends. Every request must use API version `2026-10-21` and send the key as `Authorization: Bearer`, as the current SDKs do, and carry the same system prompt, and its history must be one the real API accepts: no message empty, and every `tool_use` answered by a `tool_result` in the next message.
29
29
30
30
-**parallel tools** — a response with two `tool_use` blocks, then one for a tool the mock server lacks, then an answer. `tools` must be passed on every call, `max_tokens` must be 10000 (room for the model's adaptive thinking), every `tool_use` must get a `tool_result` in a single following user message with matching `tool_use_id`s, and the MCP `isError` result must be forwarded as `is_error`.
31
31
-**ten tool turns** — exactly `MAX_TOOL_TURNS` tool calls, then an answer. The client must print the answer and no stop notice: nothing was cut short.
0 commit comments