OpenWork merged commit a612967 to make auth and MCP sessions durable, then followed with e6acd2c to fix offline access for existing MCP clients.
For platform teams running agent tools through cloud connectors, the watch item is no longer only whether an MCP server connects once; it is whether the session, token refresh, and origin metadata recover after the desktop or client boundary shifts.
Facts
- The durable-session commit added session MCP maintenance, cloud MCP user-state storage, auth-provider changes, and app tests.
- The same commit added a durable-auth MCP evaluation flow and Den API tests for bearer sessions, OAuth refresh, token lifetime, and route guards.
- The follow-up offline-access commit changed MCP scopes and OAuth refresh-flow tests for existing clients.
Evidence
The public receipts are OpenWork commits a612967, e6acd2c, and the earlier cross-origin protected-resource repair in bcb899b.
Context
The beat movement is reliability, not a new connector logo. OpenWork is treating MCP cloud access as stateful infrastructure: user state, OAuth refresh, protected-resource origin, offline access, and eval flows all have to agree.
Limits
This proves OpenWork's implementation direction, not a universal MCP durability standard. What to watch next is whether the project exposes these recovery paths in release notes and operator diagnostics rather than only tests and eval flows.