GitHub’s Project HydraFusion research preview (all Copilot plans via /experimental in Copilot CLI) picks single, cascade, or critique multi-model workflows per task. On TerminalBench 2.1 it beat Claude Opus 5 by 4.9 points at 67% lower estimated cost; usage bills at each model’s standard token rate.
Announced Oct 22, the upgraded server at api.causely.app/mcp ships the guidance agents need to use its tools on first connection and ties every agent action back to the diagnosis and evidence behind it, for Claude Code, Cursor, Codex, and other MCP clients. Causely's own benchmark claims 48% fewer tokens and 63% faster answers, and background agent examples are open source at causely oss…
Announced Oct 22, the Git host now runs an MCP server at https://mcp.codefloe.com/mcp that Claude Code, Codex, VS Code, or any MCP client can use to work with your repositories, issues, pull requests, releases, Pages, and CI quota. It authenticates with your own access token, so the agent can do only what that token's scopes allow…
Add one URL ( https://agentic testnet mcp.hedera.com/mcp ) and sign in with a HashPack or Kabila wallet over OAuth, and your agent can transfer HBAR, mint tokens, deploy contracts, and post consensus messages, but the server holds no keys and every transaction waits for your wallet approval. It's testnet only, with no spend caps, so the wallet prompt is your only guardrail (CryptoCompass)…
Announced Oct 22, Claude users can now add Qlik from the Claude Directory to search Qlik Cloud apps and datasets, ask questions over governed data, trace lineage, and build sheets and charts by prompt, all under existing Qlik permissions via OAuth. Access needs the Qlik MCP: Allowed role permission (setup docs)…
Released Oct 22, it reuses cached local MCP tool snapshots across registered Git worktrees in one repo, makes ACP sessions honor saved sandbox settings and sandbox / no sandbox on resume, and swaps the legacy remote / no remote startup flags for clearer hosting and connection options. It also fixes Gemini tool calls failing schema validation on nullable and enum fields and keeps cloud replies intact after a dropped connection…
Spotted something we missed? Start a thread.