Thank you everyone for coming and also to those who demo'ed some cool Swift projects! Here are the minutes from the meeting:
Intro and Demos:
- @Padmashree06 was chosen as a GSoC 2026 contributor. She will be working on improved Swift DocC support in SourceKit-LSP/VS Code. Welcome to the Swift Community!
- @matthewbastien demo'ed improved Swift extension startup performance and automatic toolchain switching.
- @sebsto demo'ed working with Swift in Amazon's Kiro Agentic IDE.
- Kiro : https://kiro.dev/
- Swift power for Kiro : GitHub - sebsto/swift-kiro-power: A Kiro power to develop in Swift · GitHub
- Cupertino tool (Apple doc indexed and exposed as an MCP Server) (built by Mihaela Mihaljevic) GitHub - mihaelamj/cupertino: A local Apple Documentation crawler and MCP server. Written in Swift. · GitHub
- @Joannis_Orlandos demo'ed the WendyOS extension in VS Code
- WendyOS website: https://wendy.sh/
Q&A Session:
Q: When will the extension activation changes be available?
- A: We're having some trouble with CI, but the changes should land in a pre-release by next week. The plan is to have it soak for about a month to iron out any issues before doing an official release.
Q: I'm having an issue where the extension is constantly re-indexing my AWS SDK when it doesn't need to. What's the best way to report this?
- A: Report any issues with indexing to the SourceKit-LSP repository and include a
sourcekit-lsp diagnoseif possible. The more reports of issues we get the easier it is to find and prioritize fixes. - Workaround: You might be able to disable background indexing as a temporary fix and have SourceKit-LSP only index when you build.
- A: Report any issues with indexing to the SourceKit-LSP repository and include a
Q: Will the Swift extension pre-release fix PATHissues involving swiftly? My editor is preferring to use the toolchain in/usr/bin/swiftover swiftly's.- A: No, this is an issue that was fixed in swiftly itself. It will be available in swiftly v1.2.0 when that gets published. If you're still seeing this issue after the swiftly v1.2.0 release then please file an issue and we can have another look!
Q: How often will there be VS Code office hours?
- A: We'd like to have these meetings at a regular cadence, but haven't decided on timing yet. At most it will be every couple of months. Stay tuned for more invites!