Chat & agents

AI Agents (/agents) is the main chat workspace. You can start a new thread, pick a model, attach documents, and ask the assistant to search positions, create transactions, manage deals, and more.

Starting a chat

1. Open AI Agents from the sidebar (or AI Agents → New chat on desktop).
2. Type your question or paste data (CSV, JSON, statement text).
3. Attach files with the paperclip — PDFs, spreadsheets, and images are supported. Large spreadsheets and pasted dumps are read in full automatically; you do not need to split them.
4. Choose a model from the selector when you need more depth or a specific provider.

The assistant uses tools to read your live portfolio — it does not invent holdings. Create and update actions may require your approval unless auto-approve is enabled in org settings.

For non-trivial multi-step changes, the assistant often proposes a short plan first and waits for your confirmation before creating approval cards. Structured decision checks may also run before mutating tools are set up.

Models

Each org has a default analysis model. You can switch per thread:

• Claude (Sonnet, Opus) — strong reasoning and long context
• GPT — fast structured tasks
• Gemini — alternative provider
• OpenRouter — access to many models when enabled for your org

Model availability depends on your billing plan and org configuration under Settings → Setup. If a saved full or light default is no longer featured, the org uses another featured model from the same provider when one is available; otherwise it uses the platform default.

Projects

AI Agents → Projects groups related threads under shared instructions:

1. Create a project with a name and optional instructions (e.g. “Q1 statement import for Entity X”).
2. Start threads inside the project — the assistant sees project context and sibling thread summaries.
3. Use projects for recurring workflows (monthly reporting, deal screening) instead of one long thread.

Memory

AI Agents → Memory (/agents/memory) is where the assistant keeps short notes, and where you edit them.

Two layers, in this order, on every chat:

Organisation instructions are standing rules (“how this office wants the assistant to work”). They sit in the prompt ahead of the constitution. Facts do not belong there.

The notebook depends on the chat:

• A thread in a project uses that project’s notes. Org projects are shared with the organisation.
• A personal thread uses that member’s notes only.
• An organisation thread uses the office notes.

Notes stay in the notebook they were written in. Moving a thread changes which notebook the next turn sees.

Operator steps

1. Open AI Agents → Memory.
2. Edit Organisation instructions at the top (owners and admins). Other members can read them.
3. Switch the notebook to Personal, Organisation, or a project.
4. Add, rename, or delete a note. Each note is a short markdown page (title up to 80 characters, body up to 4,000 characters, 30 notes per notebook).
5. In a chat, ask the assistant to remember something durable (“remember we file tax estimates on 30/06”). It writes the current notebook. Ask it to change how it behaves for the whole office only when you want the standing instructions updated.

Proactive agents

AI Agents → Proactive runs background agents on a schedule:

Configure frequency, email notifications, and valuation thresholds per category (cash, funds, direct, real assets). The Proactive toggle for Portal retriever stays off; retrieval is driven by email, not by this card.

News Digest and Market Alert emails include the organisation name in the subject (so you can tell offices apart). Holding names in those emails open that position, and Open in FamilyOFX opens the matching agent thread — both switch you into that organisation first.

Portal retriever (fund portals)

When an internal inbox email says a report is waiting on a fund / GP investor portal (for example Fundrbird or a manager LP site) and the PDF is not attached:

1. FamilyOFX opens an AI Agents chat linked from that email.
2. The first time, a secure portal login card asks for username and password. Credentials are encrypted server-side and are not stored in the chat message.
3. The assistant logs in, downloads the file into the email’s documents, shows progress in the thread, then runs the usual extraction / approval cards.
4. The next email for the same portal host reuses the saved login and click path automatically (progress appears in the new chat). If login or download fails, the thread asks again or you can choose I’ll upload the file.

Limits (first version): username and password only. Banks, broker portals, authenticator apps, email/SMS codes, and captchas stay on the manual path — download the file yourself and upload or forward it. Connected Gmail (Nylas) that already runs internal extraction uses the same flow.

Approvals and auto-approve

When the assistant creates or updates data (positions, transactions, contacts), it usually creates action cards you approve or reject in the thread.

• Approve or Approve all — executes pending actions
• Cancel / discard — rejects pending actions
• With auto-approve enabled in org settings, mutating tools run immediately

Search and read-only tools (portfolio search, document search, product docs, constitution) never need approval. Updating the constitution from chat saves immediately for owners and admins.

Claude, ChatGPT, and MCP

You can connect Claude or ChatGPT to the same organisation data through the FamilyOFX MCP server. Reads run live; writes from the external app appear as pending approvals in AI Agents (MCP does not use org auto-approve).

Connect from the client, sign in, pick an organisation, and Allow on the consent screen. Upload documents in FamilyOFX before asking an external assistant to batch-import them. Revoke access under Settings → Integrations → AI connectors.

See MCP connections for full operator steps.

Deal & investment note documents

When reviewing a deal or tracking an active investment (position), you can share detailed research memos, meeting minutes, Zoom transcripts, or long-form notes directly with the AI assistant. Recorded meetings from Inbox → Recorded / the meeting recorder also land as transcript documents the assistant can read.

Instead of cluttering the single-text notes field of a deal or position, the assistant will automatically format and attach these as separate structured markdown documents.

Operator steps

1. Open a chat thread or select an existing project.
2. Share your call transcripts or long-form meeting notes (e.g. "Here are the meeting notes from my Zoom call with the founder on 03/09/2026").
3. The AI assistant will automatically attach a formatted note document containing:
   • A clear, dated title (e.g. Founder Zoom Call - 03/09/2026)
   • Clean, structured markdown content with key discussion points, milestones, and action items
4. You can ask the assistant to update, delete, or read note documents anytime:
   • To update: "Update the meeting notes document from 03/09/2026 to add that the seed round is oversubscribed"
   • To read: "What were the key takeaways from our last call with the founder?"
   • To delete: "Remove that draft memo document from yesterday"
5. In the dashboard under the deal or investment's Documents tab, click on any attached note to read it in-app with formatted typography, copy markdown, or download the .md file.

Tips

• Use European dates (DD/MM/YYYY) in chat.
• For statement imports, attach the PDF or paste CSV — ask to import into a named legal entity. Large files are read in full; you do not need to split a spreadsheet for chat.
• To add a listed holding from chat without a statement, the assistant looks up a quote, proposes quantity, price, date, currency handling, and legal entity, and asks you to confirm (or attach a broker confirmation) before creating the approval card.
• Ask “how does X work?” — the assistant can search these product docs.
• Forward documents to your shared inbox address to start threads from email.
• Support in AI Agents (the life-buoy / Support mode) messages the FamilyOFX team. Replies show in that same thread. You can also email etienne@familyofx.com.

See also: Workspace → Inbox and Testing with demo files.