# Using Pref in Muse Use your private installed connector in Muse. It maintains source-backed records; Muse uses your existing connected email and browser access to research them. The private service is on v0.4.4. Collection/save/fresh retrieval and selected acknowledgement have passed on demand. Automatic source collection with confirmed private delivery, correction UX and user-facing CSV download remain operational checks. New local wrappers do not install themselves in Muse. See [capabilities](/capabilities) for what has actually passed. ## Start with the saved portfolio Open a new Muse conversation and use the existing private `portfolio-agent` connector. Approve the individual requested API/credential-use calls when Muse asks; permanent access is not required. Keep the existing secure credential; never paste an API key into the conversation. > Use my installed portfolio-agent to retrieve my saved records and review them > now. Use fresh API results, not conversation memory. Give me a short factual > briefing of substantive company and fund developments with source links and > reporting periods. Flag a sourced capital call once; check tax documents only > when I request them. Distinguish > unknown, available and collected documents, and unknown values from zero. Flag > conflicts and do not infer payment status. For this first check, only read saved > records: do not search email, add records, send messages or execute transactions. After that read succeeds, use the on-demand research prompt below when you want Muse to check new evidence through its existing approved connections. The API has no automatic email ingestion, scheduler or financial transaction capability. ## Recognizable Pref updates Start each Pref-backed update with **A note from Pref**, even in plain text. When an assistant mixes topics, keep this heading with the Pref section or each separately delivered Pref message. A light opener is optional: “Pref here—quick update on [investment].” Then give the sourced development, any explicit action, source and reporting date, and relevant coverage gaps. Keep the voice warm and restrained. Label only updates grounded in Pref records or an explicitly authorized Pref workflow; unrelated assistant messages keep their own identity. The label does not imply Pref independently accessed email, verified a fact, sent anything or completed an action. Preserve uncertainty and the actual assistant’s role. Formatting never changes selected evidence or delivery/ACK rules. ## Actual LP updates and what needs attention > Read my saved actual LP letters and manager updates with portfolio-agent. Tell > me the material portfolio developments, manager commentary, and explicit LP > actions, with source links and reporting periods. Use summary.investments for > investment counts and show carry-only interests separately. Do not substitute > account statements, K-1 notices, or capital-call notices for an LP letter. Label > stale letters and missing coverage. Check existing email mirrors and already > collected documents first; reuse an existing authenticated session before > asking me to sign in again. Save brief sourced additions and document references, > preserving history. Do not send messages or execute transactions. Collection remains on demand. [The collection procedure](/public/collection.md) describes how to record scope and read/unread coverage without inventing comprehensive access or requesting new persistent permission. ## General review > Review my private investments with portfolio-agent. Show meaningful changes > since my last confirmed delivery, substantive company/fund developments and > materially new actions, with source links and reporting periods. Check for > relevant new email evidence. Respect my monitoring > preferences, distinguish unknown from zero, and do not infer that an old call is > still unpaid. Flag calls once unless I request a reminder or new information > arrives. Keep early performance secondary and tax checks optional. Prepare only > the exact update versions shown and acknowledge them after confirmed receipt. > Do not send messages or execute transactions. A useful briefing leads with material company/fund developments and sourced actions. Unknown values remain unknown; performance is secondary context. It should not repeat unchanged items as new. A deadline notice is not payment proof; a portal email is not a collected statement or K-1. ## Discover the rest of the portfolio > Use my optional spreadsheet/list seed, or connected email and accessible > platforms without a seed, to discover direct investments, funds, SPVs > and investment platforms. Compare with my saved records. Keep candidates > separate from confirmed holdings, show the specific source/access gaps, and ask > only about uncertain owners, vehicles or accounts. Use existing browser access > and request sign-in only where needed. The initial five-position batch is not a portfolio limit. Distinct legal owners remain separate positions. Invitations, pitches, newsletters and commitments without funding proof are not treated as funded holdings. ## Tax documents > Show my K-1 status for tax year [year], grouped by legal owner and investment. > Distinguish unknown, available and collected, cite the evidence, and include > closed investments when relevant to tax history. Do not infer collection from > an availability email. ## Add evidence or resolve a follow-up > Read this source using my existing access: [source link]. Match it to the correct > investment and legal owner, flag uncertain matches, and append the sourced > update without duplicating existing information or losing history. > This follow-up is complete, as confirmed by [source link]. Record the resolution > against its existing key, preserve its history, and verify it no longer appears > in the actionable review. Never paste credentials, account numbers or wire instructions into a record. A new obligation needs a new key. Reopening a resolved obligation or closed position under its old key is not yet supported; request a correction rather than silently creating a misleading duplicate. ## Cadence and access On-demand reviews are the initial workflow. Recurring cadence, timezone and conversation delivery must be agreed with the user and tested through Muse before claiming automated monitoring. No schedule is currently configured. If portal sign-in is required, use Muse's browser handoff and enter credentials in the portal's own sign-in form, never in chat. Pref access is private to the credential's user; there is no spouse/accountant sharing in this MVP. ## Correct a match and download the record Read document evidence before changing a match. Correct or retract the one reference using its current expected assignment ID and a sourced correction. Preserve the original extraction/history and verify in a fresh conversation. An exact future-version rule is a separate explicit action, not a consequence of correcting one document. Never acknowledge a stale prepared selection; read its pending status and replace only the invalidated selection explicitly. Ask the installed connector for `download_portfolio_spreadsheet`. Its authenticated CSV response must become a downloadable `portfolio.csv` artifact through Muse's supported download UI. A status message or CSV kept only in memory is not download acceptance. Unknown amounts remain blank, and a download acknowledges no updates. If the connector lacks the action, report that capability gap and use the approved secure client flow; do not paste a key or private error body in chat. The [versioned neutral recipe](/public/connector-recipe-v1.md) describes wrappers and receipt recovery. Supported Muse runtime/action installation and source/destination permissions must be verified separately before any finite or recurring run.