Your record. Your sources. Your assistant.
Pref: your private investments, in one maintained record
Use your own assistant to organize holdings, keep source-backed updates and pick up the same record in a fresh conversation. Claude is the verified connection for the current preview. Muse retains its existing private pilot connection. New-account setup in other assistants still needs verification.
Public enrollment is not open yet. Access is limited to approved accounts and configured assistants. Requesting access does not create a Pref account or authorize collection.
For access, contact sam@thesideletter.co. Project site.
1. Create your Pref account
Select Continue with Google to create your Pref account or sign in. Your first successful sign-in creates your account; returning users keep their saved records. Then choose your assistant and follow its connection steps. No separate Pref password is needed.
If you started from a connector in your assistant, Google sign-in returns you there automatically. You can resume setup or manage connections from Pref afterward.
Use the same Google account in each configured assistant to use the same Pref account and saved records. This account flow is shared across configured assistants, including Claude, Muse and ChatGPT/Codex when their connections are available. Each assistant needs its own supported connection; availability in one does not establish availability in another. Google identifies you using identity-only permissions. Your assistant keeps responsibility for email, file and portal access. Sign-in grants no Gmail, Drive or Sheets access. Read privacy and service terms.
2. Connect Claude
For approved Claude access, open Claude’s connectors, choose Yours, and look for the existing Pref connector using the approved service’s /mcp URL. If it is connected, keep it and try the new-chat prompt; do not delete or recreate it. If it shows Connect, select that and sign in with the same Google account. Only add a custom connector when no matching connector exists, leaving OAuth client ID and secret fields empty. If Claude says this URL already exists, cancel the add dialog and use the existing connector; an organization administrator may need to make it available. Google may show its own identity confirmation.
You return to Claude automatically. Connections renew in the background; an expired or revoked credential can still require reconnecting. Use Connected assistants to remove an assistant’s access while keeping your saved records. A second configured assistant follows the same flow using the same Google account. Email access and private conversations do not transfer.
Your assistant should check its own email tools after connection. If it needs access, connect Gmail through that assistant’s supported settings. The service cannot inspect every tool your assistant has. Check portal access separately when it becomes relevant.
New accounts receive one transactional welcome email when the configured sender is active. Login, reconnecting and adding another assistant do not send another welcome.
Claude custom connector setup depends on your account’s available controls. It is not a directory listing or automatic installation. Muse, ChatGPT and dots retain their existing separately approved setup paths; this Google release does not establish acceptance for them. The existing Muse pilot uses secure credential capture, never token pasting into a conversation. Contact support if a secure supported route is unavailable.
3. Check your connection
First ask your assistant to check its live Pref access and whether your account is in test mode. For a new test account, ask your connected assistant to save an invented investment and invented owner marked as a synthetic test with an invented source. Open a fresh conversation and ask it to retrieve the saved test through the connector, without supplying the record or its ID as a hint. Confirm the same saved ID, owner and source. Before a second assistant uses that record, separately verify its scoped connection, source boundaries and fresh-client preference/correction/history continuity. A response remembered from chat is not this check.
New test accounts stay synthetic-only through this check. Do not import real holdings into them. An existing enabled account can continue using its saved portfolio. If authentication fails or the saved record cannot be retrieved, stop and ask support to check the setup.
4. Confirm your inventory and its owners
You can start with an optional investment list or spreadsheet, or ask your assistant to discover candidates from sources you separately authorize in your own account. No seed list is required. Start with a bounded source and date window that you understand.
Review the proposed candidates, exact legal owners, vehicles and supporting sources before they become confirmed holdings. A seed name, pitch, unsigned subscription or invitation is a clue, not proof of ownership or funding. Uncertain matches remain candidates; unknown amounts remain blank. Different legal owners stay separate.
5. Authorize a bounded first import
After ownership is evidenced, agree which holdings, sources and date window may be collected and saved. The operator confirms your account is ready for the agreed real import. Your assistant uses your own authorized email or browser access; the service does not receive portal passwords, cookies or email credentials.
Save concise facts and references, then retrieve them in a fresh conversation and check the owner and source. Confirm what was checked and what was blocked, stale or unread. Your Google-connected assistant renews its connection in the background. Existing operator-managed pilot credentials keep their separately agreed permissions and expiry. New sources, recurring jobs and destinations require separate consent and acceptance.
Use the record
Ask what changed, which entity owns a position, or where the original source can be found. Using Pref in Muse includes review, discovery, correction and spreadsheet prompts.
Ask for a correction when an owner or document match is wrong. The original evidence and correction history are preserved. A CSV download should become a usable private file in your actual assistant; if that action is missing, report the gap. To send a copy to Google Sheets, choose and confirm a destination through your own separately authorized connection, then verify the result using the spreadsheet workflow.
Automatic source collection and confirmed private delivery, the current Muse correction/download experience, ongoing retained backups and another consenting user's complete setup still require operational acceptance. Local tests do not establish them. Other installed assistants, usable exact CSV files and actual destination receipts are separate acceptance gates. No native tool automatically ACKs a generated response. Public launch remains subject to approval and operational acceptance.