#general

Jul 6July 7, 2026
AM
Alexander Mosharov12:55 PMOpen in Slack
hey Team!👋
I'm planning to submit a PR with this commit (github.com/archestra-ai/archestra/commit/4b153a675484…) to support tools that run longer than the standard 60-second timeout. I aimed for a minimal implementation.
However, judging by the issues in modelcontextprotocol/typescript-sdk, using resetTimeoutOnProgress=true with an onprogress callback seems like a cleaner way to handle this.
Would you recommend sticking with my minimal hotfix for now, or should we implement proper configuration parameters for the MCP client from the start?
3 replies
M(
Margaret (archestra team)4:22 PMOpen in Slack
Happy Tuesday!
Today’s Lyra feature: one-step connection for your coding agents :archestra-love:
Engineers working in Claude Code want to stay in Claude Code. Platform teams still need model calls and tool access to run through the right controls.
Now you can connect your favourite coding agents to Archestra’s LLM Proxy and MCP Gateway with one command. The same flow also works with Codex, GitHub Copilot CLI, and Cursor.
:stopwatch: We timed it: setup takes just 45 seconds.
Pull the latest release and check it out.
🚀1:archestra-banana-dance:1:archestra-sign:1:archestra-party-blob:1:archestra-rave:1

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!