Your record. Your sources. Your assistant.

Use Pref across assistants

Pref organizes your private investments, updates and source links. Your assistant can use that saved history to explain what changed and continue in a new chat.

Your saved Pref record can continue across authorized assistants: holdings, source references, corrections, preferences and collection coverage stay with the same investor's record. Each assistant still needs its own permission to read your email, files or portals.

Claude Google sign-in and synthetic save/read have been verified for the approved owner. Muse has an existing separate portfolio pilot connection. Other assistant paths, continuity between them and usable private file output still need verification. Public enrollment is not open yet.

Connect Claude with Google

The shared Pref account page says: Continue with Google to create your Pref account or sign in. This wording and account flow apply to every configured Google-connected assistant. Your first successful Google sign-in creates a private Pref account automatically. Returning users reach the same account; there is no separate Pref password. Google supplies identity only (openid email profile); it grants no Gmail or Drive access. Completing the connection gives that assistant read/write access to saved records.

Use the same Google account across configured assistants to use the same Pref account. Claude, Muse and ChatGPT/Codex each need their own supported connection and verified callback configuration; seeing one working does not prove the others are available. Public enrollment remains closed.

For approved Claude access, add the approved /mcp URL in Claude’s connector settings. Use Claude’s published identity when offered and leave OAuth client ID and secret fields empty. Use the existing connector if your organization already has it. Select Connect, read the Pref account introduction, select Continue with Google, choose the right Google account, return automatically and verify Connected.

Connections use rotating refresh tokens with a rolling 90-day inactivity expiry. There is no routine twelve-hour approval screen. Provider errors, removal or long inactivity can require reconnecting. Connected assistants lists each grant and its connected date; Remove stops access and keeps saved records. Google’s picker handles account choice. To use a second configured assistant, connect with the same Google account; source permissions stay separate.

Only Claude’s published identity is built in. Additional assistants require an operator-configured public OAuth client with verified exact callback/origin support, then actual host acceptance. There is no claim that ChatGPT, dots or Muse already support this new route.

Existing operator-managed connectors remain available within their original scopes and expiry. They do not adopt Google accounts automatically. Linking an existing owner’s records requires verified identity plus explicit private ownership proof and operator approval; matching an email never transfers records. Other assistants retain their separately approved connection paths and require their own actual acceptance.

Reconnect an existing ChatGPT plugin

In ChatGPT, open Plugins → Personal → Pref. If it is connected, choose Try in chat. If it shows Connect, choose it and sign in with the same Google account you use for Pref. You return to ChatGPT automatically.

If an add-MCP dialog says an app named Pref already exists, cancel that dialog and open the existing Pref plugin. Do not create a second name for the same connection. If Pref is missing, ask for setup help; this preview requires a configured connection.

ChatGPT and Codex authorize separately. Connecting one does not install or connect the other. Use the same Google account in each to use the same saved Pref record. A Connected label confirms authorization; verify a live tool call and fresh-chat retrieval below.

Check the connection first

Use an invented investment and owner marked as a synthetic test. In a fresh conversation, retrieve that record without supplying its ID as a hint. Confirm the same saved ID, owner and source. Then check that your other authorized assistant sees the same saved preferences and correction history.

An assistant remembering a prior chat is not proof of shared Pref access. Do not start a real import until the operator confirms the connection and the separately agreed source permissions.

Get a private spreadsheet

Ask for your Pref CSV and confirm that your actual assistant produces a usable private file. Unknown or conflicting amounts should stay blank; saved sources and separate owners should remain visible. A response describing a spreadsheet is not the download.

Small files use the host's supported file interface. Larger files need exact authenticated retrieval and a verified private file capability. If your host cannot produce that file, report the limitation. Pref does not issue public export links or place access keys in URLs.

Confirm delivery separately

Review the exact selected content before approving delivery. A generated response or successful tool call does not prove the intended destination received it. The approved workflow must verify the actual receipt and avoid duplicates before marking those selected items delivered. Native tools do not automatically acknowledge a response.

Real source collection, recurring work, another person's access and public activation each need separate approval. See capabilities and coverage or get started.