Question: Documentation or Types for Desktop Agent implementation of App Directory
@kriswest is already working on this.
Since Jul 23, 2026.
- Dominant language
- TypeScript
- Stars
- 270
- Forks
- 194
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 36
Description
### Question Area
- [x] App Directory
- [ ] API
- [ ] Context Data
- [ ] Intents
- [ ] Use Cases
- [ ] Other
### Question
We are close to implementing the app directory support for our Desktop Agent. I have been reading the docs but there does not seem to be any clear indication about how a Desktop Agent should handle app directory records - I am thinking specifically about how to open an app.
The only docs that I have found is the [swagger](https://fdc3.finos.org/schemas/2.1/app-directory.html#tag/Application/paths/~1v2~1apps~1%7BappId%7D/get). This is of some use but I was hoping for at least some Typescript `d.ts` files.
Is it specified anywhere how a DA should open an app? I have made some assumptions:
- the DA should look through the hostManifests until it finds one it recognises and then use that to open the app.
- the host manifests should be listed in order of priority (if the DA knows about the first one it will open that and ignore the rest)
- ideally a web manifest should always be included at the end of the list so that a DA can always open an app even if know nothing about the other manifests
- the `url` supplied in the `details` section is not used for opening the app but is just used for app identity
Are these assumptions correct?
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.