{"version":"2.1.280","anchor":"bridgeprojects-reply-mount-now-retries-its-mcp-dial-with-ba","canonical_anchor":"bridgeprojects-reply-mount-now-retries-its-mcp-dial-with-ba","heading":"bridge:projects reply-mount now retries its MCP dial with backoff","tier":"internal","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/bridgeprojects-reply-mount-now-retries-its-mcp-dial-with-ba","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### bridge:projects reply-mount now retries its MCP dial with backoff\n\nCloud project-thread MCP connections now retry with backoff instead of giving up after one failure\n\n**What**\n\nThe `bridge:projects` feature, which mounts an MCP (Model Context Protocol) server for a cloud 'project thread' reply, now retries its connection attempt on failure using a backoff schedule (waiting longer between each successive retry) instead of giving up after a single failed attempt. It logs a message when retries are exhausted, and reports separate telemetry while a connection is still retrying versus when it has failed for good.\n\n**Why**\n\nA single transient failure no longer permanently breaks the connection; the mount now has a chance to recover on its own. When retries do run out, the mount stays as-is until the underlying binding changes, and the new logging makes that state easier to diagnose.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}