Make AI-agent tool choice, state transfer, and context boundaries predictable

“> This issue was posted by Claude Code using claude-opus-5 on behalf of David. `clai` can attach MCP servers via `--mcp-config` (#1374), but `clai web` cannot. `_cli_web` exposes `-t/--tool` for native tools only, and `run_web_command` takes no `toolsets` parameter, so the two `clai` surfaces now answer "how do I give this agent tools?" differently: the terminal chat can load an `mcpServers` config, the web UI…”

“## Summary When a LangGraph Platform deployment is exposed as an MCP server, every tool call is executed as a *temporary* run: no durable state exists even while it runs (`checkpointer=None`), and its auto-created thread is deleted on completion. Two consequences: 1. A graph that calls `interrupt()` cannot park — there is nowhere to persist the pending state, and a temporary run can never carry a resume…”

“### Feature Description Please add a LlamaHub Agent Tools discovery entry for `llama-index-tools-sprites`, Superfly's independently maintained Sprites ToolSpec for LlamaIndex. - PyPI: https://pypi.org/project/llama-index-tools-sprites/ - GitHub: https://github.com/superfly/llama-index-tools-sprites - Release: https://github.com/superfly/llama-index-tools-sprites/releases/tag/v0.1.0 - Import: `from…”

“### Summary When an OAuth-backed Streamable HTTP MCP server returns `401` with a `WWW-Authenticate: Bearer resource_metadata=...` header (expired token), the rmcp transport worker terminates fatally and takes down the **entire `codex` app-server process** — not just that one MCP session. On Codex Desktop the blast radius is total: after the process dies mid-turn, the rollout is left without a turn-completion…”

“### Submission checklist - [x] This is a feature request, not a bug report or usage question. - [x] I added a clear and descriptive title that summarizes the feature request. - [x] I used the GitHub search to find a similar feature request and didn't find it. - [x] I checked the LangChain documentation and API reference to see if this feature already exists. - [x] This is not related to the langchain-community…”

“### Summary Document how a custom smolagents Tool should report a recoverable input failure versus an unrecoverable external failure. ### Current implementation facts smolagents supports custom tools, while its contribution guide requires accepted issues for non-trivial changes. ### Problem Tool authors must infer whether to raise, return an error string, or let the agent retry. Inconsistent choices make recovery…”

“### Submission checklist - [x] This is a feature request, not a bug report or usage question. - [x] I added a clear and descriptive title that summarizes the feature request. - [x] I used the GitHub search to find a similar feature request and didn't find it. - [x] I checked the LangChain documentation and API reference to see if this feature already exists. - [x] This is not related to the langchain-community…”

“## Summary I'd like to add a small `BilibiliHotTool` (~130 LOC) that wraps Bilibili's public `/x/web-interface/popular` API, so smolagents Agents can fetch trending Chinese videos without writing one-off HTTP calls. ## Motivation smolagents' built-in web tools (`WebSearchTool`, `VisitWebpageTool`, `WikipediaSearchTool`) are all English-centric. As a Chinese content creator using smolagents for trend research, I…”