Your product runs the Mindset SDK and the loop; Mindset holds configuration, versions and tests, rules, keys, records and the MCP server; it calls the model provider and your systems; your coding agent configures Mindset through the MCP server

Architecture

Configuration in Mindset. The loop runs beside your users.

On your page the SDK runs the agent in the browser, so replies stream and page tools run with no round trip. Your server creates the session; the API key never reaches the browser.

4 of 11
Speaker notes

A session is an opaque credential for one agent, one user, one org and one environment, kept in memory; the SDK renews its own short-lived token. Your server names the user by email or an external id. Every way in reads the same configuration, so a new version reaches users on their next turn with no release of your code. Server-started runs, schedules and webhooks run the agent on Mindset’s side.