finos
Enhance FDC3 standards for LLMs
Enhancement Request
There has been a lot of discussion lately around LLMS and how they intereact with FDC3 and what can be done improve these workflows. This issue is meant to be an broad overview of how we can work to improve the FDC3 standard to make working with LLMs better.
Use Case
Generally speaking as LLMs work their way into developer tools there is a natural curiosity to see how they can be used with in context space of working on FDC3 desktop agent applications. There appear to have been multiple independent attempts at working with LLMs and the appD directory including but limited to interop.io's work with ioInsights, Derek Novavi's work with an early MCP-FDC3 library, the discussions around #1699, and various acknowledgements in other discussions.
For example one space that seems to have come up has been using an LLM to pick a published intent as a tool for the desktop agent to proceed with an action. In this scenario a user would like to perform an action (typically while in a chat window) and kick off some interop enabled workflow.
Proposals
The intent of this issue is to find out if there is enough consensus on these problems to merit raising specific enhancements on how to improve LLM integration.
To date it seems like a lot of the early attempts at utilizing LLMs with in a desktop agent are tied to trying to mine the appDirectory for appropriate information. Multiple people have mentioned this as a starting point. Our initial goals for working with LLMs should focus on how to make this easier.
Talking to the team working on integrating LLMs with an FDC3 desktop agent there was one response that I overwhelming received: there is not enough context available in the appDirectory to feed the LLM. Currently the available information inside an apps intents property is not rich enough.
The other use case that has been discussed previously has been working with MCP UI or another similar framework on how to produce UI elements in a chat. After speaking with the internal team at interio.io there was concern that this may not be the appropriate place for FDC3 to get involved since very little of the spec is prescriptive of how a desktop agent should handle UI elements.
