FDC3 for Web Browsers & Bridging Discussion group - 16th October 2025

[kriswest]

Group overview

Discussion group focused on FDC3 use in Web browsers and the Bridging of FDC3 Desktop Agents to allow interop to span across them (based on similar techniques to FDC3 comms in a Web browser).

Software support for both FDC3 in a Web Browser and Desktop Agent Bridging are provided in the FDC3 2.2 NPM module: https://www.npmjs.com/package/@finos/fdc3/v/2.2.0

Relevant issue tags

Current open issues that relate to the above concepts with the labels:

Meeting Date

Thursday 16th Oct 2025 - 10am (US eastern timezone EDT) / 3pm (London, BST)

Zoom info

• Join Zoom Meeting
• Meeting ID: 969 4029 4948
• Passcode: 636931
• Dial-in:

  Country	International Dial-in	Toll-free Dial-in
  US	+1 929 205 6099 (New York)	877 853 5247
  UK	+44 330 088 5830	0800 031 5717
  France	+33 1 8699 5831	0 800 940 415
  Find your local number	https://zoom.us/u/ad2WVnBzb8

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

• A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.

Participation Requirements

Note: Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.

Please click the following links at the start of the meeting if you have not done so previously.

• View the CSL
• View the GOVERNANCE of the Project
• Click here to start a PR.
  • Edit the page to add your details.
  • Hit the save button.
  • Click "Create Pull Request".
  • Click "Accept" on the EasyCLA dialog in the PR's discussion section.
• Click here to send email to become a voting participant on the FDC3 Project

Tracking Attendance

Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • FDC3 for Web Browsers & Bridging Discussion group - 21st Aug 2025 #1653
• Note recently merged PRs:
  • fix: bind this in API-returned objects & update docs for JS implementers #1645 (note new compliance requirement for web implementations - mostly needs to be implemented by preload DAs, as it is already implemented in DesktopAgentProxy instances returned by getAgent)
  • Context clearing (1197) #1642
  • Support Dynamic intent handler registrations in FDC3 web reference implementation #1613
• (short) FDC3, MCP-UI, AG-UI, WebMCP, OpenAI Apps SDK and the intersection of AI and UI #1669 - where will conversation happen?
• WCP1Hello request provides resolver property instead of the documented intentResolver property #1683
  • fix to HelloHandler in getAgent to send the correct property #1684
• Improve heartbeat argument handling in the FDC3 for Web reference implementation demo #1678
• Contributions sought to resolve issues:
  • Clarify the stateful nature of channels #1660
  • Suggestion: fdc3.addContextListener() should accept an array of contextTypes to listen for #1646
  • Clarify that Context types are defined in JSON and may be handled differently in specific API bindings #1486
• FDC3 Terminology Changes #1657
  • What changes would simplify comprehension of the Standard for App developers?
  • What changes are more or less disruptive or breaking?
• Support for Multiple Application Scopes (Agents) within a single window process #1250 & Question: Disposal/Teardown patterns in FDC3 #1263
  • Continue discussion of approaches to launching and teardown
    • Simpler proposals: Launching handled by parent application
      • Parent could be registered for all intents of sub-apps and determines what to launch to resolve?
      • Or sub-app records could be nested under parent app records in appD and a launch context passed to an exiting parent or new parent app launched?
      • Once launched sub-app has its own identity (instance-id) and can be targeted directly
    • Parent app registers a launch function of some sort with DA?
      • @novavi has furthe rdetails of proposals
• AOB & Adjourn (5mins)

Minutes

• Review of action items from previous meeting

  • No outstanding action items from August; September’s meeting was skipped and its agenda rolled into this meeting.
  • Discussion on CommonJS builds was deferred for maintainers' meeting (@Roaders leading work, to be discussed with @kriswest and @julianna-ciq after OSFF).
  • Use cases for nested vs. flat app directory records for sub-apps revisited and deferred for future discussion.

• Recently merged PRs

  • Three notable PRs have been merged into the draft:
    • fix: bind this in API-returned objects & update docs for JS implementers fix: bind this in API-returned objects & update docs for JS implementers #1645: introduces a new compliance requirement for web implementations (mainly for preload DAs).
    • Context clearing (1197) Context clearing (1197) #1642: standard now contains a proposal for clearing context; reference implementation still needs improvements.
    • Support Dynamic intent handler registrations in FDC3 web reference implementation Support Dynamic intent handler registrations in FDC3 web reference implementation #1613: adds dynamic intent handler registrations, improving the FDC3 workbench testing experience.
  • No questions or objections raised; these will be fully adopted after the next standards version vote.

• FDC3, MCP-UI, AG-UI, WebMCP, OpenAI Apps SDK & AI/UI intersection

  • @novavi summarised the issue: focus on the intersection between AI chat-based and traditional deterministic workflows.
  • Next steps: Topic to be discussed at the Use Cases Working Group meeting on 6 Nov; @novavi to coordinate with Vinay to publicise and organise agenda.

• WCP1Hello request property mismatch

  • Issue identified where the documentation, implementation, and schema did not align on the intent resolver property name.
  • @julianna-ciq and @robmoffat confirmed the impact is on DA implementers, not consumers; change will be published in a minor release (likely 2.2.2).
  • Action agreed: Maintain a list of corrections for targeted backport/cherry-pick into a release branch; maintainers to coordinate on specifics.

• Improve heartbeat argument handling in FDC3 for Web reference implementation demo

  • @kriswest described reference implementation issues: argument handling for heartbeat is inconsistent and disabling/enabling is unreliable.
  • Highlighted browser behaviour: background/frozen tabs may prevent message delivery, resulting in “zombie” apps.
  • Consensus: Add messaging to inform desktop agents about app state changes (hidden/frozen) via getAgent; leave DA behaviour implementation-specific for now, but monitor for interoperability issues.
  • Agreed to raise three issues:
    1. Messaging app state changes
    2. Handling reconnection after state changes.
    3. Impact of DA (desktop agent) itself being hidden/frozen.

• Contributions sought to resolve issues

  • Call for contributions and PRs on:
    • Clarifying the stateful nature of channels (Clarify the stateful nature of channels #1660).
    • Allowing fdc3.addContextListener() to accept an array of contextTypes (Suggestion: fdc3.addContextListener() should accept an array of contextTypes to listen for #1646).
    • Clarifying context type handling in JSON/spec (Clarify that Context types are defined in JSON and may be handled differently in specific API bindings #1486).
  • @kriswest will be available to support new contributors; particularly editorial tasks toward the end of the year.

• FDC3 Terminology Changes

  • Discussion on proposal FDC3 Terminology Changes #1657 to simplify and clarify FDC3 terminology for app developers.
  • @kriswest summarised maintainer consensus: Large-scale renaming is seen as too disruptive for limited value, but improving documentation (especially Getting Started and homepage content) is prioritised.
  • Broad agreement to:
    • Focus on clarifying introductory and API documentation.
    • Consider alternative expansions for "FDC3" that are less finance-specific; @paulgoldsmith to share ChatGPT suggestions.
    • Recognise benefits and drawbacks of finance-specific branding.
    • Seek contributors for content updates and ideas.

• Support for Multiple Application Scopes (Agents) within a Single Window Process

  • Not discussed due to time constraints.
  • Brief check-in: Interest remains, especially from @paulgoldsmith and @Roaders; @novavi noted real-world relevance may fluctuate—will revisit when there is further momentum or contribution.

Action Items

• @kriswest and @julianna-ciq to connect after OSFF and progress Add property to support analytics across apps #1290 & [WIP] Expand broadcast, raise*, and open methods to include metadata #1595
• @novavi to help publicise and coordinate the AI/UI intersection topic for the 6 Nov Use Cases WG meeting.
• @kriswest, @robmoffat, @julianna-ciq: Collate and backport required PRs/fixes for the next point release (2.2.2), including WCP1Hello property correction and Interop.io conformance test issues.
• @kriswest to raise three issues for:
  • Messaging app state changes (hidden/frozen) - Report app page lifecycle events through FDC3 for Web protocols to enable DAs to improve HeartBeat Handling #1703
  • Reconnection/handling after state changes. - Explore and Improve handling page life cycle state changes in FDC3 for Web / getAgent() #1704
  • Desktop agent state (if hidden/frozen). - Explore behavior of Browser-based Desktop Agents when their own windows are hidden or frozen (page life cycle) #1705
• @kriswest to raise an issue for improving Getting Started and homepage content, soliciting contributions.
• @paulgoldsmith to add ChatGPT-generated FDC3 acronym suggestions to the terminology issue.
• (Open) Community contributors: Invited to work on documentation clarifications, improved introductory material, and flagged PRs (Clarify the stateful nature of channels #1660, Suggestion: fdc3.addContextListener() should accept an array of contextTypes to listen for #1646, Clarify that Context types are defined in JSON and may be handled differently in specific API bindings #1486).
• (Open) Await further contributions/activity on multiple application scopes before returning it to the agenda.

Untracked attendees

Full name	Affiliation	GitHub username

[paulgoldsmith]

Paul Goldsmith / Morgan Stanley

[julianna-ciq]

Julianna Langston / interop.io

[kriswest]

Kris West / NatWest 🚀

[robmoffat]

Rob Moffat / FINOS

[SeeWhatsOn]

Chris Watson / Elgin White

[Roaders]

Giles Roadnight / Morgan Stanley 🚀

[novavi]

Derek Novavi / S&P Global

[diafwill]

Vincent AZOMAHOU /ORISHAS FINANCE