From dd5130108f3025a220b92095020eea20f7e8d2a4 Mon Sep 17 00:00:00 2001 From: S2D2 Date: Wed, 11 Nov 2026 15:46:07 +0000 Subject: [PATCH 1/2] docs: point agents at the shared MCP session and end-user retry helpers The MCP session plumbing and the end-user retry now live in one place each (_run_mcp_session and retry_for_end_user), so the "Modifying Tool Behaviour" list names them. The dependency note says why httpx2, which the transport uses on mcp 2, is not a declared core dependency: mcp 2 requires it itself. Co-Authored-By: Claude Opus 5.5 Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com> --- CLAUDE.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 228417b..facda3f 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -111,7 +111,9 @@ Never use `uv pip install`, and never use editable installs (`-e`). Two dependency tiers, nothing else. **Core** is what the SDK needs to function at all — `pydantic`, `httpx`, `mcp`, since `fetch_tools()` is the only route to -a tool and it talks MCP. **Extras** are everything else: per-framework adapters +a tool and it talks MCP. On mcp 2 the MCP transport runs on `httpx2`, which mcp 2 +itself requires, so it is not declared here; `GET /accounts` always uses `httpx`. +**Extras** are everything else: per-framework adapters (`langchain`, `pydantic-ai`), the `examples` set, and `dev` tooling. Adapters are imported lazily inside the method that needs them, so a bare install never drags in a framework you do not use. A new adapter goes in an extra with a lazy @@ -263,6 +265,8 @@ tools = toolset.fetch_tools(providers=["linear"], actions=["*_list_*"]) ### Modifying Tool Behaviour - Execution: `StackOneMcpTool.execute()` and `call_mcp_tool()` in `tools.py` +- The MCP session (transport, deadline, failure mapping) every list and call opens: + `_run_mcp_session()`; the one retry after an end-user refusal: `retry_for_end_user()` - Result parsing: `parse_tool_result()` - search/execute routing: `StackOneToolSet.execute()` - Tool construction and the feedback-tool dedupe: `StackOneToolSet._create_tool` and From 6f71924cf26d02356d34fe1bc2ab8538c9fed211 Mon Sep 17 00:00:00 2001 From: S2D2 Date: Sat, 14 Nov 2026 04:05:54 +0000 Subject: [PATCH 2/2] ci: retrigger CI after a flaky test_end_user_id shared-listing failure The failing test (test_requests_refused_together_share_one_accounts_listing) is unrelated to this docs-only change and passed on the prior head. Co-Authored-By: Claude Opus 5.5 Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>